FS#57432 - [systemd] Stricter PIDfile handling breaks several daemons
Attached to Project:
Arch Linux
Opened by Bert Peters (bertptrs) - Thursday, 08 February 2018, 10:47 GMT
Last edited by Christian Hesse (eworm) - Friday, 09 February 2018, 21:08 GMT
Opened by Bert Peters (bertptrs) - Thursday, 08 February 2018, 10:47 GMT
Last edited by Christian Hesse (eworm) - Friday, 09 February 2018, 21:08 GMT
|
Details
Description:
Starting systemd 237, it considers root-owned PID-files placed in non-root owned folders insecure, and does not acknowledge them. This results in a timeout on the service start, either causing a restart (when configured) or just the service to be killed off. The issue has been originally noticed in Debian Sid [1] and has been already been reported upstream [2]. I am reporting this issue here anyway since it might be helpful in debugging random other daemons failing. Additional info: * This affects systemd 237 and up * dnsmasq and munin-node are affected, probably others. Steps to reproduce: - Update your system - Start munin-node (or similar) - Observe journal entries similar to the attached ones. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144 [2] https://github.com/systemd/systemd/issues/8085 |
This task depends upon
Closed by Christian Hesse (eworm)
Friday, 09 February 2018, 21:08 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 237.31-1
Friday, 09 February 2018, 21:08 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 237.31-1
Comment by loqs (loqs) - Friday, 09
February 2018, 17:18 GMT
Check has been relaxed slightly
https://github.com/systemd/systemd/commit/73969ab61c39357e6892747e43307fbf07cafbed