Description of problem: I'm not sure if this is a bug in the systemd triggers, rpm, or something else. In the chronyd unit file the PIDFile has changed recently, but this change is not respected on package upgrades, which results in a timeout and systemd killing the daemon. It seems the problem is that the systemd trigger which runs "systemctl daemon-reload" is called after chrony's %postun, which calls "systemctl try-restart", so systemd doesn't see the new PIDFile when the service is restarted. Version-Release number of selected component (if applicable): systemd-239-3.fc29.x86_64 How reproducible: always Steps to Reproduce: 1. install chrony-3.3-1.fc29 2. start chronyd 3. update to chrony-3.3-4.fc29 Actual results: slow rpm transaction, timeout, and chronyd is killed Expected results: no timeout, chronyd stays running Additional information: From an rpm log: D: %triggerun(systemd-239-3.fc29.x86_64): execv(/bin/sh) pid 7867 D: Plugin: calling hook scriptlet_fork_post in selinux plugin D: setexecfilecon: (/bin/sh) + test -d /run/systemd/system + mkdir -p /var/lib/rpm-state/systemd + touch /var/lib/rpm-state/systemd/needs-reload D: %triggerun(systemd-239-3.fc29.x86_64): waitpid(7867) rc 7867 status 0 ... D: %postun(chrony-3.3-1.fc29.x86_64): execv(/bin/sh) pid 7878 D: Plugin: calling hook scriptlet_fork_post in selinux plugin D: setexecfilecon: (/bin/sh) + '[' 1 -ge 1 ']' + systemctl try-restart chronyd.service + : D: %postun(chrony-3.3-1.fc29.x86_64): waitpid(7878) rc 7878 status 0 ... D: %triggerin(systemd-239-3.fc29.x86_64): execv(/bin/sh) pid 7917 D: Plugin: calling hook scriptlet_fork_post in selinux plugin D: setexecfilecon: (/bin/sh) + test -d /run/systemd/system + /usr/bin/systemctl daemon-reload D: %triggerin(systemd-239-3.fc29.x86_64): waitpid(7917) rc 7917 status 0
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
*** Bug 1715737 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I can still reproduce this on Fedora 31, even when I rebuild the new package to use the current systemd macros.
Just repeating the analysis from 1715737: Zbigniew Jędrzejewski-Szmek 2019-05-31 08:34:00 UTC We recently changes systemd macros to not silence warnings (they used to be redirected to /dev/null, now they are not). Unfortunately this shows that there is a problem, and the warnings are valid: 'systemctl try-restart' is called during package's %postun, and 'systemctl daemon-reload' is called later, during %transfiletriggerin. It seems the whole scheme is broken ;(, and the recent change simply uncovered the error. So the whole move of to file triggers for "systemctl daemon-reload" is non-functional, this seems like serious bug to me.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://github.com/systemd/systemd/pull/18481
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
systemd now supports marking services for restart and restarting them at the end of the transaction. From systemd-248-rc1 NEWS entry: Units acquired a new property "Markers" that takes a list of zero, one or two of the following strings: "needs-reload" and "needs-restart". These markers may be set via "systemctl set-property". Once a marker is set, "systemctl reload-or-restart --marked" may be invoked to execute the operation the units are marked for. This is useful for package managers that want to mark units for restart/reload while updating, but effect the actual operations at a later step at once. Systemd rpm macros and transfiletriggers have been adjusted to make use of this. Unfortunately I missed the mass rebuild with this, so macros in individual packages have not been rebuilt. I'll open a fesco ticket to ask for a target rebuild to update the macros. I'll close this here, since $subject is fixed. We need to fix individual packages, but I don't need to track this in bugzilla.