[Nut-upsuser] wrong NOTIFYTYPE always ONBATT on upssched TIMER ?
RemiG
mailing-nut at dbmtechnologies.com
Fri Apr 4 08:52:00 BST 2025
Hi
an other test in real life (UPS sold in 2022)
ONBATT at 7h54
ONLINE at 7h58
root at minet:~# grep " ups" /var/log/syslog
Apr 4 07:53:05 minet upsmon[8374]: Onduleur UPS1 at localhost en mode
Secours sur batterie
Apr 4 07:53:05 minet upssched[24512]: Executing command: ONBATT
Apr 4 07:53:05 minet upssched-cmd-received-NOTIFYTYPE: ONBATT
Apr 4 07:53:05 minet upssched[24538]: Timer daemon started
Apr 4 07:53:05 minet upssched[24538]: New timer: BATT-STATUS-5 (300
seconds)
Apr 4 07:53:05 minet upssched[24538]: New timer: BATT-STATUS-10 (600
seconds)
Apr 4 07:53:05 minet upssched[24538]: New timer: BATT-STATUS-15 (900
seconds)
Apr 4 07:53:05 minet upssched[24538]: New timer: BATT-STATUS-20 (1200
seconds)
Apr 4 07:53:05 minet upssched[24538]: New timer: BATT-STATUS-25 (1500
seconds)
Apr 4 07:53:05 minet upssched[24538]: New timer: BATT-STATUS-30 (1800
seconds)
Apr 4 07:53:05 minet upssched[24538]: New timer: BATT-STATUS-60 (3600
seconds)
Apr 4 07:54:30 minet upsmon[8374]: Onduleur UPS1 at localhost batterie
trop basse
Apr 4 07:54:30 minet upsmon[8374]: FSD set on UPS UPS1 at localhost
failed: ERR ACCESS-DENIED
Apr 4 07:54:30 minet upsmon[8374]: Executing automatic power-fail shutdown
Apr 4 07:54:30 minet upssched[24585]: Executing command: LOWBATT-INFO
Apr 4 07:54:30 minet upssched-cmd-received-NOTIFYTYPE: LOWBATT
Apr 4 07:54:35 minet upsmon.conf: Je ne veux pas arreter ce serveur
Apr 4 07:58:05 minet upssched[24538]: Event: BATT-STATUS-5
Apr 4 07:58:05 minet upssched-cmd-received-NOTIFYTYPE: ONBATT
Apr 4 08:03:05 minet upssched[24538]: Event: BATT-STATUS-10
Apr 4 08:03:05 minet upssched-cmd-received-NOTIFYTYPE: ONBATT
Apr 4 08:08:05 minet upssched[24538]: Event: BATT-STATUS-15
Apr 4 08:08:05 minet upssched-cmd-received-NOTIFYTYPE: ONBATT
Apr 4 08:13:05 minet upssched[24538]: Event: BATT-STATUS-20
Apr 4 08:13:05 minet upssched-cmd-received-NOTIFYTYPE: ONBATT
Apr 4 08:18:05 minet upssched[24538]: Event: BATT-STATUS-25
Apr 4 08:18:05 minet upssched-cmd-received-NOTIFYTYPE: ONBATT
Apr 4 08:23:05 minet upssched[24538]: Event: BATT-STATUS-30
Apr 4 08:23:05 minet upssched-cmd-received-NOTIFYTYPE: ONBATT
Apr 4 08:53:05 minet upssched[24538]: Event: BATT-STATUS-60
Apr 4 08:53:05 minet upssched-cmd-received-NOTIFYTYPE: ONBATT
Apr 4 08:53:20 minet upssched[24538]: Timer queue empty, exiting
root at minet:~# upsc -V => Network UPS Tools upscmd 2.7.2
root at minet:~# upsc UPS1
Init SSL without certificate database
battery.charge: 90
battery.charge.low: 20
battery.runtime: 895
battery.type: PbAc
device.mfr: EATON
device.model: Ellipse PRO 650
device.serial: G354M26707
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.7.2
driver.version.data: MGE HID 1.33
driver.version.internal: 0.38
input.frequency: 50.0
input.transfer.high: 285
input.transfer.low: 165
input.voltage: 237.0
input.voltage.extended: no
outlet.1.desc: PowerShare Outlet 1
outlet.1.id: 2
outlet.1.status: on
outlet.1.switchable: no
outlet.2.desc: PowerShare Outlet 2
outlet.2.id: 3
outlet.2.status: on
outlet.2.switchable: no
outlet.desc: Main Outlet
outlet.id: 1
outlet.switchable: no
output.frequency: 50.0
output.frequency.nominal: 50
output.voltage: 238.0
output.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 01.16.0020
ups.load: 24
ups.mfr: EATON
ups.model: Ellipse PRO 650
ups.power: 147
ups.power.nominal: 650
ups.productid: ffff
ups.realpower: 99
ups.serial: G354M26707
ups.status: OL CHRG
ups.timer.shutdown: 0
ups.timer.start: 0
ups.vendorid: 0463
upssched.conf
# info2client
AT ONLINE * EXECUTE ONLINE
# info2admin only
AT ONLINE * CANCEL-TIMER BATT-STATUS-5
AT ONLINE * CANCEL-TIMER BATT-STATUS-10
AT ONLINE * CANCEL-TIMER BATT-STATUS-15
AT ONLINE * CANCEL-TIMER BATT-STATUS-20
AT ONLINE * CANCEL-TIMER BATT-STATUS-25
AT ONLINE * CANCEL-TIMER BATT-STATUS-30
AT ONLINE * CANCEL-TIMER BATT-STATUS-60
AT ONLINE * START-TIMER LINE-STATUS-5 300
AT ONLINE * START-TIMER LINE-STATUS-10 600
AT ONLINE * START-TIMER LINE-STATUS-15 900
AT ONLINE * START-TIMER LINE-STATUS-20 1200
AT ONLINE * START-TIMER LINE-STATUS-25 1500
AT ONLINE * START-TIMER LINE-STATUS-30 1800
AT ONLINE * START-TIMER LINE-STATUS-60 3600
#
# info2client
AT ONBATT * EXECUTE ONBATT
# info2admin only
AT ONBATT * CANCEL-TIMER LINE-STATUS-5
AT ONBATT * CANCEL-TIMER LINE-STATUS-10
AT ONBATT * CANCEL-TIMER LINE-STATUS-15
AT ONBATT * CANCEL-TIMER LINE-STATUS-20
AT ONBATT * CANCEL-TIMER LINE-STATUS-25
AT ONBATT * CANCEL-TIMER LINE-STATUS-30
AT ONBATT * CANCEL-TIMER LINE-STATUS-60
AT ONBATT * START-TIMER BATT-STATUS-5 300
AT ONBATT * START-TIMER BATT-STATUS-10 600
AT ONBATT * START-TIMER BATT-STATUS-15 900
AT ONBATT * START-TIMER BATT-STATUS-20 1200
AT ONBATT * START-TIMER BATT-STATUS-25 1500
AT ONBATT * START-TIMER BATT-STATUS-30 1800
AT ONBATT * START-TIMER BATT-STATUS-60 3600
# info2client
AT REPLBATT * ONBATT * EXECUTE REPLBATT
AT NOCOMM * EXECUTE NOCOMM
AT FSD * EXECUTE FSD
AT SHUTDOWN * EXECUTE SHUTDOWN
# info2admin only
AT LOWBATT * EXECUTE LOWBATT-INFO
AT COMMOK * EXECUTE COMMOK-INFO
AT COMMBAD * EXECUTE COMMBAD-INFO
and part of upssched-cmd
=============================
echo -e "$NOTIFYTYPE" | logger -t upssched-cmd-received-NOTIFYTYPE
case "$1-$Battery_status" in
ONLINE-*|ONBATT-*|REPLBATT-*|SHUTDOWN)
Message_for_client
;;
=============================
Le 02/04/2025 à 09:02, Jim Klimov a écrit :
> Well, either I misunderstood what you wrote or (my initially written
> post follows, probably misguided at start) I think your log
> contradicts your statements:
>
> > when my bash script receive events from TIMER like LINE-STATUS-xx
> > NOTIFYTYPE is always ONBATT
> > in all other cases, NOTIFYTYPE is TRUE and same as it was called by
> upsmon
>
> in the log I see :
>
> * Initial ONBATT:
>
> Apr 1 17:07:39 upsmon[652]: Onduleur UPS1 at localhost en mode Secours
> sur batterie
> Apr 1 17:07:39 upssched[9126]: Executing command: ONBATT
> Apr 1 17:07:39 upssched-cmd-received-NOTIFYTYPE: ONBATT
> Apr 1 17:07:39 upssched[8783]: Cancelling timer: LINE-STATUS-5
> ...
> Apr 1 17:07:39 upssched[8783]: New timer: BATT-STATUS-5 (300 seconds)
> ...
>
> * Handler for BATT-STATUS-5 fired and issued ONBATT after 5 min:
>
> Apr 1 17:12:39 upssched[8783]: Event: BATT-STATUS-5
> Apr 1 17:12:39 upssched-cmd-received-NOTIFYTYPE: ONBATT
>
> * Loss of comms (NUT driver down?):
>
> Apr 1 17:13:06 upsd[7074]: Data for UPS [UPS1] is stale - check driver
>
> Apr 1 17:13:09 upsmon[652]: Poll UPS [UPS1 at localhost] failed - Data
> stale
> Apr 1 17:13:09 upsmon[652]: Perte de communication avec Onduleur
> UPS1 at localhost
> Apr 1 17:13:09 upssched[9277]: Executing command: COMMBAD-INFO
> Apr 1 17:13:09 upssched-cmd-received-NOTIFYTYPE: COMMBAD
>
> * Restarted comms and ONLINE (note there is a lag between upsd seeing
> the driver/data is back, and upsmon polling seeing and propagating that):
>
> Apr 1 17:13:09 upsd[7074]: UPS [UPS1] data is no longer stale
>
> Apr 1 17:13:14 upsmon[652]: Retablissement des communications avec
> UPS1 at localhost
> Apr 1 17:13:14 upsmon[652]: Onduleur UPS1 at localhost en mode Secteur
> : recharge batterie en cours
> Apr 1 17:13:14 upssched[9307]: Executing command: ONLINE
> Apr 1 17:13:14 upssched[9306]: Executing command: COMMOK-INFO
> Apr 1 17:13:14 upssched-cmd-received-NOTIFYTYPE: COMMOK
> Apr 1 17:13:14 upssched-cmd-received-NOTIFYTYPE: ONLINE
> Apr 1 17:13:14 upssched[8783]: Cancelling timer: BATT-STATUS-10
> ...
> Apr 1 17:13:14 upssched[8783]: New timer: LINE-STATUS-5 (300 seconds)
> ...
>
> So in fact I see many different NOTIFYTYPE values and none is "TRUE".
>
> * Oh, NOW I think I get what you meant:
>
> Apr 1 17:18:14 upssched[8783]: Event: LINE-STATUS-5
> Apr 1 17:18:14 upssched-cmd-received-NOTIFYTYPE: ONBATT
>
>
> Just in case, which NUT version is involved?
>
> Jim
>
>
>
> On Tue, Apr 1, 2025 at 5:42 PM RemiG <mailing-nut at dbmtechnologies.com>
> wrote:
>
> HI
>
> i'am using schema upsmon call : NOTIFYCMD /sbin/upssched
>
> and this part of upsschede strategy (working fine)
>
> device.model: Ellipse ECO 650
>
> root at ---:~# cat /etc/nut/upssched.conf
> # Network UPS Tools - upssched.conf sample file
>
> CMDSCRIPT /opt/nut/bin/upssched-cmd
>
> PIPEFN /var/run/nut/upssched.pipe
> LOCKFN /var/run/nut/upssched.lock
>
> #
> ============================================================================
> # info2client
> AT ONLINE * EXECUTE ONLINE
> # info2admin only
> AT ONLINE * CANCEL-TIMER BATT-STATUS-5
> AT ONLINE * CANCEL-TIMER BATT-STATUS-10
> AT ONLINE * CANCEL-TIMER BATT-STATUS-15
> AT ONLINE * CANCEL-TIMER BATT-STATUS-20
> AT ONLINE * CANCEL-TIMER BATT-STATUS-25
> AT ONLINE * CANCEL-TIMER BATT-STATUS-30
> AT ONLINE * CANCEL-TIMER BATT-STATUS-60
> AT ONLINE * START-TIMER LINE-STATUS-5 300
> AT ONLINE * START-TIMER LINE-STATUS-10 600
> AT ONLINE * START-TIMER LINE-STATUS-15 900
> AT ONLINE * START-TIMER LINE-STATUS-20 1200
> AT ONLINE * START-TIMER LINE-STATUS-25 1500
> AT ONLINE * START-TIMER LINE-STATUS-30 1800
> AT ONLINE * START-TIMER LINE-STATUS-60 3600
> #
> # info2client
> AT ONBATT * EXECUTE ONBATT
> # info2admin only
> AT ONBATT * CANCEL-TIMER LINE-STATUS-5
> AT ONBATT * CANCEL-TIMER LINE-STATUS-10
> AT ONBATT * CANCEL-TIMER LINE-STATUS-15
> AT ONBATT * CANCEL-TIMER LINE-STATUS-20
> AT ONBATT * CANCEL-TIMER LINE-STATUS-25
> AT ONBATT * CANCEL-TIMER LINE-STATUS-30
> AT ONBATT * CANCEL-TIMER LINE-STATUS-60
> AT ONBATT * START-TIMER BATT-STATUS-5 300
> AT ONBATT * START-TIMER BATT-STATUS-10 600
> AT ONBATT * START-TIMER BATT-STATUS-15 900
> AT ONBATT * START-TIMER BATT-STATUS-20 1200
> AT ONBATT * START-TIMER BATT-STATUS-25 1500
> AT ONBATT * START-TIMER BATT-STATUS-30 1800
> AT ONBATT * START-TIMER BATT-STATUS-60 3600
>
> when my bash script receive events from TIMER like LINE-STATUS-xx
> NOTIFYTYPE is always ONBATT
>
> in all other cases, NOTYFYTYPE is TRUE and same as it was called
> by upsmon
>
> what is wrong ?
>
> my parsed log for this situation :
> ===============
> Apr 1 17:07:39 upsmon[652]: Onduleur UPS1 at localhost en mode
> Secours sur batterie
> Apr 1 17:07:39 upssched[9126]: Executing command: ONBATT
> Apr 1 17:07:39 upssched-cmd-received-NOTIFYTYPE: ONBATT
> Apr 1 17:07:39 upssched[8783]: Cancelling timer: LINE-STATUS-5
> Apr 1 17:07:39 upssched[8783]: Cancelling timer: LINE-STATUS-10
> Apr 1 17:07:39 upssched[8783]: Cancelling timer: LINE-STATUS-15
> Apr 1 17:07:39 upssched[8783]: Cancelling timer: LINE-STATUS-20
> Apr 1 17:07:39 upssched[8783]: Cancelling timer: LINE-STATUS-25
> Apr 1 17:07:39 upssched[8783]: Cancelling timer: LINE-STATUS-30
> Apr 1 17:07:39 upssched[8783]: Cancelling timer: LINE-STATUS-60
> Apr 1 17:07:39 upssched[8783]: New timer: BATT-STATUS-5 (300
> seconds)
> Apr 1 17:07:39 upssched[8783]: New timer: BATT-STATUS-10 (600
> seconds)
> Apr 1 17:07:39 upssched[8783]: New timer: BATT-STATUS-15 (900
> seconds)
> Apr 1 17:07:39 upssched[8783]: New timer: BATT-STATUS-20 (1200
> seconds)
> Apr 1 17:07:39 upssched[8783]: New timer: BATT-STATUS-25 (1500
> seconds)
> Apr 1 17:07:39 upssched[8783]: New timer: BATT-STATUS-30 (1800
> seconds)
> Apr 1 17:07:39 upssched[8783]: New timer: BATT-STATUS-60 (3600
> seconds)
> Apr 1 17:12:39 upssched[8783]: Event: BATT-STATUS-5
> Apr 1 17:12:39 upssched-cmd-received-NOTIFYTYPE: ONBATT
> Apr 1 17:13:06 upsd[7074]: Data for UPS [UPS1] is stale - check
> driver
> Apr 1 17:13:09 upsmon[652]: Poll UPS [UPS1 at localhost] failed -
> Data stale
> Apr 1 17:13:09 upsmon[652]: Perte de communication avec Onduleur
> UPS1 at localhost
> Apr 1 17:13:09 upssched[9277]: Executing command: COMMBAD-INFO
> Apr 1 17:13:09 upssched-cmd-received-NOTIFYTYPE: COMMBAD
> Apr 1 17:13:09 upsd[7074]: UPS [UPS1] data is no longer stale
> Apr 1 17:13:14 upsmon[652]: Retablissement des communications
> avec UPS1 at localhost
> Apr 1 17:13:14 upsmon[652]: Onduleur UPS1 at localhost en mode
> Secteur : recharge batterie en cours
> Apr 1 17:13:14 upssched[9307]: Executing command: ONLINE
> Apr 1 17:13:14 upssched[9306]: Executing command: COMMOK-INFO
> Apr 1 17:13:14 upssched-cmd-received-NOTIFYTYPE: COMMOK
> Apr 1 17:13:14 upssched-cmd-received-NOTIFYTYPE: ONLINE
> Apr 1 17:13:14 upssched[8783]: Cancelling timer: BATT-STATUS-10
> Apr 1 17:13:14 upssched[8783]: Cancelling timer: BATT-STATUS-15
> Apr 1 17:13:14 upssched[8783]: Cancelling timer: BATT-STATUS-20
> Apr 1 17:13:14 upssched[8783]: Cancelling timer: BATT-STATUS-25
> Apr 1 17:13:14 upssched[8783]: Cancelling timer: BATT-STATUS-30
> Apr 1 17:13:14 upssched[8783]: Cancelling timer: BATT-STATUS-60
> Apr 1 17:13:14 upssched[8783]: New timer: LINE-STATUS-5 (300
> seconds)
> Apr 1 17:13:14 upssched[8783]: New timer: LINE-STATUS-10 (600
> seconds)
> Apr 1 17:13:14 upssched[8783]: New timer: LINE-STATUS-15 (900
> seconds)
> Apr 1 17:13:14 upssched[8783]: New timer: LINE-STATUS-20 (1200
> seconds)
> Apr 1 17:13:14 upssched[8783]: New timer: LINE-STATUS-25 (1500
> seconds)
> Apr 1 17:13:14 upssched[8783]: New timer: LINE-STATUS-30 (1800
> seconds)
> Apr 1 17:13:14 upssched[8783]: New timer: LINE-STATUS-60 (3600
> seconds)
> Apr 1 17:18:14 upssched[8783]: Event: LINE-STATUS-5
> Apr 1 17:18:14 upssched-cmd-received-NOTIFYTYPE: ONBATT
>
> --
> # admin linux only ;-)
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
--
# admin linux only ;-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20250404/49ae6f27/attachment-0001.htm>
More information about the Nut-upsuser
mailing list