<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">If you have problems with having the NAS as master, make it a slave, and run the </blockquote>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">NUT configuration of your choice in your PC/workstation.</blockquote>
<div dir="auto">I have done just this. I changed the Synology to a slave and made my Raspberry Pi master and the rest of my servers are slaves as well. Manuel recommnded and he is definitely right, I think that is the best way forward, especially with your discovery as to what they’re doing to NUT on Synology. I am having one issue getting the nut-server to start up automatically without failing. You have any idea what’s going on there?<br /></div>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">Those LISTEN lines were appropriate pre-systemd when NUT's startup script was launched after networking was fully enabled. I would recommend "LISTEN 0.0.0.0 3493" instead, and use firewall rules if you are trying to exclude an interface (which is likely not the case on a Pi).</blockquote>
<div dir="auto">Ok, so replace both with that or just one of the lines? I suspected one of the lines may be the problem because when I took out the second line, nut-server service wouldn’t fail, but then clients couldn’t connect.<br /></div>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">That is odd, indeed. And yes, it is certainly a permission issue but on </blockquote>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">the journal files which reside below /var/log , not on the config files</blockquote>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;"><br /></blockquote>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">Start with journactl -x as it might say more about the error. And maybe </blockquote>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">verify if any log file is defined by the nut-server unit.</blockquote>
<div dir="auto">I tried journalctl -x and got a huge list, couldn’t even find where nut-service was in there. I tried...<br />
<br />
sudo journalctl -x | grep "nut-server"<br />
sudo journalctl -x | grep “error"<br />
<br />
And got a few interesting things, but not very descriptive...<br />
<a href="https://hastebin.com/ikupojorav.sql" target="_blank">https://hastebin.com/ikupojorav.sql</a><br />
<br />
Do you think it may that line upsd.conf like Charles mentioned?<br />
<br />
Thanks everyone for all the help!!!<br />
<br />
Regards,<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 12, 2020, 12:44 PM -0400, Tim Dawson <tadawson@tpcsvc.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;">555 gives no write access to the dir, and the files are covered by their<br />
own perms, so I fail to see any relevance to your comment - sorry . . .<br />
<br />
640 is decent for files, not so much for directories - as noted, the<br />
fields mean different things on dirs . . .<br />
<br />
From the man pages:<br />
<br />
The letters rwxXst select file mode bits for the affected<br />
users: read<br />
(r), write (w), execute (or search for directories) (x),<br />
execute/search<br />
only if the file is a directory or already has execute<br />
permission for<br />
some user (X), set user or group ID on execution (s),<br />
restricted dele-<br />
<br />
So while direct access may well still work, there is *ZERO* liability in<br />
allowing search, and frankly, I don't know what tests NUT may be doing<br />
to find it's files pre-open, and some may block without that attribute .<br />
. .<br />
<br />
For what it's worth . . .<br />
<br />
- Tim<br />
<br />
<br />
On 08/12/2020 03:08 AM, Manuel Wolfshant wrote:<br />
<blockquote type="cite">On 8/12/20 8:10 AM, Tim Dawson wrote:<br />
<blockquote type="cite">For directory permissions, the "x" priv determines if you can access<br />
the directory, so going from 555 (r-x,r-x,r-x) to 640 (rw-,r--,---)<br />
pretty much locks out access to the dir. Myself, I'd go back to 555.<br />
640 essentially locks the group "nut" out . . .<br />
<br />
- Tim<br /></blockquote>
<br />
At least if on Todd's system the access rights are identical to mine,<br />
no, nut is just fine with 640 because the whole directory is owned by<br />
group nut. And nut ( or anyone else but root, actually ) has no<br />
business in modifying the config files. Actually I'd be quite<br />
concerned if user "nut" wanted to modify its own config.<br />
<br />
Logs are written somewhere else.<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<br /></blockquote>
<br />
--<br />
Tim Dawson<br />
<br />
972-567-9360<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>
</body>
</html>