[Nut-upsuser] Configuring a server without an UPS attached

[Charles Lepple]

On Aug 22, 2008, at 7:18 AM, Steve T wrote:

> This will sound a bit odd.
> I have a current server running with a UPS. I'm in the process of  
> replacing that server with another and obviously want Nut to  
> monitor the new server. The new/old servers are in different  
> locations, so I don't have access to the UPS while configuring the  
> replacement server.
> I think I have the config ok, but what errors would you expect to  
> see? Typically I'm getting a 'driver not connected' type error in  
> the /var/log/messages:

"driver not connected" is normal. However...

> Aug 19 18:07:16 T300 upsd[1308]: listening on 0.0.0.0 port 3493
> Aug 19 18:07:16 T300 upsd[1308]: Can't connect to UPS [belkin]  
> (belkinunv-belkin): No such file or directory
> Aug 19 18:07:16 T300 upsd[1309]: Startup successful
> Aug 19 18:07:16 T300 upsmon[1312]: Startup successful
> Aug 19 18:07:16 T300 upsd[1309]: Client nutmon at 127.0.0.1 logged  
> into UPS [belkin]
> Aug 19 18:07:16 T300 upsmon[1313]: Poll UPS [belkin at localhost]  
> failed - Driver not connected
> Aug 19 18:07:16 T300 upsmon[1313]: Communications with UPS  
> belkin at localhost lost
> Aug 19 18:07:21 T300 upsmon[1313]: Poll UPS [belkin at localhost]  
> failed - Driver not connected
> Aug 19 18:07:21 T300 upsmon[1313]: UPS belkin at localhost is unavailable
> Aug 19 18:07:26 T300 upsmon[1313]: Poll UPS [belkin at localhost]  
> failed - Driver not connected
> Aug 19 18:07:29 T300 upsd[1342]: not listening on 0.0.0.0 port 3493
> Aug 19 18:07:29 T300 upsmon[1347]: Startup successful
> Aug 19 18:07:29 T300 upsd[1309]: Client nutmon at 127.0.0.1 logged  
> into UPS [belkin]
> Aug 19 18:07:29 T300 upsmon[1348]: Poll UPS [belkin at localhost]  
> failed - Driver not connected
> Aug 19 18:07:29 T300 upsmon[1348]: Communications with UPS  
> belkin at localhost lost
> Aug 19 18:07:31 T300 upsmon[1313]: Poll UPS [belkin at localhost]  
> failed - Driver not connected
> Aug 19 18:07:34 T300 upsmon[1348]: Poll UPS [belkin at localhost]  
> failed - Driver not connected
> Aug 19 18:07:34 T300 upsmon[1348]: UPS belkin at localhost is unavailable
> Aug 19 18:07:36 T300 upsmon[1313]: Poll UPS [belkin at localhost]  
> failed - Driver not connected
> Aug 19 18:07:39 T300 upsmon[1348]: Poll UPS [belkin at localhost]  
> failed - Driver not connected
> Aug 19 18:07:41 T300 upsmon[1313]: Poll UPS [belkin at localhost]  
> failed - Driver not connected


Having two copies of upsmon (1313 and 1348) logging messages about  
the same UPS is not expected, though.

Also note:

> Aug 19 18:07:16 T300 upsd[1308]: listening on 0.0.0.0 port 3493
[...]
> Aug 19 18:07:29 T300 upsd[1342]: not listening on 0.0.0.0 port 3493

The second copy of upsd can't bind to the same port as the first one,  
so you get the above error message.

-- 
Charles Lepple
clepple at gmail



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080822/f3c52e3a/attachment.htm