Package: sanlock
Severity: important
Justification: renders package unusable
Dear Maintainer,
thank you for maintaining the sanlock package. I may have found a version
mismatch in the included wdmd.service file and a lib.
* What led up to the situation?
Try to start the wdmd.service, as it was not succesfully pulled in by
sanlock.service.
* What exactly did you do (or not do) that was effective (or
ineffective)?
systemctl start wdmd.service
* What was the outcome of this action?
Error message: Usage: /etc/init.d/wdmd {start|stop|status|restart}
* What outcome did you expect instead?
wdmd.service starts
The wdmd.service contains this line in the [Service] section:
ExecStartPre=/lib/systemd/systemd-wdmd watchdog-check
But /lib/systemd/systemd-wdmd does not support the argument "watchdog-check",
and throws an error instead.
All related files are part of the sanlock package.
I have found this behavior in
- sanlock 3.8.2-2 in Debian Bullseye
- sanlock 3.8.5-1+b1 in Debian Bookworm
Is it safe to remove the ExecStartPre= line and skip the check?
Best regards,
Lars
-- System Information:
Debian Release: 12.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'oldstable-updates'), (500, 'oldstable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-10-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sanlock depends on:
ii adduser 3.134
ii init-system-helpers 1.65.2
ii libaio1 0.3.113-4
ii libblkid1 2.38.1-5+b1
ii libc6 2.36-9
pn libsanlock1 <none>
ii libuuid1 2.38.1-5+b1
sanlock recommends no packages.
Versions of packages sanlock suggests:
pn python3-sanlock <none>
pn sanlk-reset <none>
