Good afternoon,

On 14/03/10 at 4:52 AM +1100, Charlie Garrison <[email protected]> wrote:

My reasoning for suggesting a launchd plist for the driver is that launchd can respawn the driver if necessary - which would be helpful in your case if the device disconnects. (However, I seem to remember that you said the driver still reports "data stale", which means it has not treated the error code as a "device disconnection". We need to work on that.)

I don't believe I've had a 'data stale' error when running driver in debug mode. Or maybe I'm not following what you're saying.

But I have now... after running for around 8 hours in debug mode; I'm now getting "Data stale" errors via upsmon:

14/03/10 4:26:06 AM upsmon[15330] Communications with UPS powerware5...@localhost established
14/03/10 4:54:13 AM upsmon[15330] UPS powerware5...@localhost on battery
14/03/10 4:58:38 AM upsmon[15330] UPS powerware5...@localhost on line power 14/03/10 12:29:13 PM upsmon[15330] Poll UPS [powerware5...@localhost] failed - Data stale 14/03/10 12:29:13 PM upsmon[15330] Communications with UPS powerware5...@localhost lost 14/03/10 12:29:18 PM upsmon[15330] Poll UPS [powerware5...@localhost] failed - Data stale 14/03/10 12:29:23 PM upsmon[15330] Poll UPS [powerware5...@localhost] failed - Data stale 14/03/10 12:29:28 PM upsmon[15330] Poll UPS [powerware5...@localhost] failed - Data stale

And I'm not able to quit the driver now:

$ sudo killall -9 bcmxcp_usb
$ ps ax | grep bcmxcp
15641   ??  Us     0:22.34 /usr/local/ups/bin/bcmxcp_usb -D -a powerware5115

I can't unload that job via launchctl either. And since I was sending all the debug output to /dev/null, I don't have any clues from there. I'll test again without redirecting stderr (if I can figure out how to kill the driver). Can you suggest any way to kill the driver short of a restart?

And I answered my own question (leaving it here in case it helps someone else later). I re/plugged the UPS USB cable and the driver died. When/if I get the 'data stale' error again I'll send anything from the debug log that looks relevant.

Thanks,
Charlie

--
   Ꮚ Charlie Garrison ♊ <[email protected]>
   〠 PO Box 141, Windsor, NSW 2756, Australia

O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
http://www.ietf.org/rfc/rfc1855.txt

_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev

Reply via email to