[Nut-upsuser] Data stale error after short while
Mike Raath
raathm at gmail.com
Fri Jan 2 20:33:43 UTC 2015
Sorry, I messed up my reply a bit.
The output of the lsusb command is the same before and after the data goes
stale.
$ lsusb -d 0665:
Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial
And the output of the /lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 command is
the same as in the previous attachment. I truncated the "before" log
because it just carried on with the same output after the broadcast
notification that the UPS became unavailable (at 214.883342).
On 2 January 2015 at 22:14, Mike Raath <raathm at gmail.com> wrote:
> Ok - before stale data:
>
> After stale data:
>
> $ lsusb -d 0665:
>
> Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial
>
>
> After stale data:
>
>
> And the gzipped log attached:
>
>
>
> On 2 January 2015 at 21:56, Charles Lepple <clepple at gmail.com> wrote:
>
>> On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote:
>>
>> Not sure what other logs I can provide to try to troubleshoot this?
>>
>>
>> Two things:
>>
>> - the output of 'lsusb -d 0665:' before and after the 'stale data' warning
>> - the output of '/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 | tee
>> /tmp/nutdrv_qx.log'
>>
>> (Please gzip nutdrv_qx.log before sending it, thanks.)
>>
>> --
>> Charles Lepple
>> clepple at gmail
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150102/a9e47f85/attachment.html>
More information about the Nut-upsuser
mailing list