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
On Aug 21, 2017, at 1:35 PM, Whiteshell Tech wrote:
>
> I ran it again on battery and upsd running, set upsrw ok and then
> shutdown.return gave an "ERR CMD-NOT-SUPPORTED" Odd thing is after running
> that I am getting random timed ups powering off for one or two
On Aug 21, 2017, at 12:45 AM, Whiteshell Tech wrote:
I have attempted to set the delay higher using "upsrw -s ups.delay.shutdown=120
TrippLiteUPS@localhost" and confirmed the value with "upsc TrippLiteUPS@localhost"
Still the UPS switches off right away.
Due to the
On Aug 21, 2017, at 8:33 AM, Charles Lepple wrote:
>
> That said, it looks like the TrippLite HID mappings (in v2.7.4 as well as
> master) are missing the "shutdown.return" command. I'd look into it further,
> but ironically, the local power company has scheduled maintenance
[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
> wrote:
>
> I have attempted to set the delay higher using "upsrw -s
> ups.delay.shutdown=120 TrippLiteUPS@localhost" and
Hello,
I am hoping someone can point me in the right direction. I am setting up
a new UPS, most things seem 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
6 matches
Mail list logo