[Nut-upsuser] System with MGE UPS shuts down too early
Georgi D. Sotirov
gdsotirov at gmail.com
Sun Jan 12 10:44:03 GMT 2020
My upssched-cmd script is not modified and having just the following lines:
case $1 in
logger -t upssched-cmd "The UPS has been gone for
logger -t upssched-cmd "Unrecognized command: $1"
And thus its the same as the initial version
so the output is as expected. I see there is a newer version
from 2017-03-22 that handles also onbattwarn and ups-back-on-power, but
it wasn't included in version 2.7.4 of NUT I'm currently using.
Anyway, this is not a problem.
On 11.1.2020 at 17:52, Manuel Wolfshant wrote:
> On January 11, 2020 3:42:15 PM GMT+02:00, Roger Price
> <roger at rogerprice.org> wrote:
> >On Sat, 11 Jan 2020, Georgi D. Sotirov wrote:
> >> Jan 11 11:49:15 sotirov-bg upsmon: UPS mgeups at localhost on
> >> Jan 11 11:49:15 sotirov-bg upssched: Executing command:
> >> Jan 11 11:49:15 sotirov-bg upssched-cmd: Unrecognized command:
> >These lines say that you have something like
> > AT ONBATT mgeups at localhost EXECUTE ups-on-battery
> >declared in file upssched.conf, but script upssched-cmd does not have a
> >statement option or something similar to catch such a call to
> That is absolutely true but I've understood that the system worked OK
> in the past. And AFAIK (please correct me if I am wrong) the missing
> command was simply ignored. And I think that the lines you quoted do
> not explain a shutdown while the line I quoted does.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser