Description of problem: While the nut packages are being upgraded with yum, an alarming "Communications with UPS lost" message sometimes gets wall'ed to the console. It appears this happens because nut-server.service is stopped while nut-monitor.service is still running. To avoid these spurious errors during upgrades, I believe it should stop/start the services in a specific order: 1. Stop nut-monitor 2. Stop nut-server 3. Stop nut-driver 4. Start nut-server (pulls in nut-driver automatically) 5. Start nut-monitor Version-Release number of selected component (if applicable): 2.6.5-6.fc17
Unfortunately, this is not that easy. nut-monitor and nut-server does not have to be running on the same system. They are split to two packages and we can't affect in what order packages are updated by yum. I'll try to come up with some solution.
nut-2.6.5-9.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/nut-2.6.5-9.fc18
nut-2.6.5-12.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/nut-2.6.5-12.fc19
Package nut-2.6.5-12.fc19: * should fix your issue, * was pushed to the Fedora 19 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.5-12.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6351/nut-2.6.5-12.fc19 then log in and leave karma (feedback).
nut-2.6.5-9.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
nut-2.6.5-12.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.