ZoneMinder Forums

Not sure if it helps, but I downgraded to 1.37.60 - and everything is running perfectly.

Updated to the latest version and still getting crashes. This is generated after clicking "Force Alarm" on the Web GUI. At least it's not filling up the disk space anymore - it only seems to log it a few times and then stops. 07/15/24 10:10:03.648320 zmc_m1[1454].ERR-zm_signal.cpp/54 [Got signal 11 ...

So I restarted the zoneminder service this morning to see what it would do - and it immediately crashed on monitor 5. 07/09/24 08:25:32.741746 zmc_m5[39352].ERR-zm_signal.cpp/82 [Signal address is (nil), from 0x7ff97d811399] 07/09/24 08:25:32.741769 zmc_m5[39352].ERR-zm_signal.cpp/108 [Backtrace 0 ...

When a motion event is activated, I get the following crash. It fills up the log files and eventually run out of disk space. Version: 1.37.62 - Updated via APT today. uname -a Linux cctv 5.15.0-113-generic #123-Ubuntu SMP Mon Jun 10 08:16:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux 07/08/24 10:33:51 ...

Okay - worked out why zmes was not getting any events. The SQL query was only looking for a monitor to be in one of these states "Modect,Mocord,Nodect" My monitors are in a state of "Monitor" Changing /usr/bin/zmeventnotification.pl to the below and it all works ( add Monitor to the SQL statement ...