Hello, On Fri, Dec 29, 2017 at 05:58:10PM +0000, "Hattne, Johan" <hatt...@janelia.hhmi.org> wrote: > Package: slurmd > Version: 16.05.9-1+deb9u1 > > By default, slurmd writes its PID file to /var/run/slurmd.pid, but > the systemd service expects it to be at > /var/run/slurm-llnl/slurmd.pid. As a result, "systemctl start > slurmd" hangs unless slurm.conf defines > SlurmdPidFile=/var/run/slurm-llnl/slurmd.pid. This could be > synchronized by either patching the slurmd code or modifying the > service file; I’m guessing the latter is more appropriate. > --- /lib/systemd/system/slurmd.service 2017-11-05 05:26:27.000000000 > -0500 > +++ /etc/systemd/system/slurmd.service 2017-12-28 17:24:40.708918382 > -0500 > @@ -8,7 +8,7 @@ > Type=forking > EnvironmentFile=/etc/default/slurmd > ExecStart=/usr/sbin/slurmd $SLURMD_OPTIONS > -PIDFile=/var/run/slurm-llnl/slurmd.pid > +PIDFile=/var/run/slurmd.pid > > [Install] > WantedBy=multi-user.target > > I assume the same applies to the other slurm daemons. This is on > Debian 9.3.
Thank you for the bugreport and sorry for not getting back to you sooner. The fact that slurm's default do not match values from its debian package is indeed an issue and may lead to situations like the one you are describing. Though it is not necessary to change the .service file. You can specify SlurmctldPidFile, SlurmdPidFile or PidFile in the appropriate configuration files for (respectively) slurmctld, slurmd and slurmdbd. I am not going to revert changes on the run directory in the debian packaging for now (as I guess my co-maintainer had good reasons to override them), but I'll change debian's provided slurm's defaults to be coherent with the reste of the package. Regards, -- Mehdi Dogguy
