I noticed that certain combinations of settings will cause the system to crash with segmentation faults, or one camera would work, but not the other, etc, so I thought I would share my findings so far.
On a fresh install, I was able to get the system recording, but when I started customizing zones and other general settings in the system, the system would start to fail for various unknown reasons, and it would eventually never record again. I would have to re-load the blank database and start over and it would work fine again for a while.
One thing I noticed that causes the segmentation faults is if you set the motion detection settings to "too sensitive". Basically, I figured that if I started with very low thresholds that I could get the system to trigger, and then start adjusting numbers until I get a stable setup for motion recording. I used the following:
Type: Active
Units: Pixels
Alarm Check Method: Blobs
Min/Max Pixel Threshold (0-255): 15, (blank)
Filter Width/Height (pixels): 3, 3
Min/Max Alarmed Area: 50, 0
Min/Max Filtered Area: 40, 0
Min/Max Blob Area: 30, 0
Min/Max Blobs: 1, (blank)
Overload Frame Ignore Count: 0
With this kind of setup, it should record if someone's moving a mile down the street, but instead, nothing happens (would never record), and I occasionally saw segmentation faults.
Now, I have bumped up the numbers and actually have it recording on a very sensitive level which is what I wanted.
Type: Active
Units: Pixels
Alarm Check Method: Blobs
Min/Max Pixel Threshold (0-255): 15, (blank)
Filter Width/Height (pixels): 3, 3
Min/Max Alarmed Area: 2000, 0
Min/Max Filtered Area: 1800, 0
Min/Max Blob Area: 1600, 0
Min/Max Blobs: 1, (blank)
Overload Frame Ignore Count: 0
At one point with these settings, I started getting this error: [Buffer overrun at index 16, slow down capture, speed up analysis or increase ring buffer size]. Cam1 would record while Cam2 shut down and did nothing with the same settings. So, I reloaded and did the same settings again but with simplified zones (just the whole screen instead of selecting specific areas), and I've actually had the system running stable for a full day now, so I'm going to tweak some more tomorrow.
My current setup is a PICO2000 card with 2 cameras running at 640x480. Cam1 zones = 1 Active (90% of screen), and 1 Inclusive (10% of screen). Cam2 = Active (100% of screen).
Segmentation faults with motion setings being too sensitive.
Just to add a little more. As soon as I moved the full-page zone definition to a smaller zone, and made it a 5-point box, this is when I start receiving the errors:
Jan 9 08:33:34 rugger zma_m2[12570]: ERR [Got signal (Segmentation fault), crashing]
Jan 9 08:33:34 rugger zmdc[12376]: ERR ['zma -m 2' exited abnormally, exit status 11]
Jan 9 08:33:42 rugger zmc_dvideo1[12399]: WAR [Buffer overrun at index 16, slow down capture, speed up analysis or increase ring buffer size]
Jan 9 08:33:50 rugger zmc_dvideo1[12399]: WAR [Buffer overrun at index 16, slow down capture, speed up analysis or increase ring buffer size]
I deleted one point so it's a regular 4-point box, but the exact same size, and it's back up and running without a problem. Very weird.
Jan 9 08:33:34 rugger zma_m2[12570]: ERR [Got signal (Segmentation fault), crashing]
Jan 9 08:33:34 rugger zmdc[12376]: ERR ['zma -m 2' exited abnormally, exit status 11]
Jan 9 08:33:42 rugger zmc_dvideo1[12399]: WAR [Buffer overrun at index 16, slow down capture, speed up analysis or increase ring buffer size]
Jan 9 08:33:50 rugger zmc_dvideo1[12399]: WAR [Buffer overrun at index 16, slow down capture, speed up analysis or increase ring buffer size]
I deleted one point so it's a regular 4-point box, but the exact same size, and it's back up and running without a problem. Very weird.