My upssched-cmd script is not modified and having just the following lines:
case $1 in
upsgone)
logger -t upssched-cmd "The UPS has been gone for
awhile"
;;
*)
logger -t upssched-cmd "Unrecognized command: $1"
;;
esac
And thus its the same as the initial version
<https://github.com/networkupstools/nut/blob/7f2965da1f3d0319d6a3cbd78399897ce29b8b10/clients/upssched-cmd>,
so the output is as expected. I see there is a newer version
<https://github.com/networkupstools/nut/blob/master/clients/upssched-cmd>
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.
Regards,
--
Georgi
On 11.1.2020 at 17:52, Manuel Wolfshant wrote:
On January 11, 2020 3:42:15 PM GMT+02:00, Roger Price
<ro...@rogerprice.org> wrote:
>On Sat, 11 Jan 2020, Georgi D. Sotirov wrote:
>
>> Jan 11 11:49:15 sotirov-bg upsmon[2677]: UPS mgeups@localhost on
>battery
>> Jan 11 11:49:15 sotirov-bg upssched[29746]: Executing command:
>ups-on-battery
>> Jan 11 11:49:15 sotirov-bg upssched-cmd: Unrecognized command:
>ups-on-battery
>
>These lines say that you have something like
>
> AT ONBATT mgeups@localhost EXECUTE ups-on-battery
>
>declared in file upssched.conf, but script upssched-cmd does not have a
>case
>statement option or something similar to catch such a call to
>upssched-cmd.
>
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.
wolfy
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
