Check_UPS with nut errors

[Jeff McKeon]

I'm using check_ups in conjunction with nut 1.2.1.

My /var/log/messages log is filling up with hundreds of entries like
this..

Feb 26 15:06:59 MIS01TC07927 upsd[1008]: Host 127.0.0.1 disconnected
(read failure)
Feb 26 15:06:59 MIS01TC07927 upsd[1008]: Connection from 127.0.0.1

Every 2 minutes.

Any idea what is causing this?  How can I track this down?

If I initiate a restart using ups_reset I get the following

[root at MIS01TC07927 etc]# ./ups_reset
stoping upsd and driver

Network UPS Tools - UPS driver controller 1.2.1
Stopping UPS: ups0-1
Stopping UPS: ups1-1
Stopping UPS: ups1-2
Stopping UPS: ups2-1
Stopping UPS: ups2-2
Starting Driver and upsd

Network UPS Tools - UPS driver controller 1.2.1
Network UPS Tools - APC Smart protocol driver 0.60 (1.2.1)
Detected Smart-UPS 1400 RM [AS0118110337] on /dev/ttyCP0 (level 3)
Network UPS Tools - APC Smart protocol driver 0.60 (1.2.1)
Detected SMART-UPS 2200 RM [XS0129002019] on /dev/ttyS0 (level 3)
Network UPS Tools - APC Smart protocol driver 0.60 (1.2.1)
Detected SMART-UPS 2200 RM [XS0129002010] on /dev/ttyCP1 (level 3)
Network UPS Tools - APC Smart protocol driver 0.60 (1.2.1)
Detected SMART-UPS 2200 RM [XS0129002014] on /dev/ttyCP2 (level 3)
Network UPS Tools - APC Smart protocol driver 0.60 (1.2.1)
Detected SMART-UPS 2200 RM [XS0129002012] on /dev/ttyCP3 (level 3)
Network UPS Tools upsd 1.2.1
Can't bind to socket: Address already in use

What's with the bind to socket error?

Thanks,

Jeff


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null