search for: nailbunni

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 nut-server service with gdb, but no luck getting it to work so far. Thanks! ________________________________ 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:

Just an update, these messages are in the syslog when nut is no longer able to communicate with the server: Oct 14 01:41:59 golgotha upsmon[1300]: Poll UPS [nailbunny at localhost] failed - Data stale Oct 14 01:42:04 golgotha upsmon[1300]: Poll UPS [nailbunny at localhost] failed - Data stale Oct 14 01:42:09 golgotha upsmon[1300]: Poll UPS [nailbunny at localhost] failed - Data stale Oct 14

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 sure where to go from here as I'm not seeing anything to follow up on. ________________________________ From: Daniel Shields <grungelizard9 at

Hi Charles, Thanks for the tip. I reran the debug again until communication stopped. Backtrace is below. Thanks! 441.204990 upsdrv_updateinfo... (Driver stopped communicating) Broadcast message from nut at golgotha.tklapp.com (somewhere) (Sat Oct 15 03:36:57 UPS nailbunny at localhost is unavailable ^C Program received signal SIGINT, Interrupt. 0x00007ffff76ec1c7 in ioctl

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)

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: ^C Program received signal SIGINT, Interrupt. 0x00007ffff76ec1c7 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007ffff76ec1c7 in ioctl () from

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 sure where to go from here as I'm

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

- 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 while to get back to you

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