Status:Alarm Event Duration continuous

[Joe_Calabrese]

I am currently running ZM v1.22.3 with Ubuntu 8.04.3 and I understand that these are not current versions. With that being said, I have VERY limited knowledge on how to navigate/configure/debug issues that I have.

A guy i used to work with set this up for me about three years ago and no longer works with me and apparently hates me.

I have my cameras set to MODECT and but i keep getting continuous alarms, and the event durations that last for 600 thousand seconds, sometimes 180 seconds, and sometimes 13 seconds etc.. Previously, when my system was first set up, my cameras would detect motion for like 13 second intervals or 6 seconds, or whatever. I have tried to configure the "ZONES" to reduce sensitivity and it hasn't worked worked. I am just wondering if anyone has some tips that could help get my ALARM status under control.

If anyone has ideas to help me, you might have to put it in the most simplified response so maybe a caveman could do it...(I hate Geico commercials)
My apologies

Below is what my Event Log looks like, if this helps describe my useless thread..

Id Name Time Sec Frames Score
239827 Event-239827 12/22 11:08:33 4.87 15/5 45/50
239825 Event-239825 12/22 11:02:03 256.78 830/820 50/150
239823 Event-239823 12/22 11:02:02 0.00 11/1 100/100
239800 Event-239800 12/22 08:28:30 188.92 603/593 50/58
239796 Event-239796 12/22 08:18:30 300.70 938/927 50/77
239780 Event-239780 12/22 06:53:20 6885061.33 7140/7126 50/150
239777 Event-239777 12/22 06:52:16 60.37 11/1 100/100
239754 Event-239754 12/22 04:11:45 6894756.71 15065/15047 50/150
239752 Event-239752 12/22 04:11:44 0.00 11/1 100/100
239666 Event-239666 12/21 21:01:34 5399.77 17293/17275 50/150

[Alan87i]

If you can install phpmyadmin on the system .
Login with that local or from another pc and run a repair database on all the ZM databases

There are some terminal commands for this as well ( they escape me at the moment. )

Another way that has worked for me in the past is delete all the events/ then the monitors reboot and create new monitors use a slightly different name. Even if you use a few Upper case letters with the same name it's still different.

[Joe_Calabrese]

OK, I noticed something in the "Event" statistics under (Cause) that shows, (Signal,Linked) where the old events (when my ZM worked correctly) that showed "Motion" under cause... Does this provide any information that could help my cause?

Joe

[Alan87i]

Ya if you have the same 2 cameras "linked " they will both record all the time.
Linking 1 camera too another one will make it record when the other camera records.
Remove all the links and reboot it.

[Joe_Calabrese]

Ok, how exactly do I remove the links to make the recording stop for all the cameras.. Also, I noticed at the boot sequence, that the kernel.shmmax has a status of (FAIL) could this be related to the problem? Thanks again, I appreciate your help.

Merry Christmas!

Joe

[bb99]

To unlink monitors try: control, left click. To check shared memory value run: ipcs -l

Shared memory has caused all types of problems but this would be a first (causing continuous record); more likely the linked monitors.

[Joe_Calabrese]

Ok, i have successfully "unlinked" the monitors. Now, i am having trouble with MODECT. I walk around in front of my cameras and still no recording... I have also tried every possible configuration under the ZONES option and still nothing? Any ideas for a clueless wonder..?

[Joe_Calabrese]

Ok. I think I have figured out the issues with the MODECT including all other issues with recording... Basically for EACH camera (I have 3 total), I went into "Zones", clicked "ALL". Under "Parameter/Preset", I needed to "Choose a Preset" because my values were all messed up. For my particular situation, I chose "Best, High Sensitivity for a preset Value. I guess it was easier than I thought.

Thanks for all the help folks.

Happy New Year.

Joe