On 09-09-2020 13:26, Ole Holm Nielsen wrote:
On 09-09-2020 11:58, Andrew Elwell wrote:
As an aside, I've seen on one of the talk slides that using systemctl
reload is a Bad Thing to do with logrotation for slurm - Simply send
SIGUSR2 (or HUP for pre-17.11 versions apparently)
https://bugs.schedm
On 09-09-2020 11:58, Andrew Elwell wrote:
As an aside, I've seen on one of the talk slides that using systemctl
reload is a Bad Thing to do with logrotation for slurm - Simply send
SIGUSR2 (or HUP for pre-17.11 versions apparently)
https://bugs.schedmd.com/show_bug.cgi?id=4393
See also the last
As an aside, I've seen on one of the talk slides that using systemctl
reload is a Bad Thing to do with logrotation for slurm - Simply send
SIGUSR2 (or HUP for pre-17.11 versions apparently)
https://bugs.schedmd.com/show_bug.cgi?id=4393
Andrew
Hello,
This seems to imply you had some changes in your slurm.conf
I'm presuming you are running Centos 7 or such.
Do you see anything when you do 'journalctl -u slurmctld'
I'm wondering if you were only logging to the journal and then added the
bits to also/instead log to a separate file.
I d
