Re: [slurm-users] slurmrestd service broken by 22.05.07 update

2022-12-29 Thread Chris Stackpole
8081 only (no socket and not 6820) I was then able to just use curl on port 8081 to test things. Hope that helps. Brian Andrus On 12/29/2022 6:49 AM, Chris Stackpole wrote: Greetings, Thanks for responding! On 12/28/22 20:35, Brian Andrus wrote: I suspect if you delete /var/lib/slurmrestd.so

Re: [slurm-users] slurmrestd service broken by 22.05.07 update

2022-12-29 Thread Chris Stackpole
Greetings, Thanks for responding! On 12/28/22 20:35, Brian Andrus wrote: I suspect if you delete /var/lib/slurmrestd.socket and then start slurmrestd, it will create it as the user you need it to be. Or just change the owner of it to the slurmrestd owner. No go on that. Because /var/lib re

[slurm-users] slurmrestd service broken by 22.05.07 update

2022-12-28 Thread Chris Stackpole
Greetings, After updating to 22.05.07 (manually built from source)... slurmrestd[68695]: fatal: _create_socket: [unix:/var/lib/slurmrestd.socket] Unable to bind UNIX socket: Permission denied Looking at release notes: > -- slurmrestd - switch users earlier on startup to avoid sockets being