Re: [Nut-upsuser] NUT on Windows, Wall->message.exe

2014-02-24 Thread Kris Jordan
Kris Jordan wrote, On 2/24/2014 10:13 PM: The worst case is probably because upsmon will log a problem every poll interval until it's corrected. Intended? Correction, poll interval --> POLLFREQ (in upsmon.conf). ___ Nut-upsuser mailing list Nut-upsu

[Nut-upsuser] NUT on Windows, Wall->message.exe

2014-02-24 Thread Kris Jordan
If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? NOTIFYFLAG ONLINESYSLOG NOTIFYFLAG ONBATTSYSLOG NOTIFYFLAG LOWBATTSYSLOG NOTIFYFLAG FSDSYSLOG NOTIFYFLAG COMMOKSYSLOG NOTIFYFLAG COMMBADSYSLOG NOTIFYFLAG SHUTDOWNSYSLOG NOTIFYFLAG

Re: [Nut-upsuser] Arch Linux and Tripp Lite web snmp card issues.

2014-02-24 Thread Jason R Begley
On 2/24/2014 11:10 PM, Charles Lepple wrote: On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! Sorry, it's basically all comments. Do you have

Re: [Nut-upsuser] Arch Linux and Tripp Lite web snmp card issues.

2014-02-24 Thread Charles Lepple
On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > Thanks for the quick response Charles! I may not have gotten the correct > output from the snmpwalk, let me know if the attachment is usable. Thanks! Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also

Re: [Nut-upsuser] Arch Linux and Tripp Lite web snmp card issues.

2014-02-24 Thread Jason R Begley
Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! New data added, here is the gdb output: Reading symbols from /usr/bin/snmp-ups...(no debugging symbols found)...done. (gdb) run -a tripplite -DD

Re: [Nut-upsuser] Arch Linux and Tripp Lite web snmp card issues.

2014-02-24 Thread Charles Lepple
On Feb 24, 2014, at 6:57 PM, Jason R Begley wrote: > Segmentation fault That's not good. If you crank up the debug level past 2, does it provide any more detail about where it crashed? (We'd only need the last few lines, if they are different.) I don't know how Arch Linux does debug symbols, s

[Nut-upsuser] Setting UPS values can be confusing

2014-02-24 Thread Kris Jordan
Windows 7 Pro x64, NUT 2.6.5-4 (interim release) Product: Back-UPS RS 1200 FW:8.g3 .D USB FW:g3 Setting UPS values can be confusing. For example, battery.charge.low and battery.runtime.low. Using upsrw, the values will be retained after restarting the OS, but not if the UPS is turned off/rest

[Nut-upsuser] Arch Linux and Tripp Lite web snmp card issues.

2014-02-24 Thread Jason R Begley
I have been working with NUT to get this working since upgrading to a web snmp card in a UPS. I keep getting seg faults when running snmp-ups also. Below is the output. kernel: [1365065.178230] snmp-ups[1940]: segfault at 0 ip b7555470 sp bf8d89e8 error 4 in libc-2.18.so[b74c2000+1a9000] Run

Re: [Nut-upsuser] riello_usb driver: randomly not working and usbfs flooding syslog

2014-02-24 Thread Roberto Resoli
Il 22/02/2014 23:11, Roberto Resoli ha scritto: On 22 febbraio 2014 17:28:16 CET, Roberto Resoli wrote: Hello, after some days running without problems, my riello idialog 800 ups get disconnected, and usbfs started flooding syslog with messages like: usb 1-1.2: usbfs: process 57342 (riello_us

Re: [Nut-upsuser] nut in openwrt

2014-02-24 Thread Charles Lepple
On Feb 24, 2014, at 3:56 AM, Tim Dawson wrote: > Either it is not loaded, or the usb serial and/or hid drivers are not loaded, > which appear to have been used on your Debian box. Tim, For most of the USB drivers in NUT, we tend to bypass the kernel USB-to-serial and HID drivers (detaching the

Re: [Nut-upsuser] nut in openwrt

2014-02-24 Thread Josu Lazkano
2014-02-24 10:00 GMT+01:00 Tim Dawson : > Just looked at your prior mail, and it was using 'usbhid' based on your > output. If 'modprobe' exists on your router, what response do you get to > 'modprobe usbhid'? > > - Tim Hello, It looks that there is no "modprobe" in the router: # modprobe usbhid

Re: [Nut-upsuser] nut in openwrt

2014-02-24 Thread Tim Dawson
Just looked at your prior mail, and it was using 'usbhid' based on your output. If 'modprobe' exists on your router, what response do you get to 'modprobe usbhid'? - Tim On February 24, 2014 2:56:16 AM CST, Tim Dawson wrote: >Either it is not loaded, or the usb serial and/or hid drivers are n

Re: [Nut-upsuser] nut in openwrt

2014-02-24 Thread Tim Dawson
Either it is not loaded, or the usb serial and/or hid drivers are not loaded, which appear to have been used on your Debian box. - Tim On February 24, 2014 1:12:36 AM CST, Josu Lazkano wrote: >Thanks again. > >This is the lsmod output: > ># lsmod >aead4256 0 >arc4