[Nut-upsuser] Data Stale at random intervals

[Daniel Shields]

Hi Charles,


     Tried it with -p but couldn't get it to run, I'll have to dig further into the man pages.  I ran without -p though and got an interesting timeout error.  Attached is the log.  I'll look further into the -p option as well.  Tried sending the full zipped log but it was too big.  Attaching the part where the error occurred.  It seems like it was able to recover a couple of times, but the last time it got stuck.  Thanks!



________________________________
From: Charles Lepple <clepple at gmail.com>
Sent: Saturday, October 22, 2016 2:11 PM
To: Daniel Shields
Cc: nut-upsuser at lists. alioth. debian. org
Subject: Re: [Nut-upsuser] Data Stale at random intervals





- Charles
On Oct 16, 2016, at 3:34 AM, Daniel Shields <grungelizard9 at hotmail.com<mailto:grungelizard9 at hotmail.com>> wrote:


I've been testing with debug further and there's a few extra lines when the nut-server stops communicating as opposed to when it's running.


Backtrace after stale data, UPS nailbunny at localhost is unavailable:

Sorry to take a while to get back to you on this.

I wonder if it is getting stuck once at that point, or if it is repeatedly calling the same libusb function.

If it is the former, then I suspect we are not going to get much help from Debian on this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810449

Using "strace -p" with some extra options to see the time spent on each syscall might work. (There might be some sysctl magic necessary to attach to a running driver.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161025/8e243197/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nut-debug2.7z
Type: application/octet-stream
Size: 3553 bytes
Desc: nut-debug2.7z
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161025/8e243197/attachment-0001.obj>