Thanks Manuel. I’m following that guide but am now stuck when checking to make sure the nut-sever and nut-client are up and working. I got this:
proton@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 22:13:42 EDT; 1min 18s ago Process: 1537 ExecStart=/sbin/upsd (code=exited, status=1/FAILURE) Warning: some journal files were not opened due to insufficient permissions. proton@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: failed (Result: exit-code) since Tue 2020-08-11 22:13:42 EDT; 1min 50s ago Process: 1543 ExecStart=/sbin/upsmon (code=exited, status=1/FAILURE) Warning: some journal files were not opened due to insufficient permissions. Do I have incorrect permission on the conf files? I did change this a while back. Why should the default permissions be on the nut folder and the files in the nut folder? I changed from 555 to 640 I believe. proton@proton:~$ sudo ls -la /etc/nut total 60 drw-r----- 2 root nut 4096 Aug 11 22:13 . drwxr-xr-x 147 root root 12288 Aug 11 22:02 .. -rw-r----- 1 root nut 1543 Aug 11 22:13 nut.conf -rw-r----- 1 root nut 5615 Aug 11 21:59 ups.conf -rw-r----- 1 root nut 4601 Aug 11 22:04 upsd.conf -rw-r----- 1 root nut 2466 Aug 11 22:09 upsd.users -rw-r----- 1 root nut 15479 Aug 11 22:12 upsmon.conf -rw-r----- 1 root nut 3879 Feb 8 2020 upssched.conf -- Todd Benivegna // [email protected] On Aug 11, 2020, 9:09 PM -0400, Manuel Wolfshant <[email protected]>, wrote: > On 8/12/20 3:55 AM, Todd Benivegna wrote: > > Manuel, > > > > You are absolutely right. I think this is all the Synology just being > > very dumb. I guess those are my only two options at this point. > > > > I have no idea on how to set up the NUT server though on one of my > > NUCs or my Pi. Do you know any good guides out there? > > there are literally tons of guides. for instance: > > https://www.reddit.com/r/homelab/comments/5ssb5h/ups_server_on_raspberry_pi/ > and scroll down to configuring, past the apt install step (which you > already did ) > > basically all you need is to edit a few files below /etc/nut/ . takes 5 > min top > > > > I’m guessing it’s easy enough to edit upsmon.conf on the Synology in > > order to get that to become a slave; I think would be all that’s > > required for the Synology NAS. > > > > Yeah I saw that. Makes no sense. I can Wireshark it, however even if > > I find the cause, I’d still have to go to Synology for resolution, > > which I doubt will ever get fixed. Even if they do, I doubt it’d be > > any time soon. Maybe that’s me being pessimistic, I don’t know, but I > > just don’t if I have the time or energy for all that! > > > no need to wireshark any more, we already know that it sends bogus FSD > > > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
