ZoneMinder Forums

I recently upgraded from 1.28.0 to 1.34.22. The older version had a separate control page for PTZ cameras; when that page was active, I could click within the image area to pan and tilt the camera. Now with the new unified control screen clicking within the image just activates the digital zoom ...

FWIW, I have found that the disk I/O may be more of a bottleneck than the CPU. My server is an i7-3770K (4 cores with hyper-threading); I have 11 IP cameras, most of which are 1920x1080 at up to 15 fps with motion detection active. With all that and an ALPR daemon running my overall CPU utilization ...

Is there some reason why you can't just run your monitor in "nodect" mode and use zmtrigger.pl to trigger alarms?

So I started over again from scratch with a complete re-install of Fedora 20 as well as ZM from the repo. This time I installed only those packages which were absolutely needed in order for ZM to run. Currently everything is working with no seg faults. Last time I installed a few other things onto ...

Actually this is not an upgrade, it's a completely fresh install of the OS and ZM (due to a failed HD). I'm not using ZM's authentication at all, so I guess you can rule that out. I have 11 IP cameras, only one is an Arecont Vision, and none are over 3MP, yet zmu crashes on all of them.

FWIW.

On my fresh install of Fedora 20 + fresh install of ZM 1.28.0 from the ZM repo, when I go to edit a zone, the web UI hangs - any attempt to open a new window results in an empty frame and a "waiting for data" message. Running top from the command line shows a zmu process sucking up 100% of one CPU ...

I had a working 1.26.5 system until last night when my hard drive died. Since I had to reinstall everythnig anyway I decided to upgrade everything to thelatest and greatest. Fresh install of Fedora 20 x64. Installed the ZM 1.28 package from the ZM repo as outlined here . Installed my first monitor ...

I am running 1.26.5 on a Fedora 18 Linux box and have run into an issue. The problem is that sometimes the video stream connection does not terminate properly; if I am viewing a video stream and close the browser window (or click the "Close" link on the page), the underlying TCP connection remains ...

The simplest way is to just delete the functions which have errors. Once those are gone you'll also have to delete the (unused) references to them elsewhere in the file. Another option is to upgrade your machine to a newer distribution and/or newer version of GCC, which might be a better way to go ...

For anyone still following along, I managed to solve the problem through a combination of moving the ext4 filesystem journal to a separate device (removing the journal entirely also works, but is obviously less safe) and using a write queue and a background writer thread. The periodic starvation ...

I have had similar problems when compiling on older distros (e.g. CentOS 5, Fedora 13) - it seems older versions of GCC have problems with the function declaration attributes that are supposed to filter out the SSE stuff on machines that don't support those instructions. On those machines I have to ...

I want to try the fix you listed for FfmpegCamera::PrimeCapture but I cant locate that file. Did you install ZoneMinder from source or from a package using apt-get? If you installed from a package, you may not have the source installed on your machine. In order to make this fix you would need to ...

Experimental results: Adding a background thread to zma to write the frames to disk helped but did not completely solve the problem - there were still occasional buffer overruns. Apparently the analysis thread is blocking on something besides disk I/O (such as I/O to the database socket), or ...

After playing with the Frame Server option for a while, I have the following observations: I found that I need to allocate a lot of buffer space for the Unix domain socket that carries the frames between zma and zmf. Even 16MB of buffer space per process isn't enough to absorb all of the peaks ...

My filesystem is an ext4 consisting of multiple LVM volumes. The ZM events have their own LVM composed of 2 2TB Seagate Barracuda 7200RPM drives. Although I was able to lower the I/O priority of zmaudit.pl to Idle Class using ionice, that didn't solve the problem; it turns out that any other process ...