Hi folks,
I'm trying to get NUT installed on an existing F19 server which sits beside my shiney new APC SmartUPS. It's connected using a serial cable on ttyS0.
I've found a number of web sites that tell you how to install NUT and get it working, including one that said it worked where others didn;'t - it referred to permissions issues with the RPMs.
However, none of the instructions relate to F19 and even after making allowances I still can't get it to work. One thing that was missing was /var/run/ups which was the last thing I created. However, as you can see below, it still doesn't work.
I'm hoping eventually to have this server monitor the UPS, and then have all other servers monitor through this server.
Can anyone help with getting this working. Ta
Gary
[root@lou ups]# mkdir /var/run/nut [root@lou ups]# chown root:nut /var/run nut.conf [root@lou ups]# systemctl start nut-driver Job for nut-driver.service failed. See 'systemctl status nut-driver.service' and 'journalctl -xn' for details. [root@lou ups]# systemctl status nut-driver.service nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static) Active: failed (Result: exit-code) since Thu 2016-01-07 17:05:49 GMT; 9s ago Process: 3072 ExecStart=/sbin/upsdrvctl start (code=exited, status=1/FAILURE)
Jan 07 17:05:37 lou.ringways.co.uk upsdrvctl[3072]: Communications with UPS re-established Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Exiting. Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: APC command table version 3.0 Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Fatal error: unable to create listener socket Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: bind /var/run/nut/apcsmart-LSR1 failed: Permission denied Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Driver failed to start (exit status=1) Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Network UPS Tools - UPS driver controller 2.6.5 Jan 07 17:05:49 lou.ringways.co.uk systemd[1]: nut-driver.service: control process exited, code=exited status=1 Jan 07 17:05:49 lou.ringways.co.uk systemd[1]: Failed to start Network UPS Tools - power device driver controller. Jan 07 17:05:49 lou.ringways.co.uk systemd[1]: Unit nut-driver.service entered failed state. [root@lou ups]# journalctl -xn -- Logs begin at Thu 2014-06-05 11:52:54 BST, end at Thu 2016-01-07 17:05:49 GMT. -- Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Exiting. Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Network UPS Tools - APC Smart protocol driver 3.04 (2.6.5) Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: APC command table version 3.0 Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Fatal error: unable to create listener socket Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: bind /var/run/nut/apcsmart-LSR1 failed: Permission denied Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Driver failed to start (exit status=1) Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Network UPS Tools - UPS driver controller 2.6.5 Jan 07 17:05:49 lou.ringways.co.uk systemd[1]: nut-driver.service: control process exited, code=exited status=1 Jan 07 17:05:49 lou.ringways.co.uk systemd[1]: Failed to start Network UPS Tools - power device driver controller. -- Subject: Unit nut-driver.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 01/07/2016 09:14 AM, Gary Stainburn wrote:
[root@lou ups]# mkdir /var/run/nut [root@lou ups]# chown root:nut /var/run nut.conf
...
Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: Fatal error: unable to create listener socket Jan 07 17:05:49 lou.ringways.co.uk upsdrvctl[3072]: bind /var/run/nut/apcsmart-LSR1 failed: Permission denied
Start with: chown -v nut:nut /var/run/nut restorecon -v /var/run/nut
What do those commands output?
On Thursday 07 January 2016 17:40:51 Gordon Messmer wrote:
Start with: chown -v nut:nut /var/run/nut restorecon -v /var/run/nut
What do those commands output?
I did have to manually set up /var/run/nut and set the permissons as the RPM install didn't do that.
[root@lou ~]# chown -v nut:nut /var/run/nut ownership of ‘/var/run/nut’ retained as nut:nut [root@lou ~]# restorecon -v /var/run/nut [root@lou ~]#
I'm going to try Kevin's suggestion and look at apcupsd. Does this allow me to use this ove a network, i.e. allow other servers to monitor the status of the UPS via LOU?
On Thu, 2016-01-07 at 17:14 +0000, Gary Stainburn wrote:
However, none of the instructions relate to F19 and even after making allowances I still can't get it to work.
F19 is obsolete and unsupported, including for security patches. You really should be running at least F22, especially on a server.
poc
On Thursday 07 January 2016 20:52:32 Patrick O'Callaghan wrote:
On Thu, 2016-01-07 at 17:14 +0000, Gary Stainburn wrote:
However, none of the instructions relate to F19 and even after making allowances I still can't get it to work.
F19 is obsolete and unsupported, including for security patches. You really should be running at least F22, especially on a server.
poc
I am fully aware of this. However, it is a headless server, in the secure area of my network, performing a specific and specialised task, and is physically next to the UPS.
Your answer helps in no way whatsoever, but thanks anyway.
It does seem that nut is a bit of a problem to install
On 01/07/16 12:14, Gary Stainburn wrote:
Hi folks,
I'm trying to get NUT installed on an existing F19 server which sits beside my shiney new APC SmartUPS. It's connected using a serial cable on ttyS0.
If its an APC UPS, shouldn't you be using apcupsd instead of nut? Its a standard fedora package. The last time I was running an APC UPS, I installed it, made a few edits to the configuration file, and it just worked.
I've found a number of web sites that tell you how to install NUT and get it working, including one that said it worked where others didn;'t - it referred to permissions issues with the RPMs.
However, none of the instructions relate to F19 and even after making allowances I still can't get it to work. One thing that was missing was /var/run/ups which was the last thing I created. However, as you can see below, it still doesn't work.
I'm hoping eventually to have this server monitor the UPS, and then have all other servers monitor through this server.
Can anyone help with getting this working. Ta
Gary
-
Gary Stainburn -
Gordon Messmer -
Kevin Cummings -
Patrick O'Callaghan