search for: trippliteup

...:25:27 localhost kernel: usb 2-2.1: Manufacturer: Tripp Lite > > May 29 19:25:27 localhost kernel: hid-generic 0003:09AE:2012.0004: > hiddev0,hidraw1: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on > usb-0000:02:02.0-2.1/input0 > > May 29 19:25:29 localhost upsd[6287]: UPS [TrippLiteUPS] data is no longer > stale > > May 29 19:25:29 localhost upsd: UPS [TrippLiteUPS] data is no longer stale > > May 29 19:25:45 localhost kernel: usb 2-2.1: USB disconnect, device number > 6 > > May 29 19:25:47 localhost upsd[6287]: Data for UPS [TrippLiteUPS] is stale > -...

...duct: Tripp Lite UPS May 29 19:25:27 localhost kernel: usb 2-2.1: Manufacturer: Tripp Lite May 29 19:25:27 localhost kernel: hid-generic 0003:09AE:2012.0004: hiddev0,hidraw1: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:02:02.0-2.1/input0 May 29 19:25:29 localhost upsd[6287]: UPS [TrippLiteUPS] data is no longer stale May 29 19:25:29 localhost upsd: UPS [TrippLiteUPS] data is no longer stale May 29 19:25:45 localhost kernel: usb 2-2.1: USB disconnect, device number 6 May 29 19:25:47 localhost upsd[6287]: Data for UPS [TrippLiteUPS] is stale - check driver May 29 19:25:47 localhost upsd:...

...duct: Tripp Lite UPS May 29 19:25:27 localhost kernel: usb 2-2.1: Manufacturer: Tripp Lite May 29 19:25:27 localhost kernel: hid-generic 0003:09AE:2012.0004: hiddev0,hidraw1: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:02:02.0-2.1/input0 May 29 19:25:29 localhost upsd[6287]: UPS [TrippLiteUPS] data is no longer stale May 29 19:25:29 localhost upsd: UPS [TrippLiteUPS] data is no longer stale May 29 19:25:45 localhost kernel: usb 2-2.1: USB disconnect, device number 6 May 29 19:25:47 localhost upsd[6287]: Data for UPS [TrippLiteUPS] is stale - check driver May 29 19:25:47 localhost upsd:...

...duct: Tripp Lite UPS May 29 19:25:27 localhost kernel: usb 2-2.1: Manufacturer: Tripp Lite May 29 19:25:27 localhost kernel: hid-generic 0003:09AE:2012.0004: hiddev0,hidraw1: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:02:02.0-2.1/input0 May 29 19:25:29 localhost upsd[6287]: UPS [TrippLiteUPS] data is no longer stale May 29 19:25:29 localhost upsd: UPS [TrippLiteUPS] data is no longer stale May 29 19:25:45 localhost kernel: usb 2-2.1: USB disconnect, device number 6 May 29 19:25:47 localhost upsd[6287]: Data for UPS [TrippLiteUPS] is stale - check driver May 29 19:25:47 localhost upsd:...

...es after 4+ minutes. That is going to be hard to diagnose without the usbhid-ups logs for the time when those commands are sent - can you try to keep the log going while sending them, then note the time when the command was sent? You can use the "tee" command: /lib/nut/usbhid-ups -DD -a TrippLiteUPS 2>&1 | tee /tmp/log.shutdown.return.txt (please use gzip before attaching the log - the mailing list does not accept messages over 40kB without manual intervention.) > I did notice that that return.shutdown was not found in the list running "upscmd -l TrippLiteUPS". I did see...

...duct: Tripp Lite UPS May 29 19:25:27 localhost kernel: usb 2-2.1: Manufacturer: Tripp Lite May 29 19:25:27 localhost kernel: hid-generic 0003:09AE:2012.0004: hiddev0,hidraw1: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:02:02.0-2.1/input0 May 29 19:25:29 localhost upsd[6287]: UPS [TrippLiteUPS] data is no longer stale May 29 19:25:29 localhost upsd: UPS [TrippLiteUPS] data is no longer stale May 29 19:25:45 localhost kernel: usb 2-2.1: USB disconnect, device number 6 May 29 19:25:47 localhost upsd[6287]: Data for UPS [TrippLiteUPS] is stale - check driver May 29 19:25:47 localhost upsd:...

...eem to be working except the UPS turns off immediately during a test shutdown using///"//upsmon -c fsd".//No delay before the UPS turns itself off leaving no time for the server to shutdown properly. I have attempted to set the delay higher using "upsrw -s ups.delay.shutdown=120 TrippLiteUPS at localhost" and confirmed the value with "upsc ///TrippLiteUPS at localhost/" Still the UPS switches off right away. At first after installing the debian nut packages with apt-get and setting up the config files I had to setup a systemd service to exeu "upsdrvctl shutdow...

...t kernel: usb 8-2: Product: Tripp Lite UPS Jun 21 11:35:20 localhost kernel: usb 8-2: Manufacturer: Tripp Lite Jun 21 11:35:20 localhost kernel: hid-generic 0003:09AE:2012.1029: hiddev0,hidraw0: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:00:10.1-2/input0 /etc/ups/ups.conf [TrippLiteUPS] driver = usbhid-ups port = auto desc = "SMART1500LCD" sudo lsusb –v output for UPS Bus 008 Device 098: ID 09ae:2012 Tripp Lite Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defi...

...014: ID 09ae:2012 Tripp Lite Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [npg at localhost ~]$ upsd -V Network UPS Tools upsd 2.7.2 [npg at localhost ~]$ upsc TrippLiteUPS battery.charge: 100 battery.runtime: 3840 battery.type: PbAC battery.voltage: 27.5 battery.voltage.nominal: 24.0 device.mfr: Tripp Lite device.model: Tripp Lite UPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto d...

...e UPS > May 29 19:25:27 localhost kernel: usb 2-2.1: Manufacturer: Tripp Lite > May 29 19:25:27 localhost kernel: hid-generic 0003:09AE:2012.0004: hiddev0,hidraw1: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:02:02.0-2.1/input0 > May 29 19:25:29 localhost upsd[6287]: UPS [TrippLiteUPS] data is no longer stale > May 29 19:25:29 localhost upsd: UPS [TrippLiteUPS] data is no longer stale > May 29 19:25:45 localhost kernel: usb 2-2.1: USB disconnect, device number 6 It would be interesting to see the debug log from usbhid-ups as well. It would give a little more context to t...

[when responding, please use reply-all - the list does not mangle the reply-to header] > On Aug 21, 2017, at 12:45 AM, Whiteshell Tech <neil at whiteshell-tech.com> wrote: > > I have attempted to set the delay higher using "upsrw -s ups.delay.shutdown=120 TrippLiteUPS at localhost" and confirmed the value with "upsc TrippLiteUPS at localhost" Still the UPS switches off right away. Due to the way that the HID PDC shutdown sequence works, the value you see from "upsc ups.delay.shutdown" is just a variable in the driver. It does not write...

...ed, as clearly state here <http://networkupstools.org/stable-hcl.html>. Then I thought I needed the last src code (2.7.4), hence I built it for my machine, but when I run it by: /usr/local/ups/sbin/upsdrvctl start I had, in order, this message "writepid: fopen /var/state/ups/usbhid-ups-trippliteups.pid: Permission denied" and...the same message above about the not supported device! What's wrong in there? Regards Ambrogio P.S. I also performed the installation notes for the driver in here <http://networkupstools.org/docs/man/usbhid-ups.html>. -------------- next part -------...

...ore context to the kernel errors. I haven't used a physical CentOS or RedHat system in a while, so I am not sure of the specifics needed to just stop the usbhid-ups driver, but then you can restart it with a few "-D" flags (3 should be sufficient for this kind of problem) and "-a TrippLiteUPS" to match this configuration. Please compress any log files (gzip preferred; zip works).” Attached. This is with the settings and udev rules mentioned in the earlier. I can remove and redo if useful. “pollinterval defaults to 2, and to be honest, for most other UPSes, we suggest that pe...

On 06/24/2017 04:52 AM, Charles Lepple wrote: > On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. > No, the HCL also mentions "protocol 4001". For Tripp-Lite,

..., check /usr/local/ups for your > new installation. > Thanks, found the installation there. Please try building snmp-ups, and let me know how the output of upsc looks. > Rebuilt is with "*--with-snmp" *option, installed and started nut processes, and they are working :) upsc trippliteups at 10.200.254.26 command output shows the UPS status as shown below:) battery.charge: 100.00 device.mfr: Tripp Lite / Phoenixtec device.model: Intelligent device.type: ups driver.name: snmp-ups driver.parameter.pollinterval: 2 driver.parameter.port: 10.200.254.39 driver.version: 2.7.1.5 driver.ve...

...y installed Manuel's packages (nut and nut-client). When I run the driver as root (for my tripplite ups) I get: /usr/sbin/upsdrvctl start Network UPS Tools - Generic HID driver 0.42 (v2.7.4-418-gb1314c62.7.4.1) USB communication driver (libusb 0.1) 0.33 writepid: fopen /var/run/nut/usbhid-ups-trippliteups.pid: Permission denied Can't claim USB device [09ae:1330]: could not detach kernel driver from interface 0: Operation not permitted Driver failed to start (exit status=1) And I had to create manually /var/run/nut. What is the problem there? On Fri, Jun 23, 2017 at 8:27 PM Manuel Wolfshant &...

Hi, Nut-upsusers, I am having problem configuring NUT to work with Tripplite UPS through SNMP. There is a Tripplite SmartOnline SU10KRT3/1X and attempts to monitor it using NUT though SNMP are failing... OS: Enterprise Linux 6, Nut version: 2.6.5. ups.conf is configured: [trippliteups] driver = snmp-ups port = 10.200.254.39 desc = "ProductionServer" snmp_version = v1 community = public Starting the driver with command *snmp-ups -a trippliteups -D * is failing with the following output: Network UPS Tools - Generic SNMP UPS...

...us2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen1.1: <UHCI root HUB VIA> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen0.2: <TRIPP LITE SMART1500RMXL2Ua TRIPP LITE> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (60mA) Here's the ups.conf # cat ups.conf [TrippliteUPS] driver=usbhid-ups port=auto I've also tried the tripplite driver with no success. Any ideas on what I'm missing? Nick Teague Network Administrator Smartfox Solutions office: 1-877-301-9993 fax: 1-256-301-9299 www.smartfox.us -------------- next part -------------- An HTML attachment...

...(nut and nut-client). > > When I run the driver as root (for my tripplite ups) I get: > > /usr/sbin/upsdrvctl start > Network UPS Tools - Generic HID driver 0.42 (v2.7.4-418-gb1314c62.7.4.1) > USB communication driver (libusb 0.1) 0.33 > writepid: fopen /var/run/nut/usbhid-ups-trippliteups.pid: Permission denied > Can't claim USB device [09ae:1330]: could not detach kernel driver from > interface 0: Operation not permitted > Driver failed to start (exit status=1) > > And I had to create manually /var/run/nut. > > What is the problem there? > > On Fri,...

...ore context to the kernel errors. I haven't used a physical CentOS or RedHat system in a while, so I am not sure of the specifics needed to just stop the usbhid-ups driver, but then you can restart it with a few "-D" flags (3 should be sufficient for this kind of problem) and "-a TrippLiteUPS" to match this configuration. Please compress any log files (gzip preferred; zip works).” > > Attached. This is with the settings and udev rules mentioned in the earlier. I can remove and redo if useful. The log format looks okay, but I may not have been clear that I was looking for...