I am glad to see this is not just me having such problems. I want to find the root cause for all of those who suffer this bug. If I have the USB cable plugged in while the systems boot, it's a 50/50 chance of working, or power cycling. If it does work, then I live in fear of the next reboot! -Adam
Nut version: nut 2.7.4-8 On Tue, Feb 2, 2021 at 8:06 AM Fairfax, Charles A. via Nut-upsuser < nut-upsuser@alioth-lists.debian.net> wrote: > Sorry, the list address got dropped on prior send. > > Charles Fairfax > > -----Original Message----- > From: Fairfax, Charles A. > Sent: Tuesday, February 2, 2021 9:18 AM > To: David Zomaya <david_zom...@tripplite.com>; Adam Talbot < > ajtalb...@gmail.com> > Subject: RE: [Nut-upsuser] [EXTERNAL] Tripp Lite "Remote Shutdown" when > USB cable is attached > > I don't know that my experience is helpful except that I had what sounds > like a similar experience with a similar UPS in October of 2016. I was > attaching a Raspberry Pi (Raspbian wheezy) with NUT 2.6.4 to a TrippLite > SU3000XLCD via USB and the UPS shut down, dropping the load. I had never > seen this happen before with the 8 or so other older model TrippLite UPSs > I have in service. > > Unfortunately I was not at liberty to perform much troubleshooting owing > to the nature of the load and don't have another UPS of the same model. I > tried serial communication but was not successful. Eventually I did get > the UPS link to work. If I remember correctly I booted the Pi after > connecting the USB cable. It has been working since and I have not > unplugged the USB cable. > > Have you tried booting the computer after connecting the USB cable? > > -----Original Message----- > From: Nut-upsuser <nut-upsuser-bounces+fairfaxc= > missouri....@alioth-lists.debian.net> On Behalf Of David Zomaya via > Nut-upsuser > Sent: Monday, February 1, 2021 4:43 PM > To: Adam Talbot <ajtalb...@gmail.com>; nut-upsuser@alioth-lists.debian.net > Subject: Re: [Nut-upsuser] [EXTERNAL] Tripp Lite "Remote Shutdown" when > USB cable is attached > > I don't have a quick answer for you but I'll be in the office later this > week and can grab a model with the same protocol and run a test on one of > my Ubuntu boxes (which should be close enough to your Pi setup). > > > Thank you, > David Zomaya > Tripp Lite > > > > > > > > > From: Nut-upsuser <nut-upsuser-bounces+david_zomaya= > tripplite....@alioth-lists.debian.net> on behalf of Adam Talbot via > Nut-upsuser <nut-upsuser@alioth-lists.debian.net> > Sent: Monday, February 1, 2021 3:39 PM > To: nut-upsuser@alioth-lists.debian.net > Subject: [EXTERNAL] [Nut-upsuser] Tripp Lite "Remote Shutdown" when USB > cable is attached > > 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 ishelpd...@tripplite.com for review. > I am kinda stuck on this one. Whenever I attach (USB to a linux box) my > TrippLite UPS, it "REMOTE SHUTDOWN". This is a new problem that has > cropped up in the last 6 months. At first I thought it was a NUT > configuration issue, but now I believe this to be some kind of kernel > bug? When I plug in the UPS, I can see the system logs show the UPS, then > everything powers off. > > > UPS LCD shows the below error when I plug in the USB cable: > "OUTPUT OFF" > "REMOTE SHUTDOWN" > > > I tested this against 2 different X86 boxes and a Raspberry Pi. All cause > the same result in the UPS. Only one box (nas) has NUT installed and > configured. > > > UPS is a Tripp Lite SU3000RTXLCD2U. > > > I am totally stumped on this one. Below is a dump of basically all my > specs. Any ideas? > -Adam > > > > root@nas:~# uname -a > Linux nas 5.4.78-2-pve #1 SMP PVE 5.4.78-2 (Thu, 03 Dec 2020 14:26:17 > +0100) x86_64 GNU/Linux > > root@nas:~# cat /etc/nut/nut.conf > MODE=netserver > root@nas:~# cat /etc/nut/ups.conf > [ups1] > driver=usbhid-ups > port=auto > root@nas:~# cat /etc/nut/upsd.conf > LISTEN 127.0.0.1 3493 > LISTEN 10.1.1.2 > root@nas:~# cat /etc/nut/upsmon.conf > root@nas:~# cat /etc/nut/upssched.conf > root@nas:~# > > root@nas:~# cat /etc/debian_version > 10.7 > > > > Before all this broke, I was able to monitor the UPS and get the following > info: > battery.charge: 100 > battery.charge.low: 20 > battery.charge.warning: 20 > battery.runtime: 6662 > battery.temperature: 29.9 > battery.type: PbAc > battery.voltage: 81.0 > battery.voltage.nominal: 72.0 > device.mfr: TRIPPLITE > device.model: TRIPPLITE UPS > device.serial: XXXXXXXXXXXXXX > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 2 > driver.parameter.port: auto > driver.parameter.synchronous: no > driver.version: 2.7.4 > driver.version.data: TrippLite HID 0.82 > driver.version.internal: 0.41 > input.frequency: 60.0 > input.transfer.high: 150.0 > input.transfer.high.max: 150 > input.transfer.high.min: 145 > input.transfer.low: 55.0 > input.transfer.low.max: 60 > input.transfer.low.min: 55 > input.voltage: 123.0 > input.voltage.nominal: 120 > output.current: 1.9 > output.frequency: 60.0 > output.frequency.nominal: 60 > output.voltage: 120.0 > output.voltage.nominal: 120 > ups.beeper.status: enabled > ups.delay.shutdown: 20 > ups.delay.start: 30 > ups.firmware: 64 > ups.load: 8 > ups.mfr: TRIPPLITE > ups.model: TRIPPLITE UPS > ups.power: 226.0 > ups.power.nominal: 3000 > ups.productid: 4004 > ups.serial: 2620ELCPS87A200020 > ups.status: OL > ups.test.result: Done and passed > ups.timer.reboot: 0 > ups.timer.shutdown: -1 > ups.timer.start: 0 > ups.vendorid: 09ae > ups.watchdog.status: 0 > > > root@nas:/var/log# zcat messages.*.gz | grep -i tripp > Jan 15 11:05:05 nas kernel: [ 1.571857] usb 3-1: Product: TRIPPLITE UPS > Jan 15 11:05:05 nas kernel: [ 1.571858] usb 3-1: Manufacturer: TRIPPLITE > Jan 15 11:05:05 nas kernel: [ 1.629210] hid-generic > 0003:09AE:4004.0001: hiddev0,hidraw0: USB HID v1.11 Device [TRIPPLITE > TRIPPLITE UPS ] on usb-0000:2e:00.3-1/input0 > > > > ________________________________ > 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. > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
