Page 1 of 1

Solved. Alarm recording stopped

Posted: Tue Jun 16, 2009 9:12 am
by ludri
My setup was working fine until yesterday it does not store any alarm events.

My setup:
Ubuntu 8.10, ZM 1.24.1
P4 2.6, 882MB ram, kodicom 4400r running with 1 camera.

Camera is running at 384x288 10fps and 20fps alarm. PAL, video for linux 2, bgr24. modect.
Image Buffer Size 40, Warmup 10, Pre 20, Post 20

When I force alarm I can see in /var/log/messages:

Code: Select all

Jun 16 12:10:47 dvr zma_m2[7911]: INF [Monitor-2: 227 - Gone into alarm state]
Jun 16 12:10:47 dvr zma_m2[7911]: INF [Got signal 6 (Aborted), exiting and forcing backtrace]
Jun 16 12:10:47 dvr zma_m2[7911]: INF [Backtrace complete, please execute the following command for more information]
Jun 16 12:10:47 dvr zma_m2[7911]: INF [addr2line -e /usr/local/bin/zma 0xb8007424 0xb8007424 0xb72478a0 0xb7249268 0x8055abd 0x805c189 0x8070ac2 0x804cee2 0xb7232685 0x804cb81]
Jun 16 12:10:49 dvr zmc_dvideo1[5372]: WAR [Buffer overrun at index 39, image 3319, slow down capture, speed up analysis or increase ring buffer size]
Jun 16 12:10:51 dvr zmc_dvideo1[5372]: WAR [Buffer overrun at index 39, image 3359, slow down capture, speed up analysis or increase ring buffer size]
Jun 16 12:10:51 dvr zmc_dvideo1[5372]: WAR [Last image read from shared memory 4 seconds ago, zma may have gone away]
Jun 16 12:10:55 dvr zmwatch[5383]: INF [Restarting analysis daemon for Monitor-2, time since last analysis 8 seconds (1245143455-1245143447)] 
Jun 16 12:10:55 dvr zmdc[5350]: INF ['zma -m 2' starting at 09/06/16 12:10:55, pid = 8054] 
Jun 16 12:10:55 dvr zmdc[8054]: INF ['zma -m 2' started at 09/06/16 12:10:55] 
Jun 16 12:10:55 dvr zmwatch[5383]: INF ['zma -m 2' starting at 09/06/16 12:10:55, pid = 8054] 
Jun 16 12:10:55 dvr zma_m2[8054]: INF [Debug Level = 0, Debug Log = <none>]
Jun 16 12:10:55 dvr zma_m2[8054]: INF [In mode 3/1, warming up]
In /etc/sysctl.conf I have:
kernel.shmall = 225792
kernel.shmmax = 462422016


I tried change shared memory, Image Buffer Size, Warmup, Pre, Post settings. But I did not get alarm recording back.

Generates only these:
Id Name Time Secs Frames Score
34317 New Event 2009-06-16 12:03:28 0.00 null/null 0/0 X

Posted: Sun Jun 21, 2009 12:50 pm
by ludri
Update:
Seems it didn't like 384x288. Runs fine on 320x240.
But weird it worked fine before at 384x288 res.

Posted: Sun Jun 21, 2009 5:14 pm
by robi
ludri wrote:Update:
Seems it didn't like 384x288. Runs fine on 320x240.
But weird it worked fine before at 384x288 res.
I've been using it at 384x288 for 2.5 years, without a problem...

Posted: Mon Jun 22, 2009 3:05 pm
by ludri
Today it stopped recording at 320x240.
I created new Monitor with exact settings (same input etc.), disabled the problematic monitor.
Records fine.

I'll do clean install someday with mapped memory setting.

Is it possible to migrate events to clean install?

Solved

Posted: Mon Oct 05, 2009 2:19 pm
by ludri
Problem cause was the ext3 32000 limit:
http://www.zoneminder.com/wiki/index.ph ... monitor.3F

And the ZM_USE_DEEP_STORAGE was not set.

I solved this by upgrading ext3 to ext4 like so: http://blog.ejbca.org/2009/04/migrating ... ypted.html