Nut upsuser - Jul 2020 - Tripp-Lite AVRX500U issues (objecttothis)

Does the github link not come through
(https://github.com/networkupstools/nut/issues/799)?  All the documentation that
Tripp-Lite sent me on the 2012 protocol and my configuration files are on that
issue.  I doubt this mailing list will allow me to attach any files.  It's
the NUT github page.

At any rate ups.conf just has this in it.  No offdelay or ondelay entries:

[ups]
        driver = usbhid-ups
        port = /dev/uhid0
        desc 
upsmon.conf seems to be what is dictating the shutdown command along with
upssched.conf:
upsmon.conf
MONITOR ups at localhost:3493 1 upsmon [REDACTED] MASTER
NOTIFYCMD "/usr/local/sbin/upssched"
NOTIFYFLAG ONBATT SYSLOG+EXEC
NOTIFYFLAG LOWBATT SYSLOG+EXEC
NOTIFYFLAG ONLINE SYSLOG+EXEC
NOTIFYFLAG COMMBAD SYSLOG+EXEC
NOTIFYFLAG COMMOK SYSLOG+EXEC
NOTIFYFLAG REPLBATT SYSLOG+EXEC
NOTIFYFLAG NOCOMM SYSLOG+EXEC
NOTIFYFLAG REPLBATT SYSLOG+EXEC
NOTIFYFLAG NOCOMM SYSLOG+EXEC
NOTIFYFLAG FSD SYSLOG+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+EXEC
SHUTDOWNCMD "/sbin/shutdown -p now"
POWERDOWNFLAG /etc/killpower
HOSTSYNC 15

upssched.conf
CMDSCRIPT   "/usr/local/bin/sudo /usr/local/bin/custom-upssched-cmd"
PIPEFN      /var/db/nut/upssched.pipe
LOCKFN      /var/db/nut/upssched.lock

AT NOCOMM   * EXECUTE NOTIFY-NOCOMM
AT COMMBAD  * START-TIMER NOTIFY-COMMBAD 10
AT COMMOK   * CANCEL-TIMER NOTIFY-COMMBAD COMMOK
AT FSD      * EXECUTE NOTIFY-FSD
AT LOWBATT  * EXECUTE NOTIFY-LOWBATT
AT ONBATT   * EXECUTE NOTIFY-ONBATT
AT ONLINE   * EXECUTE NOTIFY-ONLINE
AT REPLBATT   * EXECUTE NOTIFY-REPLBATT
AT SHUTDOWN   * EXECUTE NOTIFY-SHUTDOWN
AT ONBATT    * START-TIMER SHUTDOWN 5
AT ONLINE   * CANCEL-TIMER SHUTDOWN


-----Original Message-----
From: Nut-upsuser <nut-upsuser-bounces+objecttothis=gmail.com at
alioth-lists.debian.net> On Behalf Of nut-upsuser-request at
alioth-lists.debian.net
Sent: Monday, July 13, 2020 3:00 PM
To: nut-upsuser at alioth-lists.debian.net
Subject: Nut-upsuser Digest, Vol 181, Issue 2

Send Nut-upsuser mailing list submissions to
	nut-upsuser at alioth-lists.debian.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
or, via email, send a message with subject or body 'help' to
	nut-upsuser-request at alioth-lists.debian.net

You can reach the person managing the list at
	nut-upsuser-owner at alioth-lists.debian.net

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Nut-upsuser digest..."


Today's Topics:

   1. Tripp-Lite AVRX500U issues (objecttothis)
   2. Re: Tripp-Lite AVRX500U issues (Roger Price)


----------------------------------------------------------------------

Message: 1
Date: Mon, 13 Jul 2020 00:14:04 +0400
From: "objecttothis" <objecttothis at gmail.com>
To: <nut-upsuser at alioth-lists.debian.net>
Subject: [Nut-upsuser] Tripp-Lite AVRX500U issues
Message-ID: <000e01d65888$fea26360$fbe72a20$@gmail.com>
Content-Type: text/plain; charset="utf-8"

I have gone through Two Tripp-Lite AVRX550U units trying to troubleshoot issues.
There are two separate (but possibly related issues that I am finding.  I’ve
created an issue on the Github page, but it’s not clear that anyone looks at
those issues (https://github.com/networkupstools/nut/issues/799)

 

1.	According to Tripp-lite, the AVRX550U uses the 2012 protocol, but it’s listed
in NUT as using the 2010 protocol.   I have attached the documentation that
Tripp-Lite gave me in that github issue.
2.	After my server (FreeNAS running FreeBSD 11.3- Release) shuts down, the UPS
also powers down (as it should since it was issued a shutdown command by NUT)
but then 5 seconds later the UPS powers back up even though it’s still on
battery power.  Tripp-Lite replaced the unit, telling me that the unit was
likely defective, but the second unit exhibits the exact same behavior.

 

I don’t see any sort of command in NUT to power on the UPS, so I’m thinking that
it may be a Tripp-Lite firmware issue, but I figured I’d post it here in case
someone recognizes why it’s doing this.  The first issue, according to
Tripp-lite, is a NUT issue and needs to be fixed.

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200713/2681741b/attachment-0001.html>

------------------------------

Message: 2
Date: Sun, 12 Jul 2020 23:03:50 +0200 (CEST)
From: Roger Price <roger at rogerprice.org>
To: nut-upsuser Mailing List <nut-upsuser at lists.alioth.debian.org>
Subject: Re: [Nut-upsuser] Tripp-Lite AVRX500U issues
Message-ID: <alpine.DEB.2.20.2007122257360.7255 at maria.rogerprice.org>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

On Mon, 13 Jul 2020, objecttothis wrote:
>  1. According to Tripp-lite, the AVRX550U uses the 2012 protocol, but 
> it’s listed in NUT as using the 2010 protocol.   I have attached the 
> documentation that Tripp-Lite gave me in that github issue.
The attached text I received was empty.
>  2. After my server (FreeNAS running FreeBSD 11.3- Release) shuts 
> down, the UPS also powers down (as it should since it was issued a 
> shutdown command by
> NUT) but then 5 seconds later the UPS powers back up even though it’s 
> still on battery power.
I'm curious about your offdelay and ondelay entries in ups.conf, if you have
any.
> Tripp-Lite replaced the unit, telling me that the unit was likely 
> defective, but the second unit exhibits the exact same behavior.
Roger

------------------------------

Subject: Digest Footer

_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

------------------------------

End of Nut-upsuser Digest, Vol 181, Issue 2
*******************************************