ZoneMinder Forums

Nice work!

So what was this "snafu?" No hyphens allowed in protocol names?

As a sanity check, I set up my Axis P1347 for PTZ in ZoneMinder and it works fine. Something creates the zmcontrol-9.sock file in the sockets directory and it all just works. The main difference is that the Axis control script comes as part of the ZoneMinder distribution whereas the DCS-5010 script ...

I'm having the same problem with a DLink camera (see thread here: http://www.zoneminder.com/forums/viewtopic.php?f=29&t=21387 ). My Perl-Fu is very weak, but AFAICT the zmcontrol.pl script is attempting to open a Unix domain socket that doesn't exist - whatever ZoneMinder process is supposed to ...

I've determined through perl debugging that the error is coming from line 139 in zmcontrol.pl. If I look at the contents of $saddr, I get '#002'. I don't really know what I'm doing in perl, so that's where I'm at. ideas? 137 socket( CLIENT, PF_UNIX, SOCK_STREAM, 0 ) or die( "Can't open socket:...

I can confirm that this exact same problem exists in ZM 1.25.0 running on Fedora 18 x86_64. I am running from precompiled binaries installed via yum.

After much futzing around, I have ZM up and running on Fedora 18 64. I have 6 IP cameras, 5 of which worked fine right out of the box, but the last one had symptoms similar to those described in the original post. The ZM package in the Fedora Yum repository seems to be using MMAP files, and if you c...

Yup, that did the trick - triggers are now working again.

xlib_shm relies on a specific shared memory layout, of which i changed and might change again in the future if new features are added. Is it possible that these changes to the shared memory layout are the reason that zmtrigger.pl no longer works? http://www.freesmileys.org/smileys/smiley-fc/popcorn...

I upgraded from 1.24.3 to 1.25.0 this morning. Everything seems to be working except the external triggers. If I run zmtrigger.pl manually from the command line, it spits out a bunch of error messages to stdout: Use of uninitialized value $data in pack at /usr/local/share/perl5/ZoneMinder/Memory.pm ...

It's definitely a camera firmware issue. Other brands of cameras also have this bug (or perhaps the Foscam units with this bug are OEM'd by Arecont Vision?) My solution was basically the same as mentioned above: add an if statement to the libjpeg code to suppress the error message. http://www.zonemi...

I, too, have an Arecont Vision IP camera that exhibits the same problem. It appears there is a bug in the Arecont MJPEG encoder that puts some extra junk into each frame right before the end-of-image marker. libjpeg complains about this, and zmc dutifully relays the error message from libjpeg to the...

I upgraded my system tonight using the tarball linked in the first post to this thread. For the most part it went smoothly; however, there were a few unsettling messages spit out by zmupdate.pl during the database update process: Upgrading database to version 1.24.3 Loading config from DB No option ...

I am doing a preview release as it has been so long since the last proper release I want to make sure that there are no major issues with it so please only download and install if you are feeling brave. OK, I'm feeling kinda brave. :) Any tips for those who might want to upgrade from 1.24.2 to the ...

I realize this is an ancient thread, but I ran into a similar problem with one of my IP cameras and I wanted to add some additional data which might benefit future explorers. Every once in a while ZM would record a small burst of events with this bogus timestamp (1969/12/31 16:00) and ridiculous val...

How about using a PIR floodlight? They also have the advantage that they might make someone think twice before doing anything dubious. Do you think I will be able to get an accurate motion signature from the floodlights even during daytime? FWIW, I have a PIR motion detector floodlight that is tied...