Big problem with zmes 6.1.28 and zm 1.36.16

Discussion topics related to mobile applications and ZoneMinder Event Server (including machine learning)
Post Reply
fontiano
Posts: 69
Joined: Wed Dec 25, 2019 10:29 am

Big problem with zmes 6.1.28 and zm 1.36.16

Post by fontiano »

On my test environment (debian 11) I upgraded zonemidner to latest stable 1.36.16 and zmes to 6.1.28. I deleted old zm db and re-configured 3 cams from scratch.

I noticed that Zmes doesn't detect the majority of events:

tail -f /var/log/zm/zmeventnotification.log

29/05/2022 11:48:22.939083 zmeventnotification[1716].INF [main:1048] [PARENT: using config file: /etc/zm/zmeventnotification.ini]
29/05/2022 11:48:22.945171 zmeventnotification[1716].INF [main:1048] [PARENT: using secrets file: /etc/zm/secrets.ini]
29/05/2022 11:48:23.031491 zmeventnotification[1716].INF [main:1048] [PARENT: Push enabled via FCM]
29/05/2022 11:48:23.032621 zmeventnotification[1716].INF [main:1048] [PARENT: MQTT Disabled]
29/05/2022 11:48:23.033389 zmeventnotification[1716].INF [main:1048] [PARENT: |------- Starting ES version: 6.1.28 ---------|]
29/05/2022 11:48:23.125145 zmeventnotification[1716].WAR [main:1056] [PARENT: WARNING: SSL is disabled, which means all traffic will be unencrypted]
29/05/2022 11:48:23.126497 zmeventnotification[1716].INF [main:1048] [PARENT: Event Notification daemon v 6.1.28 starting]
29/05/2022 11:48:23.127698 zmeventnotification[1716].INF [main:1048] [PARENT: Re-loading monitors]
29/05/2022 11:48:23.129518 zmeventnotification[1716].INF [main:1048] [PARENT: Secure WS is disabled...]
29/05/2022 11:48:23.130304 zmeventnotification[1716].INF [main:1048] [PARENT: Web Socket Event Server listening on port 9000]
29/05/2022 11:51:18.134987 zmeventnotification[1716].INF [main:1048] [PARENT: New event 989 reported for Monitor:2 (Name:Campi) Motion[last processed eid:]]
29/05/2022 11:51:18.138416 zmeventnotification[1836].INF [main:1048] [|----> FORK:Campi (2), eid:989 use hooks/start hook not being used, going to directly send out a notification if checks pass]
29/05/2022 11:51:20.140217 zmeventnotification[1836].INF [main:1048] [|----> FORK:Campi (2), eid:989 Event 989 for Monitor 2 has finished]
29/05/2022 11:51:28.136266 zmeventnotification[1716].INF [main:1048] [PARENT: New event 991 reported for Monitor:2 (Name:Campi) Motion[last processed eid:989]]
29/05/2022 11:51:28.140435 zmeventnotification[2217].INF [main:1048] [|----> FORK:Campi (2), eid:991 use hooks/start hook not being used, going to directly send out a notification if checks pass]
29/05/2022 11:51:30.142219 zmeventnotification[2217].INF [main:1048] [|----> FORK:Campi (2), eid:991 Event 991 for Monitor 2 has finished]
29/05/2022 11:51:53.135461 zmeventnotification[1716].INF [main:1048] [PARENT: New event 993 reported for Monitor:2 (Name:Campi) Motion[last processed eid:991]]
29/05/2022 11:51:53.140069 zmeventnotification[2619].INF [main:1048] [|----> FORK:Campi (2), eid:993 use hooks/start hook not being used, going to directly send out a notification if checks pass]
29/05/2022 11:51:55.142187 zmeventnotification[2619].INF [main:1048] [|----> FORK:Campi (2), eid:993 Event 993 for Monitor 2 has finished]
29/05/2022 11:53:28.136692 zmeventnotification[1716].INF [main:1048] [PARENT: Re-loading monitors]
29/05/2022 11:53:43.135142 zmeventnotification[1716].INF [main:1048] [PARENT: New event 1001 reported for Monitor:3 (Name:PiazzaleGiardino) Motion[last processed eid:]]
29/05/2022 11:53:43.139709 zmeventnotification[2989].INF [main:1048] [|----> FORK:PiazzaleGiardino (3), eid:1001 use hooks/start hook not being used, going to directly send out a notification if checks pass]
29/05/2022 11:53:53.142456 zmeventnotification[2989].INF [main:1048] [|----> FORK:PiazzaleGiardino (3), eid:1001 Event 1001 for Monitor 3 has finished]
29/05/2022 11:54:28.136936 zmeventnotification[1716].INF [main:1048] [PARENT: New event 1004 reported for Monitor:3 (Name:PiazzaleGiardino) Motion[last processed eid:1001]]
29/05/2022 11:54:28.143180 zmeventnotification[3358].INF [main:1048] [|----> FORK:PiazzaleGiardino (3), eid:1004 use hooks/start hook not being used, going to directly send out a notification if checks pass]
29/05/2022 11:54:30.145230 zmeventnotification[3358].INF [main:1048] [|----> FORK:PiazzaleGiardino (3), eid:1004 Event 1004 for Monitor 3 has finished]


the following events are missing: 990,992,994,995,996,997,998,999,1000,1002,1003

If I run sudo -u www-data /usr/bin/zmeventnotification.pl --debug I don't see errors on logs, simply it doesn't detect most of new events without apparent logic
Production: zm 1.34.26 - Debian 11 | Test: zm 1.36.33 - Debian 12
fontiano
Posts: 69
Joined: Wed Dec 25, 2019 10:29 am

Re: Big problem with zmes 6.1.28 and zm 1.36.16

Post by fontiano »

Maybe the problem is the alarm counter on "1". On logs I have a lot of alarm flaps.
Production: zm 1.34.26 - Debian 11 | Test: zm 1.36.33 - Debian 12
Post Reply