Package: slurmdbd
Version: 18.08.5.2-1
Followup-For: Bug #885759
Dear Maintainer,
The update to slurm 18.08.5.2-1 was supposed to move pid files of slurm
daemons from /var/run/slurm-llnl/ to /run/.
During the update apt promised to correct configuration files to update
pid path to /run (if it was set in the config).
However, this did not happen.
What happened is that config files (slurm.conf, slurmdbd.conf) still
contain pid paths in /run/slurm-llnl/. Note: not /var/run/slurm-llnl/ but
/run/slurm-llnl in my case.
These are respected by slurm processes (pid files still generated in
/run/slurm-llnl/), but systemd tries to access pids in /run/, stalling the
restart and failing it after a timeout.
This renders all slurm daemons fail to start and requires a manual edit to
config files. I.e. the update does not go smoothly as promised.
Apt did modify the config files, because it is visible in the modification
date, not a single byte changed. Old paths are still there:
PidFile=/run/slurm-llnl/slurmdbd.pid
Hint: maybe a wrong regex to match paths? Maybe only /var/run but not /run
is updated?
Since the pid is hardcoded in systemd unit configs, then imo it is better
to remove the pid file entries altogether from slurm config files.
Met
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd64 (SMP w/64 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages slurmdbd depends on:
ii libc6 2.28-7
ii lsb-base 10.2018112800
ii munge 0.5.13-2
ii slurm-wlm-basic-plugins 18.08.5.2-1
ii ucf 3.0038+nmu1
slurmdbd recommends no packages.
slurmdbd suggests no packages.
-- no debconf information
