[Nut-upsuser] Problem installing NUT on 16.04
jack at greendesk.net
Sat Dec 10 16:23:58 UTC 2016
On 12/10/2016 08:37 AM, Jack McGee wrote:
> On 12/10/2016 08:10 AM, Jack McGee wrote:
>> e, the path of least resistance would be to listen on 0.0.0.0 and use
>> a firewall rule to limit connections to that subnet.
>> sorry, after reboot I started seeing this error in terminal:
>> Broadcast message from nut at amethi (somewhere) (Sat Dec 10 08:05:01
>> UPS CyberUPS1 at localhost is unavailable
>> I had a similar issue I think when Ubuntu moved to SystemD with
>> Mythtv not waiting to start until network was up and then erroring.
>> I will see if I can recall what I did to fix that and apply it to NUT
>> and see if that fixes it.
> Restart of nut-server after boot, fixes it:
> mythuser at amethi:~$ sudo systemctl status nut-server.service
> [sudo] password for mythuser:
> ● nut-server.service - LSB: Network UPS Tools initscript
> Loaded: loaded (/etc/init.d/nut-server; bad; vendor preset: enabled)
> Active: active (running) since Sat 2016-12-10 08:35:17 CST; 17s ago
> Docs: man:systemd-sysv-generator(8)
> Process: 16600 ExecStop=/etc/init.d/nut-server stop (code=exited,
> Process: 16643 ExecStart=/etc/init.d/nut-server start (code=exited,
> CGroup: /system.slice/nut-server.service
> ├─16651 /lib/nut/usbhid-ups -a CyberUPS1
> └─16653 /lib/nut/upsd
> Dec 10 08:35:17 amethi nut-server: * Starting NUT - power
> devices information server and drivers
> Dec 10 08:35:17 amethi usbhid-ups: Startup successful
> Dec 10 08:35:17 amethi upsd: listening on 192.168.0.105 port 3493
> Dec 10 08:35:17 amethi upsd: listening on 127.0.0.1 port 3493
> Dec 10 08:35:17 amethi upsd: Connected to UPS [CyberUPS1]:
> Dec 10 08:35:17 amethi upsd: Startup successful
> Dec 10 08:35:17 amethi nut-server: ...done.
> Dec 10 08:35:17 amethi systemd: Started LSB: Network UPS Tools
> Dec 10 08:35:21 amethi upsd: User upsmon at 192.168.0.106 logged
> into UPS [CyberUPS1]
> Dec 10 08:35:21 amethi upsd: User upsmon at 127.0.0.1 logged into
> UPS [CyberUPS1]
I put 0.0.0.0 in and took out 192.168.0.105 and on restart it works.
The nut-server runs, and nut-client on another machine can reach it.
This is not opened up to outside world so I should be OK until I figure
out how to delay it until network is up.
More information about the Nut-upsuser