[Nut-upsuser] [EXTERNAL] Re: Tripp-Lite USB "REMOTE SHUTDOWN"

Thu Aug 19 21:22:45 BST 2021

> Wondering further: Could it be the UPS itself?

So, given what I know so far, my answer is "yes and no".
Yes: I think there is a good chance something is going wrong with these specific units.
No it's not a general reproducible problem across all like models. How do we know? From data with other users, we know it's not a problem across all UPSes of this type. We have swapped with UPSes of the same protocol and installed them in the same application without issue.

> Might test that by booting the system without data-connection to the UPS, to check if it is NUT and files on the system "misbehaving" or the UPS...
What files would make the most sense to check?

> There are many devices of varied smartness out there, so many things are possible.
I have or can get most of the protocol level detail.

Thank you,
David Zomaya
Tripp Lite

From: Jim Klimov <jimklimov at gmail.com>
Sent: Thursday, August 19, 2021 3:02 PM
To: Aaron Stewart
Cc: David Zomaya; Jim Klimov; Arnaud Quette via Nut-upsuser
Subject: Re: [Nut-upsuser] [EXTERNAL] Re: Tripp-Lite USB "REMOTE SHUTDOWN"

Wondering further: Could it be the UPS itself?

Say, something among the test commands tells it to power off after a timeout or when load drops, and UPS announces back the FSD for its load to hurry up powering off, so a newly started NUT forwards that to upsmon...

Might test that by booting the system without data-connection to the UPS, to check if it is NUT and files on the system "misbehaving" or the UPS...

There are many devices of varied smartness out there, so many things are possible.

Jim

On Thu, Aug 19, 2021, 20:24 Aaron Stewart <aaron.stewart at baymaterials.com> wrote:

> Back to original post, I wonder if `upsmon -c fsd` had left a file (e.g. `/tmp/killflag` or some such) that gets interpreted as an ongoing FSD when the client starts?

A malingering kill-flag occurred to me as fitting the symptoms as well, but I found no trace of it in the default location. Plus, since the cycle was killing and rebooting my server, as you said, the invisible flag would have to be persisting across boots.

cid:f5861ddd-5087-4089-98fb-5f73b0b8f50a

IT & Office Manager

        P Please consider the environment before printing this e-mail.
‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
Disclaimer

This message may contain confidential information and is intended only for the individual(s) or entities named above. Any review, retransmission, dissemination, distribution, copying or other use of this information by persons or entities other than the intended recipient is prohibited. Please notify the sender immediately by e‑mail if you have received this e‑mail by mistake and delete this e‑mail from any and all computers it may be stored on. No liability is accepted for any errors or omissions in the contents of this message which arise as a result of e‑mail transmission. If verification is required, please request a hard‑copy version. No liability is accepted for any damage caused by any virus transmitted by this e‑mail. The recipient should check this e‑mail and any attachments for the presence of viruses.
From: David Zomaya <David_Zomaya at tripplite.com>
Sent: Thursday, August 19, 2021 10:24
To: Jim Klimov <jimklimov at cos.ru>; Aaron Stewart <aaron.stewart at baymaterials.com>;  nut-upsuser at alioth-lists.debian.net <nut-upsuser at alioth-lists.debian.net>
Subject: Re: [EXTERNAL] Re: [Nut-upsuser] Tripp-Lite USB "REMOTE SHUTDOWN"

Warning: This email originated from outside of Straumann’s trusted e-mail environment. Do not click any links or open attachments unless you recognize the sender and have confidence the content is safe.

> Back to original post, I wonder if `upsmon -c fsd` had left a file (e.g. `/tmp/killflag` or some such) that gets interpreted as an ongoing FSD when the client starts?

...

Interesting ideas... I might pick your brain when I get my next round of testing set up...

Thank you,
David Zomaya
Tripp Lite

________________________________
 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 at alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

________________________________
 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.