Hide Forgot
Description of problem: The apcupsd daemon sends an email alert "Communications with UPS lost" on every boot followed almost immediately by "Communications with UPS restored". The machine in question is connecting to a remote instance of apcupsd running on another machine. It appears that this problem occurs because the network interface is not up when apcupsd is started. There is no actual problem with the remote UPS or remote apcupsd. Version-Release number of selected component (if applicable): How reproducible: Every boot. Steps to Reproduce: 1. boot 2. 3. Actual results: Email alert "Communications with UPS lost" followed almost immediately by "Communications with UPS restored". Expected results: No alert unless remote apcupsd server is actually down. Additional info: The apcupsd daemon should not be started until network services are up and it's actually possible for it to connect to the remote apcupsd. This scenario did not occur prior to updating from F15 to F16.
please try if following helps: edit /lib/systemd/system/apcupsd.service and in [Unit] section, add (there will be two "After=" lines, that's ok) following line: After=network.target then reboot. Does it help?
That worked perfectly. I tried several reboots and cold boots and never saw any spurious alert emails. Thank you!
apcupsd-3.14.10-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/apcupsd-3.14.10-3.fc16
Package apcupsd-3.14.10-3.fc16: * 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 apcupsd-3.14.10-3.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1688/apcupsd-3.14.10-3.fc16 then log in and leave karma (feedback).
apcupsd-3.14.10-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.