[Nut-upsdev] Getting 'Data stale' error with bcmxcp_usb for a PowerWare 5115 on OSX
clepple at gmail.com
Wed Mar 10 12:54:19 UTC 2010
On Wed, Mar 10, 2010 at 4:08 AM, Charlie Garrison <garrison at zeta.org.au> wrote:
> Good evening,
> On 8/03/10 at 11:54 PM -0500, Charles Lepple <clepple at gmail.com> wrote:
>> If you have time to add some upslogx() calls to the driver, I would be
>> interested in comparing the errors you are experiencing when not running in
>> debug mode. When the tripplite_usb driver is in the background, it logs the
>> 3/8/10 11:26:04 PM tripplite_usb Error reading S value: Device
>> detached? (error 0: libusb/darwin.c usb_setup_iterator:
>> IOServiceGetMatchingServices: unknown error
> I'm not seeing anything like that.
The second part of the error comes from usb_strerror(), so can you
change line 155 in your modified version to:
upslogx(LOG_WARNING, "usb_interrupt_read is %d (%s)", res, usb_strerror());
>> One option might be to just use one -D flag, and start the driver from
>> launchd. Then you can have it respawn when the device is disconnected -
>> which I believe the bcmxcp_usb driver does not currently do itself.
> Yep, I had thought about that. And I'm happy to run NUT like that, but of
> course I would prefer to solve the underlying issue.
It might be the way to go (as a fallback) for the times when we aren't
actively diagnosing the problem.
- Charles Lepple
More information about the Nut-upsdev