ZoneMinder Forums

5 is the recommended rate; I can't imagine that's too fast for 2 cameras.

What happens if you have 2 cameras on one chip, and nothing on the other 3?

I'm using about 60MB of swap atop 6GB of physical RAM; free says 1.8GB or so available. And the other machine, alas, is having disk controller problems, and I haven't been able to get it to boot. That said, I would expect *less* trouble with the 32-bit install, since the binaries are half the size. ...

Here's a month's worth of tuning on this machine, which is still 12 720p Cams at 6fps modect; I upgraded the ffmpeg to: ffmpeg version 3.3.4-2~16.04.york0 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.4) 20160609 configuration: --prefix=/usr --extra-...

Ah, capture cards. I remember capture cards.

Could your frame rate be too high? It takes a finite amount of time for the video switch in front of the A/D converter to settle. You generally need an entire frame for each switch.

What frame rate are you recording at?

Check the filesystem permissions all the way along the path to

/usr/lib/zoneminder/cgi-bin/nph-zms

and make sure *the webserver owner user* has permission to search to there and execute. It sounds like your filesystem permissions have gotten ganked somewhere.

Jannnfe: "/zoneminder/" is an unusual thing to see in that pathname; it's customarily /zm/.

Did you pick /zoneminder/ in your install on purpose?

bbunge: this comes up *a lot*: do we have a poorly chosen default somewhere?

Optical focus?

No, I believe you'll have to do that with external code.

It's actually on every page, I see.

Kniggettt: who are we supposed to poke about such things?

Not quite. 'Client denied by server config' is the important sentence there, and it means that your Apache configuration is messed up somehow.

Look in either

/var/log/apache/error_log or /var/log/httpd/error_log

whichever you have, and see what error is showing up when you call nph-zms.

That should be a hint what isn't configured correctly -- which is usually what this is.

I do agree with your diagnosis -- and of course, it *really* means that the firmware in the camera isn't rugged enough... hey. Have you checked to see if there's new firmware for the cameras?

Find the error_log file for Apache -- usually in something like

/var/log/apache or /var/log/httpd

and see what it says when you try to open a camera viewer.

The #1 problem with this is that Apache, ZM's PATHS config, and the filesystem don't all agree on where nph-zms lives.

You're right. I was paying insufficient attention to which objects were having their ownerships set incorrectly.

I would be betting on the Apache service itself. Or perhaps it's called the httpd service in that distribution. Is it deterministic which order those two start in? My comment was mostly a vast and considered distaste for the design of systemd in the first place rather than an actual target to shoot ...