ZoneMinder Forums

I double checked and it is "time"! That is not a bug I suspected and said on my first post, since on a fresh debian installation, I do not have the problem. So I looked for a suggestion to look somewhere in my system, but I do not know where! Is there some system call, somewhere in ZM code that ...

Testing conditions: 1 cam active Record mode Event length = 600 Debug active All Debug data go only into zm_debug.log Debug level 9 cat zm_debug.log |grep Closing 12/12/18 22:56:48.515045 zma_m1[17920].INF-zm_monitor.cpp/1460 [CAM00: 9603 - Closing event 1464929, section end forced ] 12/12/18 22:57 ...

Hi, I thing it is not depending to zoneminder bug, but something broken in my system! I am using mocord mode and debian buster updated. Even if I change the section length from 600 to 6000, or some different numbers, every event lasts 60 seconds! Sometime 120 seconds. Rolling back to 1.30.4 does not ...

Solved...

I created a new empty db from 1.30.4, and I restored on it a backup of the db updated by 1.32.
In zm database, in "Monitors" table I changed the Field name "AnalysisFPSLimit" to "AnalysisFPS".
Now version 1.30.4 looks to be working again.

Hi, new 1.32 has better web interface and some interesting new features, but CPU load went up from 1.2 to 2.6 and it is not really stable. I have lots of archived events and I tried to restore the 1.32 database into new created db with zm 1.30.4, but zoneminder crashes when start capturing ...

I think pre-event buffer in mocord mode is a non-sense, because in you are recording all the frames. If bulk frame would work correctly, you can browse all the frames starting from the alarmed frame going "Prev" and "Next". Even if all the images are into the filesystem, at this moment, you can ...

It looks similar to my posts here about missing frames in bulk frames in mocord mode:
viewtopic.php?f=36&t=25510&p=97509#p97509

There also an issue opened here:
https://github.com/ZoneMinder/zoneminder/issues/1698

.... but nobody looks to be interested!

Mocord is continuos recording + motion detection.

For this camera I used the following settings: Source type = Ffmpeg Source Path = rtsp://$camera_ipaddress/axis-media/media.amp?resolution=$Widthx$Height Remote Method = TCP Target colorspace=32bit color Capture Width = $Width Capture Height= $Height $Width and $Height are the resolution parameter ...

I setup 12 ipcam in ZM_1.30.4 on a debian9 vm into esxi6.5. VM dedicated RAM is 8GB. CPU is Xeon E3 1246V3. Disk controller is LSI megaraid 9271-8i 1GB cache. DB is MariaDB, with some changes in cnf file as well as suggested by mysqltuner. 10 cameras are running at 1280x720 @ 25fps and 2 are running ...

Am I the only one looking the events frame by frame? I just tried to compile master branch, and still not working, no possible to view frame number 99 or 101, or 199 and 201 and so on... I would like to update to 1.30, but I cannot do. Is there any plan to fix this issue? The issue is not present in ...

I had a similar issue. In alarm I lost lot of frames. I have now 6 cameras in mocord mode, 5 of them are set 1280x720p@25fps and 1 is 1280x960@20fps. CPU is Xeon E3-1246, and load does not go over 3.00 if all cameras go in alarm. So less power compared to your, and I do not loose any frame even in ...

Hi knnniggett,
thanks for your help, built from git 1.30.0 in debian stretch and outline is now OK.
There is something else not working in 1.30.0 (please see issues in github) and message on this forum: viewtopic.php?f=36&t=25510

Thanks again for your help.

Hi, I am using 1.29.0 and everything is OK. I would like to update to 1.30.0 but I found an issue in new 1.30.0. I am using a Debian Stretch just installed in a virtual machine and a couple of ipcam using Mocord method. In the event list, click on the "Frames" column you can see the frames list ...

Same problem for me! Latest 1.30.0 on fresh installed debian testing. I have a fully working 1.29.0, so I know how to configure the zones. I can find the error into the apache2 error log file each time I click on the "Max Score" column in the event list: [Wed Nov 23 15:30:36.903547 2016] [:error ...