<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>For directory permissions, the "x" priv determines if you can access the directory, so going from 555 (r-x,r-x,r-x) to 640 (rw-,r--,---) pretty much locks out access to the dir. Myself, I'd go back to 555. 640 essentially locks the group "nut" out . . .<br><br>- Tim<br><br><div class="gmail_quote">On August 11, 2020 11:11:22 PM CDT, Todd Benivegna <todd@benivegna.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div name="messageBodySection">
<div dir="auto">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. <br>
<br>
proton@proton:~$ service nut-server status<br>
nut-server.service - Network UPS Tools - power devices information server<br>
Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)<br>
Active: failed (Result: exit-code) since Tue 2020-08-11 23:43:55 EDT; 2min 0s ago<br>
Process: 1559 ExecStart=/sbin/upsd (code=exited, status=1/FAILURE)<br>
<br>
<br>
proton@proton:~$ service nut-client status<br>
nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller<br>
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled)<br>
Active: active (running) since Tue 2020-08-11 23:43:55 EDT; 2min 7s ago<br>
Process: 1567 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)<br>
Main PID: 1570 (upsmon)<br>
Tasks: 2 (limit: 9019)<br>
CGroup: /system.slice/nut-monitor.service<br>
1569 /lib/nut/upsmon<br>
1570 /lib/nut/upsmon<br>
Warning: some journal files were not opened due to insufficient permissions.<br>
<br>
<br>
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.<br>
<br>
<br>
proton@proton:~$ sudo service nut-server status<br>
nut-server.service - Network UPS Tools - power devices information server<br>
Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)<br>
Active: active (running) since Tue 2020-08-11 23:49:50 EDT; 12s ago<br>
Process: 2949 ExecStart=/sbin/upsd (code=exited, status=0/SUCCESS)<br>
Main PID: 2950 (upsd)<br>
Tasks: 1 (limit: 9019)<br>
CGroup: /system.slice/nut-server.service<br>
2950 /lib/nut/upsd<br>
Aug 11 23:49:50 proton upsd[2949]: listening on 127.0.0.1 port 3493<br>
Aug 11 23:49:50 proton upsd[2949]: listening on 127.0.0.1 port 3493<br>
Aug 11 23:49:50 proton upsd[2949]: Connected to UPS [ups]: usbhid-ups-ups<br>
Aug 11 23:49:50 proton upsd[2949]: Connected to UPS [ups]: usbhid-ups-ups<br>
Aug 11 23:49:50 proton upsd[2950]: Startup successful<br>
Aug 11 23:49:50 proton systemd[1]: Started Network UPS Tools - power devices information server.<br>
Aug 11 23:49:50 proton upsd[2950]: User upsmon_local@127.0.0.1 logged into UPS [ups]<br>
Aug 11 23:49:51 proton upsd[2950]: User monuser@192.168.1.70 logged into UPS [ups]<br>
Aug 11 23:49:53 proton upsd[2950]: User upsmon_remote@192.168.1.30 logged into UPS [ups]<br>
Aug 11 23:49:53 proton upsd[2950]: User upsmon_remote@192.168.1.20 logged into UPS [ups]<br>
<br>
<br>
<br>
Here is my upsd.conf:<br>
<br>
LISTEN 127.0.0.1 3493<br>
LISTEN 192.168.1.31 3493<br>
<br>
<br>
<br>
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.<br>
<br>
Thanks,<br>
<br>
Todd</div>
</div>
<div name="messageSignatureSection"><br>
<p style="margin: 0px; font-stretch: normal; line-height: normal; font-family: "Helvetica Neue"; color: rgb(34, 34, 34);">--</p>
<p style="margin: 0px; font-stretch: normal; line-height: normal; font-family: "Helvetica Neue"; color: rgb(51, 51, 51);"><span style="color: #222222"><b>Todd Benivegna</b></span> <span style="color: #222222">//</span> <a href="mailto:todd@benivegna.com">todd@benivegna.com</a></p>
</div>
<div name="messageReplySection">On Aug 11, 2020, 10:29 PM -0400, Todd Benivegna <todd@benivegna.com>, wrote:<br>
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">
<div name="messageBodySection">
<div dir="auto">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:<br>
<br>
proton@proton:~$ service nut-server status<br>
nut-server.service - Network UPS Tools - power devices information server<br>
Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)<br>
Active: failed (Result: exit-code) since Tue 2020-08-11 22:13:42 EDT; 1min 18s ago<br>
Process: 1537 ExecStart=/sbin/upsd (code=exited, status=1/FAILURE)<br>
<br>
Warning: some journal files were not opened due to insufficient permissions.<br>
<br>
<br>
<br>
proton@proton:~$ service nut-client status<br>
nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller<br>
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled)<br>
Active: failed (Result: exit-code) since Tue 2020-08-11 22:13:42 EDT; 1min 50s ago<br>
Process: 1543 ExecStart=/sbin/upsmon (code=exited, status=1/FAILURE)<br>
<br>
Warning: some journal files were not opened due to insufficient permissions.<br>
<br>
<br>
<br>
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. <br>
<br>
proton@proton:~$ sudo ls -la /etc/nut<br>
total 60<br>
drw-r----- 2 root nut 4096 Aug 11 22:13 .<br>
drwxr-xr-x 147 root root 12288 Aug 11 22:02 ..<br>
-rw-r----- 1 root nut 1543 Aug 11 22:13 nut.conf<br>
-rw-r----- 1 root nut 5615 Aug 11 21:59 ups.conf<br>
-rw-r----- 1 root nut 4601 Aug 11 22:04 upsd.conf<br>
-rw-r----- 1 root nut 2466 Aug 11 22:09 upsd.users<br>
-rw-r----- 1 root nut 15479 Aug 11 22:12 upsmon.conf<br>
-rw-r----- 1 root nut 3879 Feb 8 2020 upssched.conf</div>
</div>
<div name="messageSignatureSection"><br>
<p style="margin: 0px; font-stretch: normal; line-height: normal; font-family: "Helvetica Neue"; color: rgb(34, 34, 34);">--</p>
<p style="margin: 0px; font-stretch: normal; line-height: normal; font-family: "Helvetica Neue"; color: rgb(51, 51, 51);"><span style="color: #222222"><b>Todd Benivegna</b></span> <span style="color: #222222">//</span> <a href="mailto:todd@benivegna.com">todd@benivegna.com</a></p>
</div>
<div name="messageReplySection">On Aug 11, 2020, 9:09 PM -0400, Manuel Wolfshant <wolfy@nobugconsulting.ro>, wrote:<br>
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">On 8/12/20 3:55 AM, Todd Benivegna wrote:<br>
<blockquote type="cite">Manuel,<br>
<br>
You are absolutely right. I think this is all the Synology just being<br>
very dumb. I guess those are my only two options at this point.<br>
<br>
I have no idea on how to set up the NUT server though on one of my<br>
NUCs or my Pi. Do you know any good guides out there?<br></blockquote>
<br>
there are literally tons of guides. for instance:<br>
<br>
https://www.reddit.com/r/homelab/comments/5ssb5h/ups_server_on_raspberry_pi/<br>
and scroll down to configuring, past the apt install step (which you<br>
already did )<br>
<br>
basically all you need is to edit a few files below /etc/nut/ . takes 5<br>
min top<br>
<br>
<br>
<blockquote type="cite"> I’m guessing it’s easy enough to edit upsmon.conf on the Synology in<br>
order to get that to become a slave; I think would be all that’s<br>
required for the Synology NAS.<br></blockquote>
<br>
<br>
<blockquote type="cite">Yeah I saw that. Makes no sense. I can Wireshark it, however even if<br>
I find the cause, I’d still have to go to Synology for resolution,<br>
which I doubt will ever get fixed. Even if they do, I doubt it’d be<br>
any time soon. Maybe that’s me being pessimistic, I don’t know, but I<br>
just don’t if I have the time or energy for all that!<br>
<br></blockquote>
no need to wireshark any more, we already know that it sends bogus FSD<br>
<br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
Nut-upsuser@alioth-lists.debian.net<br>
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</blockquote>
</div>
</blockquote>
</div>
</blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>