No problem.
You may want to set your variables in your /etc/sysconfig/slurmrestd file.
That is where you can set that variable along with others
(SLURMRESTD_LISTEN, SLURMRESTD_DEBUG, SLURMREST_OPTIONS) and your
service file will pick them up.
Brian Andrus
On 6/14/2021 12:05 PM, Heitor wrot
On Mon, 14 Jun 2021 11:25:52 -0700
Brian Andrus wrote:
> Using v20.11.7
>
> I have 8081 because that is the port I am running slurmrestd on.
>
> How are you starting slurmrestd? If you are using systemd and have
> the service file, look inside it.
I'm using systemd:
$ cat /usr/lib/sys
Using v20.11.7
I have 8081 because that is the port I am running slurmrestd on.
How are you starting slurmrestd? If you are using systemd and have the
service file, look inside it.
Brian Andrus
On 6/14/2021 9:48 AM, Heitor wrote:
On Mon, 14 Jun 2021 08:30:51 -0700
Brian Andrus wrote:
Yo
On Mon, 14 Jun 2021 08:30:51 -0700
Brian Andrus wrote:
> You don't use the prefix.
>
> This works for me on the node running slurmrestd on port 8081:
>
> user=someuser
> curl --header "X-SLURM-USER-NAME: ${user}" --header
> "X-SLURM-USER-TOKEN: $(sudo scontrol toker username=${user}|cut
> -d='=
You don't use the prefix.
This works for me on the node running slurmrestd on port 8081:
user=someuser
curl --header "X-SLURM-USER-NAME: ${user}" --header "X-SLURM-USER-TOKEN:
$(sudo scontrol toker username=${user}|cut -d='=' -f2-)"
http://localhost:8081/slurm/v0.0.36/ping
Brian Andrus
On 6
Hello,
So far I've been unable to use slurmrestd. I'm running CentOS7 with slurm
20.11.7 from the EPEL7 repo.
I generate a token this way:
$ sudo scontrol token username=ubuntu
SLURM_JWT=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2MjM2ODA2NjUsImlhdCI6MTYyMzY3ODg2NSwic3VuIjoidWJ1bnR1In0.bNIY
