[slurm-users] log rotation for slurmctld.

Marcus Wagner wagner at itc.rwth-aachen.de
Fri Mar 13 14:14:11 UTC 2020

hi all,

by concidence, I have stumbled today over the troubleshooting slides 
from slug 2019.

SchedMD there explicitly tells us to use SIGUSR2 instead of restart / 
reload / reconfig / SIGHUP.

Please compare


Around slide 22 or so.


On 3/13/20 2:27 PM, Bjørn-Helge Mevik wrote:
> navin srivastava <navin.altair at gmail.com> writes:
>> can i move the log file  to some other location and then restart.reload of
>> slurm service will start a new log file.
> Yes, restarting it will start a new log file if the old one is moved
> away.  However, also reconfig will do, and you can trigger that by
> sending the process a HUP signal.  That way you don't have to restart
> the daemon.  We have this in our logrotate file:
>      postrotate
>          ## Using the newer feature of reconfig when getting a SIGHUP.
>          kill -hup $(ps -C slurmctld h -o pid)
>          kill -hup $(ps -C slurmdbd h -o pid)
>      endscript
> (That is for both slurmctld.log and slurmdbd.log.)

Marcus Wagner, Dipl.-Inf.

IT Center
Abteilung: Systeme und Betrieb
RWTH Aachen University
Seffenter Weg 23
52074 Aachen
Tel: +49 241 80-24383
Fax: +49 241 80-624383
wagner at itc.rwth-aachen.de

More information about the slurm-users mailing list