ZoneMinder Forums

I've got an office with a lot of different cameras Axis (207, 207W, 210, 2100...)( a total of six).
I access at of all them by different ports (16010, 16020, 16030...)
I've installed ZM on Ubuntu 6.06 and all work ok with a excellent ratio of fps.
I haven't got a problem with ZM on the logs, but my problem is after 8-12 hours of ZM is up.
The image of some cameras is black or the signal is lost.
On the logs I can see:

==> /tmp/zmdc.log <==
09/20/06 20:10:50.546563 zmdc[4977].ERR ['zmc -m 8' exited abnormally, exit status 255]
09/20/06 20:10:56.450911 zmdc[4977].ERR ['zmc -m 3' exited abnormally, exit status 255]
09/20/06 20:10:59.577224 zmdc[6046].INF ['zmc -m 3' started at 06/09/20 20:10:59]
09/20/06 20:10:59.578443 zmdc[4977].INF ['zmc -m 3' starting at 06/09/20 20:10:59, pid = 6046]
09/20/06 20:10:59.737496 zmdc[6050].INF ['zmc -m 8' started at 06/09/20 20:10:59]
09/20/06 20:10:59.742193 zmdc[4977].INF ['zmc -m 8' starting at 06/09/20 20:10:59, pid = 6050]
09/20/06 20:10:59.831132 zmdc[4977].ERR ['zmc -m 5' exited abnormally, exit status 255]

==> /tmp/zmwatch.log <==
09/20/06 20:10:59.435220 zmwatch[5087].INF [Restarting capture daemon for Axis-207W, time since last capture 7 seconds (1158775859-1158775852)]
09/20/06 20:10:59.586165 zmwatch[5087].INF ['zmc -m 3' started at 06/09/20 20:10:59] at /usr/local/bin/zmwatch.pl line 118
09/20/06 20:10:59.587798 zmwatch[5087].INF [Restarting capture daemon for Axis-207, time since last capture 15 seconds (1158775859-1158775844)]
09/20/06 20:10:59.751438 zmwatch[5087].INF ['zmc -m 8' started at 06/09/20 20:10:59] at /usr/local/bin/zmwatch.pl line 118

==> /var/log/messages <==
Sep 20 20:10:59 localhost zmwatch[5087]: INF [Restarting capture daemon for Axis-207W, time since last capture 7 seconds (1158775859-1158775852)]
Sep 20 20:10:59 localhost zmdc[6046]: INF ['zmc -m 3' started at 06/09/20 20:10:59]
Sep 20 20:10:59 localhost zmdc[4977]: INF ['zmc -m 3' starting at 06/09/20 20:10:59, pid = 6046]
Sep 20 20:10:59 localhost zmc_m3[6046]: INF [Debug Level = 0, Debug Log = <none>]
Sep 20 20:10:59 localhost zmwatch[5087]: INF ['zmc -m 3' started at 06/09/20 20:10:59]
Sep 20 20:10:59 localhost zmwatch[5087]: INF [Restarting capture daemon for Axis-207, time since last capture 15 seconds (1158775859-1158775844)]
Sep 20 20:10:59 localhost zmc_m3[6046]: INF [Starting Capture]
Sep 20 20:10:59 localhost zmdc[6050]: INF ['zmc -m 8' started at 06/09/20 20:10:59]
Sep 20 20:10:59 localhost zmc_m8[6050]: INF [Debug Level = 0, Debug Log = <none>]
Sep 20 20:10:59 localhost zmdc[4977]: INF ['zmc -m 8' starting at 06/09/20 20:10:59, pid = 6050]
Sep 20 20:10:59 localhost zmwatch[5087]: INF ['zmc -m 8' started at 06/09/20 20:10:59]
Sep 20 20:10:59 localhost zmc_m8[6050]: INF [Starting Capture]


For extra details:
- The Axis cameras have all the upgrade firmware at the last version.
- The O.S. version is Ubuntu 6.06
- I checked the mysql database and it haven't any problem
- On /etc/sysctl.conf I added the lines: kernel.shmall = 134217728 kernel.shmmax = 134217728
- The log hasn't any mistakes in the permissions. the command "ipcs -m" shows me:

---- Segmentos memoria compartida ----
key shmid propietario perms bytes nattch estado
0x00000000 32768 gdm 600 393216 2 dest
0x7a6d2001 65537 www-data 700 9216964 4
0x7a6d2003 98306 www-data 700 9216964 3
0x7a6d2004 131075 www-data 700 9216964 3
0x7a6d2005 163844 www-data 700 9216964 3
0x7a6d2006 196613 www-data 700 9216964 3
0x7a6d2008 229382 www-data 700 9216964 3

Thank you for helping to me.

Hi

I have seen the
... problem in my setup mostly when using a wireless camera (black images and stuff). I fixed that by boosting up the signal which in my case was getting the WAP nearer to the camera.

This problem too shows up on the recordings using modetect and a wireless cam with bad signal, where zm gets all fouled up and produces events one after the other many happening upon the same minute all composed of the same event repeated several times with only some new frames added. My guess here is that the event starts and in the middle of it signal is lost, the daemon restarts, the event closes and reopens, captures a little more, signal gets lost, and cycles, shooting a whole bunch of problems. Anyway this gets resolved with a good signal between the wap and the cam.

Upon the "abnormal exit status 255" and then restarting... I have seen this too, mostly now on 1.22.2 and on wired cams but have not found luck (and time) to seek the culprit here :-S. I have not found the time either to see if the cams that do show this "abnormal exit" foul up in any way the recordings, perhaps someone has?

My setup was using the most excellent Ross Melin´s Livecd 1.21.4 RPMed to 1.22.2, so I guess Ubuntu has nothing to do with the problem.

Regards

The messages indicate that ZM is unable to get images from the cameras for quite long periods. While you can increase the timeout, it is probably better to get to the problem causing it. Do you still have the same issues if you only use one camera at a time or does it always affect the same cameras in the same way?

In the same ip there are 3 cameras for 3 different ports 16010 16020 and 16030 and other cameras for other different ip. When they begin the mistakes they trump the cameras that have the same ip (1-16010 2-16020 3-16030) others cameras work OK always.

How I can increase the timeout?

Thanks ZM world xD
Sorry for the poor language

It is ZM_HTTP_TIMEOUT in Options->Network but several seconds is an awfully long time to wait for images to come back from a cam.

Ahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh!!!!!

All work ok!!!!
Thanks

Muchisimas Gracias un saludo

GeN:

What did you do to fix the problem? Did increasing the timeout period do it for you, or something else...?

GeN wrote:In the same ip there are 3 cameras

multiple devices with the same ip? on the same LAN?

Yes it's most likely a video server like this one:
http://www.axis.com/techsup/cam_servers ... /index.htm

Regards,
Corey