[Nut-upsuser] Data Stale at random intervals

[Daniel Shields]

Hi Charles,


     TBH, I'm not using the pi server as I went back to my main server after it still wasn't playing nice.  Ultimately my goal is to get nut working with my main server as it was on Wheezy.   The kernel version is:


Linux nut.tklapp.com 4.4.21+ #911


I have the debug running now and will post back with the results of a failure.  Thanks!


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

On Oct 11, 2016, at 10:07 PM, Daniel Shields wrote:
>
> No joy.  Reverted.

A wrong number for the udev rules file would prevent the driver from starting at all due to permissions errors. It is possible that 52 and 62 are currently in the acceptable range.

>
> From: Daniel Shields <grungelizard9 at hotmail.com>
> Sent: Tuesday, October 11, 2016 9:19 PM
> To: nut-upsuser at lists. alioth. debian. org
> Cc: Daniel Shields
> Subject: Re: Data Stale at random intervals
>
> Have done more Googling and searching around the system.  Found that /lib/udev/rules.d/52-nut-usbups.rules has been changed to 62 by others and also in Sid (2.7.4) so gave that a shot.  Will post back with results.
>
>
> From: Daniel Shields <grungelizard9 at hotmail.com>
> Sent: Monday, October 10, 2016 10:51 PM
> To: nut-upsuser at lists. alioth. debian. org
> Subject: Re: Data Stale at random intervals
>
> Also, I have replaced the cable and have tried to install on Raspbian with the same issue.  Seems I may be missing something in the configuration, but haven't been able to find anything yet.

Which kernel version is your release of Raspbian running?

The logs seem to indicate that your UPS frequently sends status via interrupt reports. Does the "interruptonly" option help? If so, you can also try again without interruptonly (since that option might prevent certain variables from updating), but with increased timeouts for pollfreq and pollinterval.

Partially due to pressure from Debian, there is a libusb-1.0 branch of NUT now. That seemed to work better with the problem Tripp Lite unit that I have, although several variables changed at once. With a 4.4.0 (Ubuntu) kernel and libusb-1.0, the UPS stays connected for several days.

Can you run the driver in debug mode for longer, and post the part where it stops responding? Does the UPS still show up in libusb at that point? (No need to post the syslog output - it is mainly from other portions of NUT.)

> On October 10, 2016, at 9:39 PM, Daniel Shields <grungelizard9 at hotmail.com> wrote:
>
> Hello All,
>
>      Been at this for a few weeks, so figured I'd reach out.  I was previously running Debian Wheezy Nut Version 2.6.4 with no issues for over 6 months on the same hardware.  This issue started when I upgraded to Jessie, so just trying to get everything happy again.
>
> System is running "Linux golgotha.tklapp.com 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux"
>
> Nut Version:  ii  nut                                     2.7.2-4                  all                      network UPS tools - metapackage
>
> Installed via apt-get
>
> Monitoring:
>
> CyberPower 1500PFCLCD UPS
>
> Communication: USB, Serial
>
> I'm able to start the NUT service on my system and it runs for a couple of hours up to just under 24 hours.  I have scrubbed the logs and have not been able to pinpoint the exact issue.
>
> I have attached the syslog and debug logs.  Any help is greatly appreciated.  Thanks!
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

--
Charles Lepple

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161012/8aa169e2/attachment.html>