ZoneMinder Forums

I had similar symptoms with two wireless network cameras that seemed to randomly go offline and then back online all by themselves. Some days it would only happen once, while other days it would happen several times. Even though the warning message in your post points to shared memory, I think that ...

From the photo it looks like you've got a wired analog camera (not a DSC-910, nor a wireless camera) with a typical power plug and bnc for video. Looking at the antennas, particularly the plugs, it looks like those antennas are intended for wireless Ethernet, which is a different (i.e. incompatible)...

So I recently took the plunge and recompiled my instance of zoneminder to use mapped memory rather than shared memory. It works great. That got me thinking.... since /dev/shm is bascially a dynamic ram disk, why not use it for zm's temporary files as well as zm's mapped memory files? To test this, I...

I noticed that the author of the CentOS guide appears to have configured ffmpeg w/o enabling any options. Do a make clean and then reconfigure ffmpeg with the following: ./configure \ --enable-gpl \ --enable-swscale \ --enable-shared \ --enable-pthreads This is what worked on my system although I fo...

You've got an ffmpeg problem. I'm assuming you complied ffmpeg from source? Look at your output prior to the error... do you see any complaints about missing header files? The trouble with ffmpeg is that the authors constantly change things around, and trying to stay on top of the changes is a chall...

At this point I'm out of good ideas. Based on the camera connection parameters you provided, I'm assuming you have authentication turned off on the camera. You may also want to turn off (at least temporarily) your firewall and disable selinux just to make sure they aren't interfering. Yeah, I know.....

I'm wondering if the issue is not shared memory per say, but rather an inability to get an image from the camera. I noticed that zmupdate was not able to contact www.zoneminder.com could simply be an unrelated dns problem, but just in case let me ask the obvious... can you successfully open a web br...

I doubt that value will work at all since it almost certainly exceeds the amount of physical memory you have in the machine. Try the value I mentioned previously. If you are setting this via your sysctl.conf then remember you will need to reboot for the new setting to take effect. Admittedly, the va...

I just took a second look at the the output you posted. You've identified kernel.shmall (and that looks ok), but what is kernel.shmmax set to? One usually has to increase the shmmax on a default system to avoid shared memory errors. I've got mine set to 268435456 (256MB). This number will vary, depe...

Are you using a local capture card? If so, check your permissions on /dev/videoX where "X" is the number of the video device that points to your capture card. Either chmod /dev/videoX or I think zmfix can fix it for you (search the forums for proper syntax). If this does not resolve the is...

I'm thinking you need to specify the "--with-libarch=lib64" configure parameter (libmysqlclient.a can be found under /usr/lib64 not /usr/lib on 64bit systems). If you want to use a known good set of parameters, just copy and paste these: ./configure \ --with-webdir=/var/www/html \ --with-c...

Technically no, it didn't, but it's interesting you mention that because something along the lines of corrupted events is the reason why I started looking under the hood so the speak in first place. While the SQL mods previously posted didn't fix the random corrupted event issue I was trying to solv...

There are two layers of permissions we are dealing with here: file permissions and samba permissions. The way your system is configured, Zoneminder records directly to /media/disk/cctv. It doesn't use samba to do this. Consequently, you can set your Samba permissions to anything you want, and it wil...

If you feel you must share your zm events folder, I recommend setting the read only flag on your cctv samba share just to prevent any accidental deletions or modifications.

I've skimmed through Phil's command history a few times and here is my take on what was done: - gather info about your video device with v4l-info - Turn up zm debug - Check that the Ubuntu deb package you used put everything in the right places with the right permissions - Check zm log, apache log, ...