Long ago, Nostradamus foresaw that on 01/19/2012 07:35 AM, Michal Hlavinka would write: >>> Yes, on Fedora 16, you have to start nut-server before nut-monitor, and >>> systemd tries to start them at once. Haven't got around to >>> reporting that. >>> I don't think this problem is fortress specific. > it *should* work :) >> quickly looking at the service files, nut-monitor is marked to be >> started after nut-server, and nut-server after nut-driver >> so you may be hitting a systemd bug. > could you please provide part from /var/log/messages, where > nut-{driver,server} are being started? Also what systemd and nut > version do you have (together with release number) ? rpm -q nut systemd After boot, only upsmon is running (and whining about no server) and messages contains:
Jan 21 12:53:30 melissa systemd[1]: Service nut-driver.service is not needed anymore. Stopping. Jan 21 12:53:30 melissa systemd[1]: Requested transaction contradicts existing jobs: File exists I can then manually start nut-server.service. Status is then: # systemctl status nut-server.service nut-server.service - Network UPS Tools - power devices information server Loaded: loaded (/lib/systemd/system/nut-server.service; enabled) Active: active (running) since Sat, 21 Jan 2012 15:33:30 -0500; 2min 26s ago Process: 6259 ExecStart=/usr/sbin/upsd (code=exited, status=0/SUCCESS) Main PID: 6260 (upsd) CGroup: name=systemd:/system/nut-server.service └ 6260 /usr/sbin/upsd # rpm -q nut systemd nut-2.6.2-2.fc16.i686 systemd-37-3.fc16.i686 > There is one bug in systemd, that breaks driver-server relation: > https://bugzilla.redhat.com/show_bug.cgi?id=704197, it was fixed > recently, but it's still not available as update. _______________________________________________ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev