search for: grungelizard9

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, b...

...b) ________________________________ From: Charles Lepple <clepple at gmail.com> Sent: Friday, October 14, 2016 10:41 PM To: Daniel Shields Cc: nut-upsuser at lists. alioth. debian. org Subject: Re: [Nut-upsuser] Data Stale at random intervals On Oct 14, 2016, at 8:53 PM, Daniel Shields <grungelizard9 at hotmail.com<mailto:grungelizard9 at hotmail.com>> wrote: Ran with gdb: gdb /lib/nut/usbhid-ups run -u nut -a nailbunny -x bus=010 -x vendorid=0764 -x productid=0501 -DDDDD Same result as when I ran normally. Driver just stops communicating with no errors or messages in the logs....

...n 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-usbup...

...us=010 -x vendorid=0764 -x productid=0501 -DDDDD Same result as when I ran normally. Driver just stops communicating with no errors or messages in the logs. Not sure where to go from here as I'm not seeing anything to follow up on. ________________________________ From: Daniel Shields <grungelizard9 at hotmail.com> Sent: Friday, October 14, 2016 12:02 AM To: Charles Lepple Cc: nut-upsuser at lists. alioth. debian. org Subject: Re: [Nut-upsuser] Data Stale at random intervals Just an update, these messages are in the syslog when nut is no longer able to communicate with the server: Oct 1...

...! ________________________________ From: Charles Lepple <clepple at gmail.com> Sent: Wednesday, October 12, 2016 8:20 PM To: Daniel Shields Cc: nut-upsuser at lists. alioth. debian. org Subject: Re: [Nut-upsuser] Data Stale at random intervals On Oct 12, 2016, at 8:13 PM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > Wow. Okay, well I let the debug run all day. Nothing in the logs even with debug cranked to level 5. Attached are the last 1000 lines before it quit. I'm really stumped now. gzipped and resent for the rest of the list. Can you elaborate on how it quit?...

No joy. Reverted. ________________________________ 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...

...73 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x000000000040a88e in ?? () #2 0x0000000000402c4d in ?? () #3 0x00007ffff762cb45 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x0000000000402e4d in ?? () (gdb) ________________________________ From: Daniel Shields <grungelizard9 at hotmail.com> Sent: Friday, October 14, 2016 11:41 PM To: Charles Lepple Cc: nut-upsuser at lists. alioth. debian. org Subject: Re: [Nut-upsuser] Data Stale at random intervals Hi Charles, Thanks for the tip. I reran the debug again until communication stopped. Backtrace is below....

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)

- Charles > On Oct 16, 2016, at 3:34 AM, Daniel Shields <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...

...______________________ 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: So...

Hello, I have a Raspberry Pi model B running Raspbian Stretch. I have installed version 2.7.4-5 of nut from the raspbian repos. I have a CyberPower 1500PFCLCD UPS. When I reboot the Pi, the nut-server service fails to start. root at nut:~# service nut-server status ? nut-server.service - Network UPS Tools - power devices information server Loaded: loaded

...r reconnects, but can't communicate due to the Data Stale. I get the same result from trying to restart the nut-server service manually. I have to stop and restart the service and it will work for a couple hours up to ~ 24 sometimes. ________________________________ From: Daniel Shields <grungelizard9 at hotmail.com> Sent: Thursday, October 13, 2016 2:19 PM To: Charles Lepple Cc: nut-upsuser at lists. alioth. debian. org Subject: Re: [Nut-upsuser] Data Stale at random intervals Here are the results of a restart as well as a stop/start. Seems like it may be the server? I tried to run the...

Hi Charles, I've been monitoring for the past few days and NUT has been running solid. Tested and everything's working as it should. Thanks for all of your help on this, great to have it running well again and learned lot. ________________________________ From: Daniel Shields <grungelizard9 at hotmail.com> Sent: Tuesday, October 25, 2016 8:01 PM To: Charles Lepple Subject: Re: [Nut-upsuser] Data Stale at random intervals Hi Charles, Pardon my ignorance [?] I figured it out. Didn't realize the \ was a separator. It's installed so I'll see how it goes. Thanks...

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. 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...

On Oct 12, 2016, at 8:13 PM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > Wow. Okay, well I let the debug run all day. Nothing in the logs even with debug cranked to level 5. Attached are the last 1000 lines before it quit. I'm really stumped now. gzipped and resent for the rest of the list. Can you elaborate on how it quit?...

On Oct 14, 2016, at 8:53 PM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > Ran with gdb: > > gdb /lib/nut/usbhid-ups > > run -u nut -a nailbunny -x bus=010 -x vendorid=0764 -x productid=0501 -DDDDD > > Same result as when I ran normally. Driver just stops communicating with no errors or messages in the logs. Not...

On Oct 22, 2017, at 2:39 AM, Daniel Shields <grungelizard9 at hotmail.com> wrote: > > Oct 22 05:57:37 nut.tklapp.com upsd[341]: not listening on 192.168.213.189 port 3493 > Oct 22 05:57:37 nut.tklapp.com upsd[341]: not listening on 192.168.213.189 port 3493 > Oct 22 05:57:37 nut.tklapp.com upsd[341]: listening on 127.0.0.1 port 3493 > Oc...

Hello all. I have installed Nut on a Raspberry PI and all looks to be configured correctly, but I get stale data and communications lost at random intervals. I tried running nut-driver in gcc to see if I could find any clues there, but it ran for about 24 hours with no sign of an issue. However, when I let Nut run normally, it seems to be anywhere from 2 to 8 hours and the data goes stale and