ZoneMinder Forums

In which case, it looks like the documentation needs to be corrected. Please see the attached screenshot:

zmNinja app had the same issue. However, I discovered this is caused by by a very high value of AUTH_HASH_TTL. I am not sure what the tipping point exactly is but when I reduced it from 720 (30 days) to 168 (7 days), the problem vanished.

I am running zoneminder 1.36.33 on debian 12 bookworm and am using builtin authentication. Everything works fine on a web browser but when I log in on a zmNinja (pro) app, I can see a very fast, continuously looping message "zoneminder authentication success" at the top of the app screen. This is ...

An update on my problem and the analysis I have done in the past one week or so: I had earlier explained that all my cameras are monitored with a software called nagios which runs on the same server as ZM and which works by pinging each camera every 5 minutes. Generally this is fine for my purposes ...

I have checked the network bandwidth usage on the server and that does not appear to be a problem. Please see attached a screenshot of the output of nload with all 6 cameras streaming. I am not an expert in this area but for a 10/100/1000 gigabit NIC card that the machine has, the network load does ...

I have six identical cameras connected to the ZM box over wired (POE) circuits. The cameras are continuously monitored by a software called nagios running on the same host as zoneminder. Nagios monitoring reports have not shown a single missed ping for months. However, I still keep getting these ZM ...

Please, can anyone provide any insights into this issue? I still get a few prematurely terminated clips every day and in every single case, I see the following in the logs:

I made a couple of changes to the configuration to work around this problem: 1. Reduced source frame interval from 20 to 5 and FPS from 15 to 5 for all six of my cameras 2. Increased WATCH_CHECK_INTERVAL from 15 to 60 in ZM 3. Increased WATCH_MAX_DELAY from 45 to 180 in ZM I know the last 2 changes ...

Yes, the OS and ZM are on a SSD. However, ZM storage is on a 4TB HDD.

Thank you for your responses. I have double, triple checked all my connections but can't find anything wrong. I have a network monitoring system in place whose 72-hour camera ping reports (from the ZM box) are all green. I have also checked syslogs & kernel logs and can't find any signs of crashing ...

I have been using zoneminder for years and am currently on ZM 1.36.33 with six monitors running in mocord mode. All my cameras are identical, with each camera streaming in at 2592X1944 / 15 FPS. I have configured each monitor to save recordings in section lengths of 300 secs. While this works as ...

Recently upgraded to 1.36.29. All looks fantastic, however, I have not been able to increase the web session timeout beyond its default 1 hour (I think). How can I change the session timeout to something like a week? I have tried php.ini (session.gc-maxlifetime) and the zoneminder COOKIE_LIFETIME ...

Thanks iconnor. Once again, you have bailed me out. 1.36.29 works like a charm

I have been using Zoneminder for years without issues. This morning, ever since I upgraded to 1.36.5, I have been seeing an error in the logs every time the system tries to save a video at the end of a recording interval (currently set to 300 secs). The error message I see is as follows: Error ...

Hi iconnor, It is my privilege to interact with you directly. I now see the point and also recall that I had done something similar on an eCommerce website with a huge number of saleable products (and their prices, stock levels etc). My apologies for the oversight. Great product and a fantastic ...