On 2/5/2014 8:24 AM, Charles Lepple wrote:
On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote:
NUT will complain endlessly about communication errors and never establish SNMP
communication with my APC UPS
Hmm, at first glance, I read the "complain endlessly" part as a figure of
speech, and figured SNMP would get there eventually since it's UDP. But if you have to
stop and restart NUT, that is a different story
Sorry about the time warp on this. I had some issues in my office and
wasn't running the box for a while. Here is the actual error:
Feb 16 10:15:40 freenas upsmon[2939]: UPS [CR-UPS]: connect failed:
Connection failure: Connection refused
Feb 16 10:16:15 freenas last message repeated 7 times
Feb 16 10:18:17 freenas last message repeated 24 times
Feb 16 10:19:38 freenas last message repeated 16 times
And the subsequent messages are what I mean about complaining endlessly.
Stopping and restarting the UPS service (nut) resolves the problem as
follows:
Feb 16 10:20:13 freenas notifier: Detected SMART-UPS 5000 RM DL4 on host
192.168.253.32 (mib: apcc 1.2)
Feb 16 10:20:13 freenas notifier: [CR-UPS] Warning: excessive poll
failures, limiting error reporting
Feb 16 10:20:15 freenas notifier: [CR-UPS] Warning: excessive poll
failures, limiting error reporting
Feb 16 10:20:17 freenas notifier: Network UPS Tools - UPS driver
controller 2.6.5
Feb 16 10:20:17 freenas notifier: Starting nut.
Feb 16 10:20:17 freenas notifier: listening on 0.0.0.0 port 3493
Feb 16 10:20:17 freenas notifier: Connected to UPS [CR-UPS]: snmp-ups-CR-UPS
Feb 16 10:20:17 freenas notifier: Starting nut_upsmon.
Feb 16 10:20:17 freenas notifier: UPS: CR-UPS (master) (power value 1)
Feb 16 10:20:17 freenas notifier: Starting nut_upslog.
Hopefully that makes what I meant more clear.
Thanx,
EBD
_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
