zoneminder buffer overrun(s)

[curtishall]

I couldn't connect to zm this morning, I found this in the logs:

I'm not sure why this is happening, but it's not the first time. I have my
max_fps set to 15


Oct 16 12:42:40 lizard zmc-d0[11557]: WAR [Buffer overrun at index 84 ]
Oct 16 12:42:40 lizard zma-m6[20563]: WAR [Approaching buffer overrun,
consider increasing ring buffer size]
Oct 16 12:42:42 lizard zma-m6[20563]: INF [IRCamera: 10477000 - Processing
at 200.00 fps]
Oct 16 12:42:42 lizard zmc-d0[11557]: WAR [Buffer overrun at index 11 ]
Oct 16 12:42:42 lizard zma-m6[20563]: WAR [Approaching buffer overrun,
consider increasing ring buffer size]
Oct 16 12:42:44 lizard zma-m6[20563]: WAR [Approaching buffer overrun,
consider increasing ring buffer size]
Oct 16 12:42:44 lizard zmc-d0[11557]: WAR [Buffer overrun at index 39 ]
Oct 16 12:42:44 lizard zma-m6[20563]: WAR [Approaching buffer overrun,
consider increasing ring buffer size]
Oct 16 12:42:44 lizard zmc-d0[11557]: WAR [Buffer overrun at index 41 ]
Oct 16 12:42:44 lizard zma-m6[20563]: WAR [Approaching buffer overrun,
consider increasing ring buffer size]
Oct 16 12:42:46 lizard zmc-d0[11557]: WAR [Buffer overrun at index 64 ]
Oct 16 12:42:46 lizard zma-m6[20563]: WAR [Approaching buffer overrun,
consider increasing ring buffer size]
Oct 16 12:42:47 lizard zma-m6[20563]: INF [IRCamera: 10478000 - Processing
at 200.00 fps]
Oct 16 12:42:48 lizard zmc-d0[11557]: INF [IRCamera: 775000 - Capturing at
14.71 fps]
Oct 16 12:42:50 lizard zmc-d0[11557]: WAR [Buffer overrun at index 29 ]
Oct 16 12:42:50 lizard zma-m6[20563]: WAR [Approaching buffer overrun,
consider increasing ring buffer size]
Oct 16 12:42:52 lizard zma-m6[20563]: INF [IRCamera: 10479000 - Processing
at 200.00 fps]


I couldn't stop [restart] zm, so i had to restart the server...

and I did doublecheck, it's capturing (max) at 15fps

[zoneminder]

This error is usally caused when the capturing daemon gets frame so fast that it ends up going all the way around the ring buffer and catching up the analysis daemon. It is also however sometimes caused by a slightly unusual startup sequence, though then it tends to always be the same index being reported.

What size of ring buffer do you have and do you have any unusual zone settings that might take it longer to process than normal (eg. overlapping zones on a large image etc?)

Phil,

[curtishall]

Phil,

As always, thanks for the reply.

I believe the ring buffer is also known as the Image Buffer Size (frames) which is set to: 150
Warmup Frames: 25
Pre Event Image Buffer: 20
Post Event Image Buffer: 40
Alarm Frame Count: 1

A system restart fixed the problem, I couldn't get zmpkg.pl to stop [restart]