Red Hat Bugzilla – Bug 821295
systemd times out starting nut-monitor.service
Last modified: 2012-05-29 06:24:57 EDT
Description of problem:
"systemctl start nut-monitor.service" causes upsmon to start, run for a short time, and then be killed by systemd.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. systemd start nut-monitor.service
2. Wait, and watch /var/log/messages
upsmon stays running.
systemd eventually kills upsmon, saying: "nut-monitor.service operation timed out. Terminating."
upsmon claims to be unable to write to /var/run/nut/upsmon.pid, probably due to the fact that /var/run/nut does not exist. nut-monitor.service tries to create /var/run/nut using /usr/bin/systemd-tmpfiles, but systemd-tmpfiles lives in /bin, not /usr/bin.
Right, UsrMove happened on F17+ only.
nut-2.6.3-3.fc16 has been submitted as an update for Fedora 16.
nut-2.6.3-3.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nut-2.6.3-3.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
nut-2.6.3-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
nut-2.6.3-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.