ZoneMinder Forums

Hello,
After resetting to a previous backup, optimizing and checking the database and then bringing ZM back to the current version, everything seems to be working again.

Another kind of self-healing that you don't know why or why.

Many greetings
Detlef Paschke

Hello, I was a bit surprised that I haven't had any recordings in the last few days. Now I discovered the cause after I allowed the SD stream to record at the event. The SD stream registers an event, but the linked HD stream does not trigger recording. I believe the problem persists since this ...

t's the same here under Debian12, since today's update (1.37.56~20240320.53-bookworm) via (1.37.55~20240315.181-bookworm).

Best regards
Detlef Paschke

Hello, If I read "Notes" from the linked monitor 1:1 what is written in the "Cause" of the monitor with the event monitoring, you can see whether the event was triggered by the camera (ONVIF) or by Zoneminder. Currently you have no information if the monitor with event monitoring is on Norecord ...

Hello, If I activate the ONVIF_Event_Listener on a monitor, then ONVIF2 is stated as "Cause" in the recorded ONVIF events. Other events list the zones in which something occurred. In a Liked Monitor, the "Cause" field always says Linked and the "Notes" field always remains empty. Is it necessary to ...

Hello,

Today I updated from 1.37.48~20240104.28-bookworm to 1.37.50~20240127.87-bookworm and the "10 minute problem" is fixed for me.
The recordings are stopped again after the event and reaching the post-event buffer. Thank you.

Many greetings
Detlef Paschke

Hello, I updated to 1.37.50 today. I manually triggered an alarm for a few seconds. After the alarm stops, the monitor will appear as idle. However, the recording continues unnoticed in the background until 10 minutes (maximum section length 600 seconds) are reached. EVENT_CLOSE_MODE is set to idle ...

The main stream does not stop recording at all or only after the set maximum section length. The "Record on Motion" Monitor is displayed as "idle" after an event, but the recording continues to run unnoticed in the background until the set maximum section length (standard 600 seconds) is reached ...

Hello, sorry but I think it's even worse now. The main stream does not stop recording at all or only after the set maximum section length. The "Record on Motion" Monitor is displayed as "idle" after an event, but the recording continues to run unnoticed in the background until the set maximum ...

Hello, I noticed with ZM 1.37.48 that a sub-stream monitor with Analysis Always and without recording, the alarm status is no longer completely ended. Even after the event, the sub-stream monitor remains in alarm status but with a yellow border and yellow writing in the Montage. The connected main ...

Hello, With ZM 1.37.47 I observed that an event recorded by the sub-stream and which is 16 seconds long is split into two events on the linked main stream monitor. The pre-event buffer and post-event buffer settings for both streams are set identically to 60 frames. The camera is set to Main and Sub ...

Hello, I have the problem with Zoneminder that events are only recorded in the 9 to 10 second range and are canceled in the middle of the movement. In the buffer settings I had already set the pre-event and post-event buffers to 5 seconds but that didn't help either. Currently only one camera works ...

In any case, grep "^%Cpu(s)" is not correct for Debian, because in Debian it says %CPU(s). I changed this in zmstats.pl as a test, but the message continues to come every minute. Hello, The fact is that grep “^%Cpu(s)” is the cause of the problem. It just didn't work for me right away because Zon ...

Hello, From what I have found so far, there must be problems for me somewhere in this area of zmstats.pl. # Get CPU utilization percentages my $top_output = `top -b -n 1 | grep "^%Cpu(s)" | awk '{print \$2, \$4}'`; my ($user_utilization, $system_utilization) = split(/ /, $top_output); $user ...

Hello, I have Zoneminder installed on a Debian 12 VM under Proxmox. This is the maximum information I can get with Debug Level 9. 20.12.2023 10:03:08.661514 zmstats[1241].DB1 [ZoneMinder::Logger:321] [LogOpts: level=DB9/DB1, screen=OFF, database=WAR, logfile=DB1->/var/log/zm/zmstats.log, syslog=WAR ...