ZoneMinder Forums

The image buffer is now set at 100 and I still get this error? Any idea how to fix this?


2011-10-16 10:41:08.218613 zmc_m2 21463 WAR Buffer overrun at index 10, image 13210, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 2568
2011-10-16 10:41:06.876148 zms 21821 INF Got signal 15 (Terminated), exiting zm_signal.cpp 44
2011-10-16 10:41:04.945383 zmc_m2 21463 WAR Buffer overrun at index 33, image 13133, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 2568
2011-10-16 10:41:04.175585 zmc_m2 21463 WAR Buffer overrun at index 15, image 13115, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 2568
2011-10-16 10:41:04.124432 zma_m2 21525 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1083
2011-10-16 10:41:04.070147 zmc_m2 21463 WAR Buffer overrun at index 12, image 13112, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 2568
2011-10-16 10:41:03.379416 zma_m2 21584 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1083
2011-10-16 10:41:03.292887 zmc_m2 21463 WAR Buffer overrun at index 94, image 13094, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 2568
2011-10-16 10:41:02.199686 zmc_m2 21463 WAR Buffer overrun at index 68, image 13068, slow down capture, speed up analysis or increase ring buffer size zm_monitor.cpp 2568
2011-10-16 10:41:02.197007 zma_m2 21584 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1083
2011-10-16 10:41:01.932314 zma_m2 21584 WAR Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size zm_monitor.cpp 1083

Try setting FPS to half of its value and lower down the buffer to 75.

I dropped the buffer to 75, but the FPS is at 9......Dropping it in half would take it down to 4?

I got a TON of errors when I did that, same ones.

SO I put it back up and they almost quit completely.

I get a ton of backtrace errors too...

Hi,

Maybe is a good idea to give more details about you system. How many cameras, type of capture card, IPcams or video, etc. This data will help to help.

PacoLM

This is a Quad Core, SunFire system running CentOS 6. 8 Gigs of ramm.

4 Drives, stripped, on a SAS network.

Two IP Cameras, both are AXIS M3014 Network Camera. Their in the same room, pointing at two different angles.

They do both MJPEG and H264...tho I haven't had good luck with rtsp here, I have zoneminder to use motion jpeg.

Both cams are set to have two types of zones. This is for a data center. Cam 1 watches the door, and two cage doors, plus the floor. Cam 2 watches both cage doors, and the floor.

Any other output you need I can give you, any other details as well.

I don't believe there is a capture card......as I would assume this is for a local camera.

I've only had this error when I was testing and having other issues... ZM was busy cleaning up alarms that couldn't record due to a bad symlink issue.

What kind of CPU use are you having? With megapixel cams, I find ZM not very good with Mocord. Motion detection eats up a lot o CPU (although better with turbo-jpg). If you need 9 fps, try the Axis motion detection.

the CPU usage was in the 3's before, but now rides at about .7 on a constant. This is a SunFire box....made by SUN, which are super solid servers. Its a dual proc, quad core machine, so we got alot of processor power. I agree tho, it is a very processor intensive system.

I was going to try the whole axis detection as well.

My main issue right now, is that it all works, and it works fine, but the system starts recording during an alarm and never stops....

Check to see if you have linked monitors or overlapping zones. This causes the continuous recording problem in a high percentage of this complaint. It is also becoming much more common problem linking a monitor to itself causing the same problem. MTK's patch eliminates this according to the change listing.

I too get similar warnings:
On Video 6 for example, my Image Buffer Size is 40, 25 warmup frames, 15 pre-event, 50 post event, 1000 stream replay image buffer, alarm frame count 1.

Max and Alarm Max FPS are 5. There is one zone set to alarmed pixels min/max pixel threshold 20 / 0. Min/max alarmed area 5 / 80. Overload Frame Ignore Count 0 (what is that?).

This issue does not seem to be a major problem, though I do have issues where sometimes a monitor will get 'stuck' recording a single event non-stop for days.

bb99 wrote:Check to see if you have linked monitors or overlapping zones. This causes the continuous recording problem in a high percentage of this complaint. It is also becoming much more common problem linking a monitor to itself causing the same problem. MTK's patch eliminates this according to the change listing.

The two monitors are linked. They are both in the same room, one faces one way, the other faces another but they do overlap. I tried to figure out how to get them to not be linked, but I couldn't figure that part out. If I got one cam, i add the 2nd and it links the two. How can you get them to either unlink or have them not link upon creation?

Also, the patch you mention, where can I obtain this patch at? Will it work for 1.25?

Sorry, MTK = MastertheKnife. Patch and explanation are here: http://www.zoneminder.com/forums/viewto ... =9&t=17652. It does work with 1.25.0 (read the whole post for changes and updates incorporated). If monitors are linked there will be an asterisk next to the monitor linked to. To undo the link hold the control key down and click to unlink. This linking to itself is a new one on me and I can't describe exactly what to look for. For the zones: start with one zone and get it working making only one change at a time so it's easy to undo. I'm not eliminating the possibility of an issue within ZM because of the number of posts with this same problem. Only solved post fixing the continuous recording was fixed by going back to one default zone.

bb99 wrote:Sorry, MTK = MastertheKnife. Patch and explanation are here: http://www.zoneminder.com/forums/viewto ... =9&t=17652. It does work with 1.25.0 (read the whole post for changes and updates incorporated). If monitors are linked there will be an asterisk next to the monitor linked to. To undo the link hold the control key down and click to unlink. This linking to itself is a new one on me and I can't describe exactly what to look for. For the zones: start with one zone and get it working making only one change at a time so it's easy to undo. I'm not eliminating the possibility of an issue within ZM because of the number of posts with this same problem. Only solved post fixing the continuous recording was fixed by going back to one default zone.

Crazy, I am gonna try the MTK patch here in a minute. I just stripped all the cameras out. Rebuilding it, wants to name it Monitor-6....so its keeping the idea of Monitor 1-5 somewhere.

I renamed it, first one added with out any link. The second one added, wants to link the the first. I dont see an Astrix, but I do see the name of the camera in the linked frame. Looking at the first cam, after the second one is added, it now shows in the first one. I don't see an astrix on anything.....

So I am just now gonna add zones to the camera one. Gonna test it. The only thing that sucks is the cams are on the 4th floor and I am on the 1st.

I would love to post screen shots, but I can't post images to the forum....

So only adding zones to the 1st cam, works great!

I haven't attempted to setup zones for the 2nd one yet, but thats the next testing. The funny thing is, the cam doesn't record the first steps of me coming in the room. The door alarm didn't even trigger.

Increase your "Pre Event Image Count" to 2 seconds. @10 fps that would be a value of 20. These frames will be added to the front of the alarm frames giving you the desired result. Setting is just a suggestion for a starting point but keep in mind this is a true buffer and does count against the image buffer.