Hi, On Mon, Feb 23, 2015 at 10:58:12AM -0500, Matthew Gabeler-Lee wrote: > Unfortunately this bug is still present. A virgin install of nut-client > results in a service start failure and thus package install failure. > > $ sudo systemctl status nut-monitor.service > ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown > controller > Loaded: loaded (/lib/systemd/system/nut-monitor.service; disabled) > Active: failed (Result: resources) since Mon 2015-02-23 10:56:03 EST; 1min > 3s ago > Process: 7398 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS) > > Feb 23 10:56:03 harkonnen upsmon[7398]: upsmon disabled, please adjust the > configuration to your needs > Feb 23 10:56:03 harkonnen upsmon[7398]: Then set MODE to a suitable value in > /etc/nut/nut.conf to enable it > Feb 23 10:56:03 harkonnen systemd[1]: Failed to start Network UPS Tools - > power device monitor and shutdown controller. > Feb 23 10:56:03 harkonnen systemd[1]: Unit nut-monitor.service entered failed > state.
I can reproduce the problem as well: # systemctl status nut-monitor.service ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller Loaded: loaded (/lib/systemd/system/nut-monitor.service; disabled) Active: failed (Result: resources) since Sun 2015-03-01 13:16:49 CET; 8s ago Process: 25872 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS) Mar 01 13:16:49 whisky upsmon[25872]: upsmon disabled, please adjust the configuration to your needs Mar 01 13:16:49 whisky upsmon[25872]: Then set MODE to a suitable value in /etc/nut/nut.conf to enable it Mar 01 13:16:49 whisky systemd[1]: PID file /var/run/nut/upsmon.pid not readable (yet?) after start. Mar 01 13:16:49 whisky systemd[1]: Failed to start Network UPS Tools - power device monitor and shutdown controller. Mar 01 13:16:49 whisky systemd[1]: Unit nut-monitor.service entered failed state. That is, the problem is that systemd will still expect /var/run/nut/upsmon.pid to be present after attempting to start upsmon. I think that MODE=none should no longer be a valid option when using systemd as you'd then use 'systemctl disable' instead. I don't know systemd very well, so there could be other options as well and/or maybe a way to disable upsmon in systemd by default after installing it. Anyway, I tend to think that dropping systemd support might still be a good option but you should talk to the release team before. It would be great if we can get a fix into testing as a removal would affect other packages (e.g. collectd) as well. Let me know if I can help. Thanks, Sebastian -- Sebastian "tokkee" Harl +++ GnuPG-ID: 0x2F1FFCC7 +++ http://tokkee.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
signature.asc
Description: Digital signature
