Some pics are missing

[Centaurus17]

Hi,

I got ZM the first time running *) - it works but there are pictures missing: when there is motion in front of the cam the recording/event starts - but after 6 pictures there are some pics (corresponding approx. 1-2 seconds of time) missing ... after this break the following pictures are OK.

Additional sometimes I have an event with zero pics...

Thanks for a hint to get a continous record.
Centaurus17


*) ZM 1.25, fresh installed Debian Wheezy, motherboard Pure White E350, HDD WD10JUCT, Vivothek-IP-Cam 1280x800

[Centaurus17]

Additional to describe the problem: after exporting the pics from one event (modect) I have:

• 001-capture.jpg to 008-capture.jpg (pre-event-buffer)
• 009-capture.jpg = the pic where the first detection happened (bottom border)
• then some pics are missing
• 010-capture.jpg is quirky damaged
• the following pics are OK in the correct order

Any ideas? Thanks a lot.

Regards

[Centaurus17]

In the meantime I could find following: the problem has something to do with the buffers and the hardware:

• On the Sapphire Pure White E350 with 4GB RAM: if I change the 'warmup buffer' to 0, the 'pre event image count' to 1 and the 'post event image count' to 5 - it seems to work.
• Then I tested the same - clean installation Debian Wheezy, ZM v1.25 - on a more powerful PC: there the standard-settings 'warmup buffer' = 25, 'pre event image count' = 10 and 'post event image count' = 10 does not show the problem 'missing pics'.

Question: what's wrong on the E350, where is the limiting factor? The CPU? The 4 GB RAM? The 2,5" HDD/5400upm? Which buffer-settings are recommended for 4-5 IP-cams 1280x800 on the E350?

Thanks for hints.

[Centaurus17]

Hi,

following problems in the syslog:

Code: Select all

Jan 23 20:04:52 debianserver zma_m3[9835]: INF [Tuere: 146630 - Opening new event 393, alarm start]
Jan 23 20:04:52 debianserver zmc_m3[9826]: WAR [Buffer overrun at index 6, image 149016, slow down capture, speed up analysis or increase ring buffer size]
Jan 23 20:04:52 debianserver zma_m3[9835]: WAR [Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size]
Jan 23 20:04:52 debianserver zmc_m3[9826]: WAR [Buffer overrun at index 7, image 149017, slow down capture, speed up analysis or increase ring buffer size]
Jan 23 20:04:54 debianserver zma_m3[9835]: INF [Tuere: 146642 - Gone into alert state]
Jan 23 20:04:54 debianserver zma_m3[9835]: INF [Tuere: 146652 - Left alarm state (393) - 25(12) images]
Jan 23 20:04:54 debianserver zma_m3[9835]: INF [Tuere: 146652 - Closing event 393, alarm end]
...
...
Jan 23 20:21:44 debianserver zms[13666]: ERR [Got unexpected memory map file size 122881524, expected 46081124]
Jan 23 20:21:49 debianserver zms[13669]: ERR [Got unexpected memory map file size 122881524, expected 46081124]
Jan 23 20:21:53 debianserver web_php[9852]: ERR [Timed out waiting for msg]
Jan 23 20:21:58 debianserver zms[13731]: ERR [Got unexpected memory map file size 122881524, expected 46081124]
Jan 23 20:22:06 debianserver zms[13738]: ERR [Got unexpected memory map file size 122881524, expected 46081124]
Jan 23 20:22:08 debianserver zma_m3[9835]: INF [Tuere: 159000 - Processing at 11.90 fps]
Jan 23 20:22:11 debianserver zms[13731]: INF [Got signal 15 (Terminated), exiting]
Jan 23 20:22:11 debianserver zms[13731]: ERR [Unable to send stream frame: Broken pipe]
Jan 23 20:22:21 debianserver zms[13744]: ERR [Got unexpected memory map file size 122881524, expected 46081124]
Jan 23 20:22:27 debianserver zms[13738]: INF [Got signal 15 (Terminated), exiting]
Jan 23 20:22:27 debianserver zms[13738]: ERR [Unable to send stream frame: Broken pipe]

In the /etc/sysctl.conf I have for 1 camera 1280x800pix & ring buffer = 25 (at the moment):

Code: Select all

kernel.shmall = 1342177280
kernel.shmmax = 1342177280

Could anybody give a hint how to fix this problem(?) - I try to solve it since some days...

Thanks and best regards
C.

[Centaurus17]

The most errors in the syslog I could fix. But I do not know why ZM records instead of e.g. 1 (longer) event *) with 15 seconds more short events (and when event-part #2 and #3 is starting - I have errors in the log).

*) I'm walking around in front of the camera for ~ 15 seconds - and instead of 1 (longer) event I have 3 or 4. This cannot have something to do with pre-event- and post-event buffer (I think...).

Any ideas?

----

New test: I walked in front of the camera ... 3 events are recorded (modect): 5.89 + 0.82 + 6.77 seconds (and I'm always moving...) ... why not 1 event with 14 seconds...? An in this event(parts) are missing some pics.

----

syslog (from another event which was splitted in 3 events):

Jan 24 13:31:31 debianserver zmc_m3[881]: INF [Tuere: 28000 - Capturing at 11.90 fps]
Jan 24 13:31:53 debianserver zma_m3[890]: INF [Tuere: 27778 - Gone into alarm state]
Jan 24 13:31:53 debianserver zma_m3[890]: INF [Tuere: 27778 - Opening new event 465, alarm start]
Jan 24 13:32:00 debianserver zma_m3[890]: INF [Tuere: 27830 - Gone into alert state]
Jan 24 13:32:00 debianserver zma_m3[890]: INF [Tuere: 27840 - Left alarm state (465) - 65(52) images]
Jan 24 13:32:00 debianserver zma_m3[890]: INF [Tuere: 27840 - Closing event 465, alarm end]
Jan 24 13:32:02 debianserver zma_m3[890]: INF [Tuere: 27869 - Gone into alarm state]
Jan 24 13:32:02 debianserver zma_m3[890]: INF [Tuere: 27869 - Opening new event 466, alarm start]
Jan 24 13:32:03 debianserver zma_m3[890]: INF [Tuere: 27875 - Gone into alert state]
Jan 24 13:32:04 debianserver zma_m3[890]: INF [Tuere: 27885 - Left alarm state (466) - 19(6) images]
Jan 24 13:32:04 debianserver zma_m3[890]: INF [Tuere: 27885 - Closing event 466, alarm end]
Jan 24 13:32:13 debianserver zma_m3[890]: INF [Tuere: 28000 - Processing at 11.76 fps]
Jan 24 13:32:48 debianserver zmc_m3[881]: INF [Tuere: 29000 - Capturing at 12.99 fps]
Jan 24 13:32:58 debianserver zma_m3[890]: INF [Tuere: 28537 - Gone into alarm state]
Jan 24 13:32:58 debianserver zma_m3[890]: INF [Tuere: 28537 - Opening new event 467, alarm start]
Jan 24 13:33:07 debianserver zma_m3[890]: INF [Tuere: 28612 - Gone into alert state]
Jan 24 13:33:08 debianserver zma_m3[890]: INF [Tuere: 28622 - Left alarm state (467) - 88(75) images]
Jan 24 13:33:08 debianserver zma_m3[890]: INF [Tuere: 28622 - Closing event 467, alarm end]
Jan 24 13:33:39 debianserver zma_m3[890]: INF [Tuere: 29000 - Processing at 11.63 fps]
Jan 24 13:34:08 debianserver zmc_m3[881]: INF [Tuere: 30000 - Capturing at 12.50 fps]

[Centaurus17]

Again:

Jan 24 15:10:47 debianserver zma_m3[6241]: INF [In mode 3/1, warming up]
Jan 24 15:11:07 debianserver zmc_m3[6232]: INF [Got signal 15 (Terminated), exiting]
Jan 24 15:11:07 debianserver zmc_m3[6232]: WAR [Attempt to join non-started thread -1]
Jan 24 15:11:07 debianserver zmc_m3[6232]: WAR [Attempt to join non-started thread -1]
Jan 24 15:11:07 debianserver zmc_m3[6273]: ERR [Got unexpected memory map file size 76801284, expected 61441204]
Jan 24 15:11:08 debianserver zmc_m3[6273]: INF [Starting Capture]
Jan 24 15:11:08 debianserver zma_m3[6241]: INF [Got signal 15 (Terminated), exiting]
Jan 24 15:11:08 debianserver zma_m3[6282]: ERR [Got unexpected memory map file size 76801284, expected 61441204]
Jan 24 15:11:08 debianserver zma_m3[6282]: WAR [Waiting for capture daemon]
Jan 24 15:11:09 debianserver zmc_m3[6273]: WAR [Sequence in probation 2, out of sequence]
Jan 24 15:11:09 debianserver zmc_m3[6273]: WAR [Discarding frame 0]
Jan 24 15:11:09 debianserver zmc_m3[6273]: WAR [Discarding incomplete frame 0, 0 bytes]
Jan 24 15:11:09 debianserver zmc_m3[6273]: ERR [Error while decoding frame 0]
Jan 24 15:11:09 debianserver zmc_m3[6273]: ERR [256: 00 00 01 b6 58 ca 1c 10 .....

... but kernel.shmall & kernel.shmmax ist set much larger (1342177280) ... ???

C.

[Centaurus17]

I'm hanging at the correct settings for kernel.shmall & kernel.shmmax for 1 high res camera with 1280x800/24bit/40buffer on a PC with 4GB RAM (testing system). If this will work I'm planning to increase the RAM to 8GB and set up 4 cameras 1280x800.

With google I found a lot of contradictorily suggestions ... some are setting kernel.shmall = kernel.shmmax (e.g. here), some (e.g. here) are counting the color in the calculation with 3, the Wiki says color x24, kernel.shmmax should be 1/2 of RAM - how big should be kernel.shmall(?) ... confused.

The correct settings (& way of calculation) for both systems - a.) 4GB RAM/1 cam 1280x800 and b.) 8GB RAM/4 cams 1280x800, both on Wheezy - are looked for.

Thx