nut-2.6.5-15.fc20.x86_64 was installed via yum from the Fedora Updates repo. It did not install any systemd target services and requires the user to build their own. Version-Release number of selected component (if applicable): nut-2.6.5-15.fc20.x86_64 nut-client-2.6.5-15.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. yum install nut 2. configure /etc/ups/ups.conf 3. systemctl enable upsdrvctl.service Actual results: Failed to issue method call: No such file or directory Expected results: Service enabled Additional info: With the transition to systemd, all services should install a .service component for systemd, or add themselves to default.target. nut does neither.
*** Bug 1097429 has been marked as a duplicate of this bug. ***
> 3. systemctl enable upsdrvctl.service correct name of the service is nut-driver.service but that is service started on demand. You should use nut-client.service - on machine that wants to monitor ups(es) nut-server.service - on machine that has the ups connected in most use cases you will want both nut-client.service and nut-server.service to be started
nut-2.7.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/nut-2.7.2-1.fc20
Package nut-2.7.2-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nut-2.7.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7477/nut-2.7.2-1.fc20 then log in and leave karma (feedback).
nut-2.7.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.