ZoneMinder Forums

lightguy48 wrote: ↑Sat Nov 11, 2023 9:40 pm Wow, I had never thought of that before, testing it now and it seems like a great solution!

I see in the logs a warning about the dimensions not matching but it doesn't seen to cause any issues...

I did this with my dad's cameras and it's GREAT!

I no longer used linked monitors... they were too flakey. What I do now is I monitor the high res stream, but I tell Zoneminder it's low res. So, my camera is 1080P or more, in the Source settings I tell Zoneminder it's 640x360. Zoneminder automatically resizes and does detection on the low res ...

Howdy all! So I've been swapping the cameras at my dad's house away from the Q-SEE ones as they've started dying at an alarming rate. I purchased a couple Reolink RLC-520A cameras, firmware v3.1.0.801_22010701, and they work absolutely perfectly. Zero issues. I also purchased a Reolink Duo 2 PoE and ...

Howdy all! I've been running a rock-solid ZM setup without any real issues (except one caused by HomeAssistant, which I've now disabled), until recently. Essentially, zmNinja runs fine for hours at a time, and then it will "hang" at a gray screen called that says "loading"... The only thing I can ...

That's correct. No links, no linked camera problems / easier to configure. Sounds simple, huh? There are two (3) reasons why not to use linked monitors: 1) Modect/nodect doesn't always detect events (main reason). 2) HDD space is not that expensive (use passthrough though) 3) Linked monitors can ...

I agree. Something tells me that we're the only ones keeping such metrics, and since it doesn't affect performance, people probably don't notice it.

Ha... I resorted to a cronjob that restarts the apache2 service everyday at 3am as well. Same effective result.

Further digging points to the fact that it's DEFINITELY apache processes that continue to increase. I've tried limits.conf and also adding systemd variables to the apache2.service file. Neither results in either an indication that my values are being honored, or a fix to the problem. The process ...

So... I've made some changes based on the recommendations here: https://forums.zoneminder.com/viewtopic.php?f=43&t=31006 Unfortunately, it hasn't made any difference... Anyone have any ideas, there's obviously something going on here, but my guess is that most folks aren't monitoring to this level ...

Looks like this made no difference for me. Things are still climbing.

I just edited my post above... Looks like it might actually be working. It's related to the root user and the * domain. Going to monitor. Will report back. It only takes a few hours for the graph to trend noticeably upward.

Interesting... After a reboot, it seems as though my limits.conf file is being ignored... ulimit -a is showing the old values, not the new ones... Any pointers? EDIT: Might not actually be an issue... apparently when using * as the domain, the root user is unaffected, and currently, zoneminder runs ...

* soft nofile 90000 * hard nofile 90000 * soft memlock 5120000 * hard memlock 5120000 * soft nproc 127680 * hard nproc 127680 Frank - Once again thank you!! My original values were: max locked memory (kbytes, -l) 65536 open files (-n) 1024 max user processes (-u) 128118 I used your numbers blindly ...

For my new settings, I've set nofile and nproc by times 10 and increased the memlock by about 1GB to the following values (for both soft and hard): new: - nofile 6553500 - memlock 5120000 - nproc 127680 Frank - This is very helpful. By any chance, do you know how to query what the values currently ...

Finally, after increasing the nofile and memlock values in my /etc/security/limits.conf the problems are not longer exists. After this change, everything works and even my load on the system is now way lower than before. Hey Frank. I'd like to investigate this for myself and see if it solves my ...