search for: rtdup

...gt; reveal much more: > ----------------------------------------------------------------------------------------------- > rtd at linux-5048:~> sudo /usr/local/ups/sbin/upsdrvctl -DDDDD shutdown > Network UPS Tools - UPS driver controller 2.7.2.6_RTD ... > 0.000137 Shutdown UPS: rtdups > 0.000160 exec: /usr/local/ups/bin/usbhid-ups -a rtdups -k > Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) > USB communication driver 0.32 > Can't claim USB device [2a37:5110]: No such file or directory > 0.007491 Driver failed to start (exit status=1)...

On Fri, 4 Sep 2015, Rob Groner wrote: > Well, I tried the same script method with openSUSE 13.2, and it still did not execute. > > So I tried the system method, and it worked 1 time out of 3 attempts. I captured the last failure: > 2015-09-04T11:43:38.825317-04:00 linux-5048 upsdrvctl[1887]: Can't claim USB device [2a37:5110]: No such file or directory >

...------------------------ rtd at linux-5048:~> sudo /usr/local/ups/sbin/upsdrvctl -u ups start root's password: Network UPS Tools - UPS driver controller 2.7.2.6_RTD Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) USB communication driver 0.32 writepid: fopen /var/run/ups/usbhid-ups-rtdups.pid: No such file or directory Using subdriver: RTD UPS HID v1.0 rtd at linux-5048:~> sudo /usr/local/ups/sbin/upsd -u ups Network UPS Tools upsd 2.7.2.6_RTD fopen /var/run/ups/upsd.pid: No such file or directory /usr/local/ups/etc/upsd.conf is world readable listening on 127.0.0.1 port 3493 C...

Roger, rtd at linux-5048> sudo /usr/local/ups/bin/usbhid-ups -a rtdups -k -DDD Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) USB communication driver 0.32 0.000000 debug level is '3' 0.000405 upsdrv_initups... 0.004386 Checking device (0930/6545) (002/002) 0.004431 Failed to open device, skipping. (Permission denied) 0.004442 Checki...

...dding the debug commands cause a problem? It seems like it would either be timing related (extra time taken by outputting debug messages) or the debug flags are actually affecting execution. -------------------------------------------------- linux-86h4:/usr/local/ups/bin # ./usbhid-ups -u root -a rtdups Network UPS Tools - Generic HID driver 0.39 (2.7.2.6_RTD) USB communication driver 0.32 Duplicate driver instance detected! Terminating other driver! Broadcast message from rtd at linux-86h4 (somewhere) (We...

On Sep 9, 2015, at 9:40 AM, Rob Groner <rgroner at RTD.com> wrote: > > I'm not sure which USB lib it compiled against. What does this return? ldd /path/to/driver -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150909/ba08f4c0/attachment.html>

Charles, dmesg doesn't say anything when "usbhid-ups -a rtdups -k" is executed. I'm not sure which USB lib it compiled against. I installed them via "zypper install libusb-*". I'll try to find the version that got installed, as that WOULD be one thing that might have changed since the last time I had this working. I'm not sur...

...the system messages, so I went into the upsmon.conf file and commented out the "online" and "onbatt" NOTIFYFLAG messages. I then did a reload of upsmon...but found I was still getting the messages. Long story short, my upsmon.conf file now consists of a single entry: MONITOR rtdups at localhost 1 upsmaster sekret master I'm still getting the onbattery, online, comm good, comm bad, etc system messages. Clearly there is some default behavior going on. How do I keep these system messages from happening? Thanks Rob -------------- next part -------------- An HTML atta...

On Sep 8, 2015, at 4:48 PM, Rob Groner <rgroner at RTD.com> wrote: > > 0.005927 Device matches > 0.005940 failed to claim USB device: Device or resource busy > 0.005954 failed to detach kernel driver from USB device: No such file or directory Rob, this is a bit of a tough one to track down. The "Device or resource busy" message can either come from a kernel