[Nut-upsuser] Synology NAS is shutting down Ubuntu servers after very brief power outage (fwd)

[Manuel Wolfshant]

On 8/12/20 7:11 AM, Todd Benivegna wrote:
> Ok, so just a follow-up to my last email; still following that guide, 
> which is great…. Just stuck on getting the nut-server service starting 
> automatically.  Got everything else working.  I’ve been able to get 
> the nut-client starting up automatically at boot up (I had a missing 
> “1” in upsmon.conf.  Oooops!)  However, I cannot get nut-server 
> service to start-up automatically still.
>
> proton at proton:~$ service nut-server status
> nut-server.service - Network UPS Tools - power devices information server
>      Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; 
> vendor preset: enabled)
>      Active: failed (Result: exit-code) since Tue 2020-08-11 23:43:55 
> EDT; 2min 0s ago
>     Process: 1559 ExecStart=/sbin/upsd (code=exited, status=1/FAILURE)
>
>
> proton at proton:~$ service nut-client status
> nut-monitor.service - Network UPS Tools - power device monitor and 
> shutdown controller
>      Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; 
> vendor preset: enabled)
>      Active: active (running) since Tue 2020-08-11 23:43:55 EDT; 2min 
> 7s ago
>     Process: 1567 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)
>    Main PID: 1570 (upsmon)
>       Tasks: 2 (limit: 9019)
>      CGroup: /system.slice/nut-monitor.service
> 1569 /lib/nut/upsmon
> 1570 /lib/nut/upsmon
> Warning: some journal files were not opened due to insufficient 
> permissions.
>
>
> I can get it to start manually by doing "sudo service nut-server 
> restart".  Then it starts up…. Just starts up and all is good.
>
>
> proton at proton:~$ sudo service nut-server status
> nut-server.service - Network UPS Tools - power devices information server
>      Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; 
> vendor preset: enabled)
>      Active: active (running) since Tue 2020-08-11 23:49:50 EDT; 12s ago
>     Process: 2949 ExecStart=/sbin/upsd (code=exited, status=0/SUCCESS)
>    Main PID: 2950 (upsd)
>       Tasks: 1 (limit: 9019)
>      CGroup: /system.slice/nut-server.service
> 2950 /lib/nut/upsd
> Aug 11 23:49:50 proton upsd[2949]: listening on 127.0.0.1 port 3493
> Aug 11 23:49:50 proton upsd[2949]: listening on 127.0.0.1 port 3493
> Aug 11 23:49:50 proton upsd[2949]: Connected to UPS [ups]: usbhid-ups-ups
> Aug 11 23:49:50 proton upsd[2949]: Connected to UPS [ups]: usbhid-ups-ups
> Aug 11 23:49:50 proton upsd[2950]: Startup successful
> Aug 11 23:49:50 proton systemd[1]: Started Network UPS Tools - power 
> devices information server.
> Aug 11 23:49:50 proton upsd[2950]: User upsmon_local at 127.0.0.1 logged 
> into UPS [ups]
> Aug 11 23:49:51 proton upsd[2950]: User monuser at 192.168.1.70 logged 
> into UPS [ups]
> Aug 11 23:49:53 proton upsd[2950]: User upsmon_remote at 192.168.1.30 
> logged into UPS [ups]
> Aug 11 23:49:53 proton upsd[2950]: User upsmon_remote at 192.168.1.20 
> logged into UPS [ups]
>
>
>
> Here is my upsd.conf:
>
> LISTEN 127.0.0.1 3493
> LISTEN 192.168.1.31 3493
>
>
>
> Could it be a permissions issue?  Weird that all it takes is me 
> manually doing "sudo service nut-server restart” is all it 
> takes.  Clients connect and everything.


That is odd, indeed. And yes, it is certainly a permission issue but on 
the journal files which reside below /var/log , not on the config files

Start with journactl -x as it might say more about the error. And maybe 
verify if any log file is defined by the nut-server unit.

M.