UPS - NUT - Communications with UPS lost

[IonutZ]

I'm using snmp-ups for a Smart UPS SUA3000XL with an AP9617 (UPS is connected on the network) and when I trigger a shutdown I get "Communications with UPS lost" before it gets a SHUTDOWN signal from the UPS... polling at 5s.

Also upon restarting FreeNAS, the NUT can't establish a connection with the UPS until I turn the service Off and back On.

This is what I found in /var/log/messages

Sep 6 20:24:50 nas notifier: nut not running? (check /var/db/nut/upsd.pid).
Sep 6 20:24:50 nas notifier: kill: No such process
Sep 6 20:24:50 nas notifier: No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.7'!
Sep 6 20:24:50 nas notifier: Please report it to NUT developers, with an 'upsc' output for your device.
Sep 6 20:24:50 nas notifier: Going back to the classic MIB detection method.
Sep 6 20:24:50 nas notifier: Detected Smart-UPS 3000 XL on host 10.23.1.9 (mib: apcc 1.2)
Sep 6 20:24:51 nas notifier: [APC] Warning: excessive poll failures, limiting error reporting
Sep 6 20:24:52 nas notifier: [APC] Warning: excessive poll failures, limiting error reporting
Sep 6 20:24:53 nas notifier: Network UPS Tools - UPS driver controller 2.7.1
Sep 6 20:24:53 nas notifier: Starting nut.
Sep 6 20:24:53 nas notifier: fopen /var/db/nut/upsd.pid: No such file or directory
Sep 6 20:24:53 nas notifier: listening on 127.0.0.1 port 3493
Sep 6 20:24:53 nas notifier: Connected to UPS [APC]: snmp-ups-APC
Sep 6 20:24:53 nas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Sep 6 20:24:53 nas notifier: Starting nut_upsmon.
Sep 6 20:24:53 nas notifier: kill: No such process
Sep 6 20:24:53 nas notifier: UPS: APC (master) (power value 1)
Sep 6 20:24:53 nas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Sep 6 20:24:53 nas notifier: Starting nut_upslog.​

This is what is found in /var/log/ups.log

20140906 202453 100.00 115.90 14.90 [OL] 22.90 60.00
20140906 202953 100.00 116.60 14.90 [OL] 22.50 60.00​

This indicates that nut is indeed talking to the UPS.

Any ideas?

 

[IonutZ]

Using smartapc with settings to only shutdown on low battery, I get this constantly:

UPS APC on line power


Broadcast Message from root@nas.atex.us
(no tty) at 14:01 EDT...

UPS APC battery is low


Broadcast Message from root@nas.atex.us
(no tty) at 14:01 EDT...

Executing automatic power-fail shutdown



Broadcast Message from root@nas.atex.us
(no tty) at 14:01 EDT...

UPS APC on battery


*** FINAL System shutdown message from root@nas.atex.us ***

System going down IMMEDIATELY​

Even though the UPS isn't on battery...

 

[DJ9]

You could try using apcupsd instead of NUT.

 

[IonutZ]

DJ9 how do I go about using apcupsd? Where do I install it? Jail or actual freenas? And if so in what folder?

 

[DJ9]

I just installed it via pkg.

Code:

pkg install apcupsd

You can also check out this thread if you'd like to use a different method.
http://forums.freenas.org/index.php?threads/how-do-i-install-apcupsd-in-freenas.23548/#post-143092

 

[IonutZ]

DJ9 you don't say haha. I created this thread before the other one when I was still trying to figure out nut... but I gave up on that.

 

[DJ9]

Heh, I should read better. ;)

 

[fireheadman]

slightly old thread, but replying since I am having the same output:

Code:

[root@maximus nut 759]# cat ups.conf
[maximus-ups]
	driver = snmp-ups
	port = 192.168.1.xxx
	desc = "IBM 1000t UPS"
pollfreq = 30
community = public
snmp_version = v1

Code:

Nov 27 23:19:56 maximus notifier: nut not running? (check /var/db/nut/upsd.pid).
Nov 27 23:19:56 maximus notifier: No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.7'!
Nov 27 23:19:56 maximus notifier: Please report it to NUT developers, with an 'upsc' output for your device.
Nov 27 23:19:56 maximus notifier: Going back to the classic MIB detection method.
Nov 27 23:19:56 maximus notifier: Detected IBM UPS1000TLV on host 192.168.1.5 (mib: apcc 1.2)
Nov 27 23:19:57 maximus notifier: [maximus-ups] Warning: excessive poll failures, limiting error reporting
Nov 27 23:19:59 maximus notifier: [maximus-ups] Warning: excessive poll failures, limiting error reporting
Nov 27 23:20:00 maximus notifier: Network UPS Tools - UPS driver controller 2.7.3
Nov 27 23:20:00 maximus notifier: Starting nut.
Nov 27 23:20:00 maximus notifier: fopen /var/db/nut/upsd.pid: No such file or directory
Nov 27 23:20:01 maximus notifier: listening on 127.0.0.1 port 3493
Nov 27 23:20:01 maximus notifier: Connected to UPS [maximus-ups]: snmp-ups-maximus-ups
Nov 27 23:20:01 maximus notifier: /usr/local/etc/nut/cmdvartab not found - disabling descriptions
Nov 27 23:20:01 maximus notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Nov 27 23:20:01 maximus notifier: Starting nut_upsmon.
Nov 27 23:20:01 maximus notifier: kill: No such process
Nov 27 23:20:01 maximus notifier: UPS: maximus-ups (master) (power value 1)
Nov 27 23:20:01 maximus notifier: Using power down flag file /etc/nokillpower
Nov 27 23:20:01 maximus upsmon[13099]: UPS maximus-ups battery is low
Nov 27 23:20:01 maximus notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Nov 27 23:20:01 maximus notifier: Starting nut_upslog.

The output would make it appear nut and nut_upsmon are not working, however when looking at the /var/db/nut location, I see all the pid files present.

Code:

root@maximus nut 754]# ls -la
total 24
drwxrwx---   2 root  uucp	320 Nov 27 23:20 .
drwxr-xr-x  20 root  wheel  1792 Nov 27 23:15 ..
srw-rw----   1 uucp  uucp	  0 Nov 27 23:20 snmp-ups-maximus-ups
-rw-r--r--   1 uucp  uucp	  6 Nov 27 23:20 snmp-ups-maximus-ups.pid
-rw-r--r--   1 uucp  uucp	  6 Nov 27 23:20 upsd.pid
-rw-r--r--   1 root  uucp	  6 Nov 27 23:20 upslog.pid
-rw-r--r--   1 root  uucp	  6 Nov 27 23:20 upsmon.pid

Wondering if part of nut or whatever script is checking for procs/pids needs to be slowed down a second to allow for the pid files to populate?

battery is low since I just performed a runtime-calibration, ups is slowly recharging... which I might be replacing the batteries after this since they are 2+ years old already. Originally I was using the Shutdown when batteries are low, but that instantly would trigger a shutdown. I currently have it set to Shutdown if power outage occurs but restored within 420 sec (7min).