nut updated to 2.7.4
This update has been submitted for testing by mhlavink.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Error: Package: nut-client-2.7.4-1.el7.x86_64 (epel-testing)
That's one of the reasons I removed that dep :)
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
mhlavink edited this update.
Karma has been reset.
ok, too trusting with MR, -2.el7 is bad too, here comes -3.el7
This update can be pushed to stable now if the maintainer wishes
After the update from nut-2.7.2-4.el7.x86_64 I got many errors like
upsmon: Poll UPS [UPS@127.0.0.1] failed - Driver not connected
upsd: Can't connect to UPS [UPS] (apcsmart-UPS): No such file or directory
The /run/nut directory contains only upsmon.pid. I was expecting the "apcsmart-UPS" socket file too...
To recover, I stopped/started the nut-monitor and nut-server individually.
I suspect a conflict in the Systemd unit configuration. The line
ExecStartPre=-/usr/bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/nut-run.conf
is present in both nut-driver (started by nut-server) and nut-monitor units. According to nut-run.conf contents and the tmpfiles.d man page the "D" flag (Create or empty a directory) could raise the conflict. Maybe "d" is better?
I saw that other RPMs create their directory under /run during the installation, whilst systemd-tmpfiles creates it during the system boot. See also https://fedoraproject.org/wiki/Packaging:Tmpfiles.d
Using the client since Dec 2020 without pb. As of yesterday I also have a server. Everything works for me.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.