<div dir="ltr"><div>My environment is a little different, but I'm seeing at least the client working without issue on CentOS 7.</div><div><br></div>On CentOS 7.2 I also used the epel repository and installed nut-client; currently nut-client-2.7.2-3.el7.x86_64 The only configuration change was to update the /etc/ups/upsmon.conf file with the appropriate MONITOR statement. Other than that, normal enabling and starting the service was sufficient to have it work properly. The CentOS systems are installed from the minimal image and have a small set of KVM virtualization packages installed. In my environment, the nut server runs on a Raspberry Pi, so only the client is needed on the other systems.<br><div><br></div><div>--Larry</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 25, 2016 at 10:20 AM, Mark Hansen <span dir="ltr"><<a href="mailto:meh@winfirst.com" target="_blank">meh@winfirst.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I'm configuring the NUT package which comes with CentOS 7.X:<br>
<br>
nut.x86_64 2.7.2-3.el7 @epel<br>
nut-client.x86_64 2.7.2-3.el7 @epel<br>
<br>
I've configured NUT based on the instructions found on this page:<br>
<br>
<a href="https://www.luzem.com/2015/01/25/install-ups-in-centos-7/" rel="noreferrer" target="_blank">https://www.luzem.com/2015/01/<wbr>25/install-ups-in-centos-7/</a><br>
<br>
which worked, except for one problem. When starting the services (nut-server, nut-monitor)<br>
the /var/run/nut directory is not created, and so the service fails to start.<br>
<br>
If I create the directory manually, using the following commands, I can get the services<br>
to start, but upon re-boot, the directory is gone and the services fail to start again:<br>
<br>
mkdir /var/run/nut<br>
chown root:nut /var/run/nut<br>
chmod 770 /var/run/nut<br>
restorecon -v /var/run/nut<br>
<br>
I searched and it seems the issue is that /var/run is on a temporary filesystem, so stuff<br>
created there do not survive a reboot.<br>
<br>
To work around the problem, I've created a start-up script (/usr/local/sbin/rc.local) and<br>
create the directory there. This seems to work, but I'm thinking there is something wrong<br>
or missing in my configuration.<br>
<br>
What is the correct fix?<br>
<br>
Thanks,<br>
<br>
______________________________<wbr>_________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@lists.alioth.debian.org" target="_blank">Nut-upsuser@lists.alioth.debia<wbr>n.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">http://lists.alioth.debian.org<wbr>/cgi-bin/mailman/listinfo/nut-<wbr>upsuser</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div>Larry Fahnoe, Fahnoe Technology Consulting, fahnoe@FahnoeTech.com</div><div> Minneapolis, Minnesota <a href="http://www.FahnoeTech.com" target="_blank">www.FahnoeTech.com</a></div></div>
</div>