[Nut-upsuser] [POSSIBLE FRAUD] Re: [EXTERNAL] Re: Help with Tripp Lite Internet600U

Wed May 20 20:22:18 BST 2020

Wow - you're doing all the work for me!

Thanks for the rule set.  

I can't easily reboot that box just now, so I'm working on reloading the rules.

When I try 

udevadm control --reload-rules && udevadm trigger

May 20 15:19:01 elmer systemd-udevd[3413]: Process '/sbin/crda' failed with exit code 234.

May 20 15:19:01 elmer systemd-udevd[3413]: Using default interface naming scheme 'v240'.

sigh.  More to learn.  

I don't want to waste your time because this is not a tripp lite issue - but do you happen to have a suggestion about troubleshooting crda?

---- On Wed, 20 May 2020 15:13:42 -0400 David Zomaya <David_Zomaya at tripplite.com> wrote ----

Sorry, neglected to mention:

You'll need to either reload the udev rules or reboot to make the new rule "active".

Thank you,

David Zomaya

Tripp Lite

From: David Zomaya
 Sent: Wednesday, May 20, 2020 2:11:24 PM
 To: Tom Cooper
 Cc: nut-upsuser
 Subject: Re: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U 

Borrowing from our friends at Ask Ubuntu ( https://askubuntu.com/a/276637 ) there is. I've modified it for use with a Tripp Lite UPS and 3024 protocol below. Try disconnect/reconnect after and see what happens.

:/etc/nut$ cat /etc/udev/rules.d/90-nut-ups.rules
 # /etc/udev/rules.d/90-nut-ups.rules
 ACTION=="add", \
 SUBSYSTEM=="usb", \
 ATTR{idVendor}=="09ae", ATTR{idProduct}=="3024", \
 MODE="0660", GROUP="nut"

Thank you,

David Zomaya

Tripp Lite

From: Tom Cooper <mailto:tom at cooperfamily.xyz>
 Sent: Wednesday, May 20, 2020 2:02 PM
 To: David Zomaya
 Cc: nut-upsuser
 Subject: Re: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U 

Funny - I thought of that  and had tried it.  Didn't work 

I also moved it from the USB2 ports to the USB3 ports.

Same result.

I have not heard of udev, but after quick googling and glancing at an example, /etc/udev/rules.d/99-com.rules

I am not convinced that I coule come up with a formula to make a working rule.

Is there a simple sample I can copy to help figure out elevated privileges?

---- On Wed, 20 May 2020 14:56:14 -0400 David Zomaya <mailto:David_Zomaya at tripplite.com> wrote ----

"Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation
 not permitted"

Is probably an issue with NUT grabbing the UPS... can you disconnect and reconnect the USB cable and try again?

If that fails, maybe a udev rule will help.

Thank you,

David Zomaya

Tripp Lite

http://www.tripplite.com/

From: Tom Cooper <mailto:tom at cooperfamily.xyz>
 Sent: Wednesday, May 20, 2020 1:54:20 PM
 To: David Zomaya
 Cc: nut-upsuser
 Subject: Re: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U

David,

I appreciate the quick feedback!

If I didn't fat finger any of the parameters you sent me, it's still not working.

Here's the output from the attempt to start.  (BTW - nothing appears in the daemon.log when I use the upsdrvctl command.)

pi at elmer:/home/macbackup $ sudo vi /etc/nut/nut.conf

pi at elmer:/home/macbackup $ sudo vi /etc/nut/ups.conf

pi at elmer:/home/macbackup $ sudo vi /etc/nut/upsd.conf

pi at elmer:/home/macbackup $ sudo upsdrvctl start

Network UPS Tools - UPS driver controller 2.7.4

Network UPS Tools - Generic HID driver 0.41 (2.7.4)

USB communication driver 0.33

Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation not permitted

Driver failed to start (exit status=1)

Network UPS Tools - Generic HID driver 0.41 (2.7.4)

USB communication driver 0.33

Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation not permitted

Driver failed to start (exit status=1)

Network UPS Tools - Generic HID driver 0.41 (2.7.4)

USB communication driver 0.33

Can't claim USB device [09ae:3024]: could not detach kernel driver from interface 0: Operation not permitted

Driver failed to start (exit status=1)

---- On Wed, 20 May 2020 14:03:09 -0400 David Zomaya <mailto:David_Zomaya at tripplite.com> wrote ----

My thoughts for a test:

Just have 

MODE=standalone
 in nut.conf

Put 

[tripplite]

     driver = usbhid-ups

     port = auto

     productid=3024

     desc = "Tripp Lite Internet600U"

In ups.conf

Put 

 LISTEN 127.0.0.1 3493
  LISTEN ::1 3493

[tripplite]

     driver = usbhid-ups

     port = auto

in upsd.conf

That may be suboptimal but will probably work for a test.

Side note: I use "upsdrvctl start/stop" to start and stop the driver. 

Thank you,

David Zomaya

Tripp Lite

From: Tom Cooper <mailto:tom at cooperfamily.xyz>
 Sent: Wednesday, May 20, 2020 12:55 PM
 To: David Zomaya
 Cc: nut-upsuser
 Subject: Re: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U

David,

That's exciting - but I am not seeing similar results.  

I *must* be doing something dumb - but I can't see it.

I've got nut-2.7.4-8 installed on my pi

Hope you can help.

Tom

pi at elmer:/home/macbackup $ lsusb | grep ipp

Bus 001 Device 004: ID 09ae:3024 Tripp Lite

pi at elmer:/home/macbackup $ sudo cat /etc/nut/nut.conf

# Network UPS Tools: example nut.conf

#

##############################################################################

# General section

##############################################################################

# The MODE determines which part of the NUT is to be started, and which

# configuration files must be modified.

#

# This file try to standardize the various files being found in the field, like

# /etc/default/nut on Debian based systems, /etc/sysconfig/ups on RedHat based

# systems, ... Distribution's init script should source this file to see which

# component(s) has to be started.

#

# The values of MODE can be:

# - none: NUT is not configured, or use the Integrated Power Management, or use

#   some external system to startup NUT components. So nothing is to be started.

# - standalone: This mode address a local only configuration, with 1 UPS

#   protecting the local system. This implies to start the 3 NUT layers (driver,

#   upsd and upsmon) and the matching configuration files. This mode can also

#   address UPS redundancy.

# - netserver: same as for the standalone configuration, but also need

#   some more network access controls (firewall, tcp-wrappers) and possibly a

#   specific LISTEN directive in upsd.conf.

#   Since this MODE is opened to the network, a special care should be applied

#   to security concerns.

# - netclient: this mode only requires upsmon.

#

# IMPORTANT NOTE:

#  This file is intended to be sourced by shell scripts.

#  You MUST NOT use spaces around the equal sign!

MODE=none

[tripplite]

     driver = usbhid-ups

     port = auto

     productid=3024

     desc = "Tripp Lite Internet600U"

pi at elmer:/home/macbackup $ sudo systemctl start nut-driver

Job for nut-driver.service failed because the control process exited with error code.

See "systemctl status nut-driver.service" and "journalctl -xe" for details.

>From the log file:

May 20 13:51:47 elmer systemd[1]: Starting Network UPS Tools - power device driver controller...

May 20 13:51:47 elmer upsdrvctl[2658]: This TrippLite device (09ae:3024) is not (or perhaps not yet) supported

May 20 13:51:47 elmer upsdrvctl[2658]: by usbhid-ups. Please make sure you have an up-to-date version of NUT. If

May 20 13:51:47 elmer upsdrvctl[2658]: this does not fix the problem, try running the driver with the

May 20 13:51:47 elmer upsdrvctl[2658]: '-x productid=3024' option. Please report your results to the NUT user's

May 20 13:51:47 elmer upsdrvctl[2658]: mailing list <mailto:nut-upsuser at lists.alioth.debian.org>.

May 20 13:51:47 elmer upsdrvctl[2658]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)

May 20 13:51:47 elmer upsdrvctl[2658]: USB communication driver 0.33

May 20 13:51:47 elmer upsdrvctl[2658]: No matching HID UPS found

May 20 13:51:47 elmer upsdrvctl[2658]: Driver failed to start (exit status=1)

May 20 13:51:52 elmer upsdrvctl[2658]: This TrippLite device (09ae:3024) is not (or perhaps not yet) supported

May 20 13:51:52 elmer upsdrvctl[2658]: by usbhid-ups. Please make sure you have an up-to-date version of NUT. If

May 20 13:51:52 elmer upsdrvctl[2658]: this does not fix the problem, try running the driver with the

May 20 13:51:52 elmer upsdrvctl[2658]: '-x productid=3024' option. Please report your results to the NUT user's

May 20 13:51:52 elmer upsdrvctl[2658]: mailing list <mailto:nut-upsuser at lists.alioth.debian.org>.

May 20 13:51:52 elmer upsdrvctl[2658]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)

May 20 13:51:52 elmer upsdrvctl[2658]: USB communication driver 0.33

May 20 13:51:52 elmer upsdrvctl[2658]: No matching HID UPS found

May 20 13:51:52 elmer upsdrvctl[2658]: Driver failed to start (exit status=1)

May 20 13:51:58 elmer upsdrvctl[2658]: This TrippLite device (09ae:3024) is not (or perhaps not yet) supported

May 20 13:51:58 elmer upsdrvctl[2658]: by usbhid-ups. Please make sure you have an up-to-date version of NUT. If

May 20 13:51:58 elmer upsdrvctl[2658]: this does not fix the problem, try running the driver with the

May 20 13:51:58 elmer upsdrvctl[2658]: '-x productid=3024' option. Please report your results to the NUT user's

May 20 13:51:58 elmer upsdrvctl[2658]: mailing list <mailto:nut-upsuser at lists.alioth.debian.org>.

May 20 13:51:58 elmer upsdrvctl[2658]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)

May 20 13:51:58 elmer upsdrvctl[2658]: USB communication driver 0.33

May 20 13:51:58 elmer upsdrvctl[2658]: No matching HID UPS found

May 20 13:51:58 elmer systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE

May 20 13:51:58 elmer upsdrvctl[2658]: Driver failed to start (exit status=1)

May 20 13:51:58 elmer upsdrvctl[2658]: Network UPS Tools - UPS driver controller 2.7.4

May 20 13:51:58 elmer systemd[1]: nut-driver.service: Failed with result 'exit-code'.

May 20 13:51:58 elmer systemd[1]: Failed to start Network UPS Tools - power device driver controller.

---- On Wed, 20 May 2020 13:46:09 -0400 David Zomaya <mailto:David_Zomaya at tripplite.com> wrote ----

Tested a Ubuntu 18.04 LTS virtual machine with NUT 2.7.4 and a 3024 protocol Tripp Lite UPS (mine is a INTERNET550U, but same protocol) 

:/etc/nut$ lsusb | grep Tripp
 Bus 002 Device 004: ID 09ae:3024 Tripp Lite

I it got generally working (outputting reasonable responses to upsc, although there are some issues with variables like frequency) by adding productid=3024 to my ups.conf. Like this:

[TrippLiteUPS3024]
         driver = usbhid-ups
         port = auto
         productid=3024

Here is the upsc output:

:/etc/nut$ sudo upsc TrippLiteUPS3024
 Init SSL without certificate database
 battery.charge: 100
 battery.charge.warning: 30
 battery.runtime: 1850
 battery.type: PbAc
 battery.voltage: 0.0
 battery.voltage.nominal: 12.0
 device.mfr: Tripp Lite
 device.model: INTERNET550U
 device.serial: 2951EVLBC87B503245
 device.type: ups
 driver.name: usbhid-ups
 driver.parameter.pollfreq: 30
 driver.parameter.pollinterval: 2
 driver.parameter.port: auto
 driver.parameter.productid: 3024
 driver.parameter.synchronous: no
 driver.version: 2.7.4
 driver.version.data: TrippLite HID 0.82
 driver.version.internal: 0.41
 input.frequency: 6010.0
 input.transfer.high: 145.0
 input.transfer.low: 95.0
 input.voltage: 0.0
 input.voltage.nominal: 120
 output.current: 0.0
 output.frequency: 6010.0
 output.frequency.nominal: 60
 output.voltage: 0.0
 output.voltage.nominal: 120
 ups.beeper.status: disabled
 ups.delay.shutdown: 20
 ups.delay.start: 30
 ups.load: 0
 ups.mfr: Tripp Lite
 ups.model: INTERNET550U
 ups.power: 0.0
 ups.power.nominal: 550
 ups.productid: 3024
 ups.serial: 2951EVLBC87B503245
 ups.status: OL
 ups.timer.reboot: 65535
 ups.timer.shutdown: 65535
 ups.timer.start: 65535
 ups.vendorid: 09ae
 ups.watchdog.status: 0
 :/etc/nut$

Tom: Let me know if this helps you.

List in general: would this help solve general 3024 issues?

Thank you,

David Zomaya

Tripp Litehttp://www.tripplite.com/ 

From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=mailto:tripplite.com at alioth-lists.debian.net>
 on behalf of David Zomaya
 Sent: Wednesday, May 20, 2020 8:49 AM
 To: Tom Cooper
 Cc: nut-upsuser
 Subject: [POSSIBLE FRAUD] Re: [Nut-upsuser] [EXTERNAL] Re: Help with Tripp Lite Internet600U

Will do. Ball in my court for now.

Thank you,

David Zomaya

Tripp Litehttp://www.tripplite.com/ 

From: Tom Cooper <mailto:tom at cooperfamily.xyz>
 Sent: Wednesday, May 20, 2020 8:47:28 AM
 To: David Zomaya
 Cc: nut-upsuser
 Subject: Re: [EXTERNAL] Re: [Nut-upsuser] Help with Tripp Lite Internet600U

That would be great.  If there is something I can do to collect data or troubleshoot, please let me know.

---- On Wed, 20 May 2020 08:51:14 -0400 David Zomaya <mailto:David_Zomaya at tripplite.com> wrote ----

I'm still working remotely, but I should be able to get something set up soon.

I'll reply all here once I have something to report.

Thank you,

David Zomaya

Tripp Litehttp://www.tripplite.com/ 

From: Tom Cooper <mailto:tom at cooperfamily.xyz>
 Sent: Wednesday, May 20, 2020 7:48:32 AM
 To: David Zomaya
 Cc: nut-upsuser
 Subject: Re: [EXTERNAL] Re: [Nut-upsuser] Help with Tripp Lite Internet600U

I'm running Raspbian Buster, but given that the error seems to be "higher order" than a hardware issue - one of parsing the protocol?  I suspect that Ubuntu would be a decent "lookalike" to model the issue. 

---- On Tue, 19 May 2020 22:31:56 -0400 David Zomaya <mailto:David_Zomaya at tripplite.com> wrote ----

If I installed and tested against Ubuntu, how useful would that be in general and in this specific case? 

I think we've seen a few reports of issues with the newer 3024 protocols and I'd like to help get them sorted out. 

Thank you,

David Zomaya

Tripp Lite

From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=mailto:tripplite.com at alioth-lists.debian.net>
 on behalf of Charles Lepple <mailto:clepple at gmail.com>
 Sent: Tuesday, May 19, 2020 9:24 PM
 To: Tom Cooper
 Cc: nut-upsuser
 Subject: [EXTERNAL] Re: [Nut-upsuser] Help with Tripp Lite Internet600U

This is an EXTERNAL email.  Please take a moment and think before clicking any links or opening any attachments from this email.  If suspicious, please forward to mailto:ishelpdesk at tripplite.com for review.

 ______________________________________________________________________
 On May 19, 2020, at 9:21 PM, Tom Cooper <mailto:tom at cooperfamily.xyz> wrote:
 > 
 > Bus 001 Device 004: ID 09ae:3024 Tripp Lite 
 > 
 We have only had reports of success with protocol 2010 of INTERNET600U (which would be 09ae:2010 in lsusb).

 More details: https://urldefense.proofpoint.com/v2/url?u=https-3A__alioth-2Dlists.debian.net_pipermail_nut-2Dupsuser_2020-2DApril_011803.html&d=DwIGaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=PY3fmIYRp20XyPJAWtuIoMta82maER1CGSdOB3x6HEM&s=9Ri1IbEOy_cyZZctw4a1IFxUMKAIwhu2xTRnjanyorI&e= 

 _______________________________________________
 Nut-upsuser mailing list
 mailto:Nut-upsuser at alioth-lists.debian.net
 https://urldefense.proofpoint.com/v2/url?u=https-3A__alioth-2Dlists.debian.net_cgi-2Dbin_mailman_listinfo_nut-2Dupsuser&d=DwIGaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=PY3fmIYRp20XyPJAWtuIoMta82maER1CGSdOB3x6HEM&s=374XOzWi2asZji_KmGBZFGWtzgxtuHrjfrzcGP8Fsvw&e= 
 _______________________________________________
 Nut-upsuser mailing list
 mailto:Nut-upsuser at alioth-lists.debian.net
 https://urldefense.proofpoint.com/v2/url?u=https-3A__alioth-2Dlists.debian.net_cgi-2Dbin_mailman_listinfo_nut-2Dupsuser&d=DwIGaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=PY3fmIYRp20XyPJAWtuIoMta82maER1CGSdOB3x6HEM&s=374XOzWi2asZji_KmGBZFGWtzgxtuHrjfrzcGP8Fsvw&e= 

This message is for the addressee's use only. It may contain confidential information. If you receive this message in error, please delete it and notify the sender. Tripp Lite disclaims all warranties and liabilities,
 and assumes no responsibility for viruses which may infect an email sent to you from Tripp Lite and which damage your electronic systems or information. It is your responsibility to maintain virus detection systems to prevent damage to your electronic systems
 and information.

This message is for the addressee's use only. It may contain confidential information. If you receive this message in error, please delete it and notify the sender. Tripp Lite disclaims all warranties and liabilities, and assumes
 no responsibility for viruses which may infect an email sent to you from Tripp Lite and which damage your electronic systems or information. It is your responsibility to maintain virus detection systems to prevent damage to your electronic systems and information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200520/02aaf26b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.png
Type: image/png
Size: 1382 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200520/02aaf26b/attachment-0001.png>