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@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@localhost] failed - Data stale Apr 1 17:13:09 upsmon[652]: Perte de communication avec Onduleur UPS1@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@localhost Apr 1 17:13:14 upsmon[652]: Onduleur UPS1@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 <[email protected]> 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@---:~# 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@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@localhost] failed - Data > stale > Apr 1 17:13:09 upsmon[652]: Perte de communication avec Onduleur > UPS1@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@localhost > Apr 1 17:13:14 upsmon[652]: Onduleur UPS1@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 > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
