[Nut-upsuser] Cyberpower/powerpanel error: Data stale

[Seann Clark]

Arjen de Korte wrote:
> Citeren Seann Clark <nombrandue at tsukinokage.net>:
>
>> If I use the powerpanel driver, it either dies, or fails to start.
>>
>> Here is a sample from the syslog dealing with that:
>> Oct 25 02:37:21 haruhi upsd[9796]: listening on 0.0.0.0 port 3493
>> Oct 25 02:37:21 haruhi upsd[9796]: Can't connect to UPS 
>> [cyberpower-ups] (powerpanel-cyberpower-ups): No such file or directory
>> Oct 25 02:37:21 haruhi upsd[9797]: Startup successful
>> Oct 25 02:37:25 haruhi upsd[9815]: not listening on 0.0.0.0 port 3493
>> Oct 25 02:37:27 haruhi upsd[9797]: Connected to UPS [cyberpower-ups]: 
>> powerpanel-cyberpower-ups
>> Oct 25 02:37:27 haruhi upsd[9836]: not listening on 0.0.0.0 port 3493
>> Oct 25 02:37:28 haruhi upsd[9856]: not listening on 0.0.0.0 port 3493
>> Oct 25 02:37:29 haruhi upsd[9876]: not listening on 0.0.0.0 port 3493
>> Oct 25 02:37:34 haruhi upsd[9919]: not listening on 0.0.0.0 port 3493
>> Oct 25 02:37:42 haruhi upsd[9797]: Data for UPS [cyberpower-ups] is 
>> stale - check driver
>> Oct 25 02:38:33 haruhi upsd[9797]: UPS [cyberpower-ups] data is no 
>> longer stale
>> Oct 25 02:38:35 haruhi upsd[9797]: Data for UPS [cyberpower-ups] is 
>> stale - check driver
>> Oct 25 02:39:14 haruhi upsd[10229]: not listening on 0.0.0.0 port 3493
>> Oct 25 02:39:14 haruhi upsd[9797]: Rejecting TCP connection from 
>> 192.168.1.21
>
> You seem to have an awful lot of upsd servers. Check out why. Chances 
> are you're running multiple instances, this doesn't fly.
I have validated this time around that it isn't running multiples, 
sometimes the init scripts don't seem to kill off everything, so a 
manual kill is sometimes needed on orphaned processes.
>
>> I fixed the "rejecting TCP connections" lines so that isn't important 
>> in those logs (Forgot to change ACL's) but, since powerpanel was the 
>> first driver I used before moving over to the cyberpower driver this 
>> morning, I have decent logs of this problem.
>
> Make sure you kill everything (driver, server and monitor) before 
> starting new ones.
>
> If all else fails, running the 'powerpanel' driver in debug mode might 
> reveal what is the problem, but for the moment I think this might be 
> due to competing servers. 

This output is after everything has been shut down and all NUT related 
items killed out of memory after a init script being run to stop the 
main items. The output of the debug is:
debug level is '3'
Trying binary protocol...
read: (20 bytes) => 2e 4f 50 31 35 30 30 20 20 20 20 2e 78 2e 3c 2e 35 31
 30 30
CyberPower UPS with binary protocol on /dev/ttyS0 detected
send: (3 bytes) => 52 02 0d
read: (2 bytes) => 52 00
send: (3 bytes) => 52 04 0d
read: (2 bytes) => 52 00
send: (3 bytes) => 52 08 0d
read: (2 bytes) => 52 00
send: (3 bytes) => 52 18 0d
read: (2 bytes) => 52 00
send: (2 bytes) => 44 0d
read: (14 bytes) => 23 7d 00 22 2e d6 80 b1 2e 09 f6 00 ff 0d
dstate_init: sock /var/run/nut/powerpanel-cyberpower-ups open on fd 6
send: (2 bytes) => 44 0d
read: (14 bytes) => 23 7c 00 21 2e d6 7f b1 2e 09 f6 00 ff 0d
send: (2 bytes) => 44 0d
read: (14 bytes) => 23 7d 00 22 2e d6 80 b1 2e 09 f6 00 ff 0d
send: (2 bytes) => 44 0d
read: (14 bytes) => 23 7d 00 22 2e d6 80 b2 2e 09 f6 00 ff 0d
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Warning: excessive comm failures, limiting error reporting
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
send: (2 bytes) => 44 0d
read: timed out
send: (2 bytes) => 44 0d
read: timed out
send: (2 bytes) => 44 0d
read: timed out
send: (2 bytes) => 44 0d
read: (14 bytes) => 23 7a 00 22 2e d6 81 b1 2e 09 f6 00 ff ff
Communications with UPS re-established
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
send: (2 bytes) => 44 0d
read: timed out
Communications with UPS lost: Status read failed!
^CSignal 2: exiting

regards
Seann


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5614 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20081028/3a0cc5c0/attachment.bin