Events not being captured.

[roguelj]

Hi all, am new to the forum, so please be gentle!

I have a strange issue with Zoneminder. I am running Zoneminder V1.24.1 on Debian Lenny on an AMD Athlon(TM) XP 2100+ with 1Gb ram. I am using a single BT878 card (card=77) with 2 cameras attached connected to channels 0 and 1, both set to MoDect.

All appears to be fine - I can see video from both cameras clearly. However, when someone walks in front of the cameras or other movement is apparent (by looking at the feed), no events are captured. Its quite obvious movement too, not just in the corner of the FOV, but right slap bang in the middle, large as life.

I have added a symlink from events to /home/zoneminder/events and images to /home/zoneminder/images (there's more space on that partition). However I'd have thought that if this was the problem, then the events would fire but you would not be able to see the images (I did this before on V1.23.x. I incorrectly set the paths, and it did indeed capture events but you could not see them). So I am a little unsure as to what is going on.

Any help you can give would be appreciated.

[roguelj]

Has anyone got any ideas on this?

[cordel]

Saying that no events are captured is a bit vague and leaves allot to be assumed.

Does the zone go into alarm?
Are any images stored on the drive if you force an alarm?
Have you tuned the zone to suit the field of view?

[sdj72]

I just ran into this and found it was a permissions issue on the events directory. I had mounted a 2nd drive and it was showing Numerical ownership and group so a quick chown and chgrp fixed it for me. To figure it out I turned on additional debugging and set at level 3 and saw the permissions issue in the logs.
I hope this helps.

Shane

[roguelj]

Ah, hi again.
Finally got round to setting ZM up again after a hardware failure. Set everything up as before, and still had the same problem. The zone did not go into alarm, no images were stored, and the zone was not tuned - it was set to the entire image.
The problem was indeed due to a permissions issue - once I had changed this with chmod +777 events (not sure if this the correct way to do this, as far as security is concerned), all now appears to be working. Cheers sdj72.