1.36.11 could not start 13 cameras at once
1.36.11 could not start 13 cameras at once
Hello.
updated from branch 1.35 to 1.36.11, after reboot the server hung tightly. When we managed to break through, stopping the ZM processes, the PC came to life. At startup, the PC hangs. He immediately eats up all the memory and swap. Turning off the cameras and turning on one by one, all the rules
updated from branch 1.35 to 1.36.11, after reboot the server hung tightly. When we managed to break through, stopping the ZM processes, the PC came to life. At startup, the PC hangs. He immediately eats up all the memory and swap. Turning off the cameras and turning on one by one, all the rules
Re: 1.36.11 could not start 13 cameras at once
worked for an hour and hung again
Re: 1.36.11 could not start 13 cameras at once
…
- Attachments
-
- BC6D1670-6996-4271-8143-EDA5F2D5F024.jpeg (369.38 KiB) Viewed 8906 times
Re: 1.36.11 could not start 13 cameras at once
Your cameras have a huge keyframe interval. Either set it lower in camera, or set a reasonable MaxImageBufferCount.
Or post some logs FFS.
Or post some logs FFS.
Re: 1.36.11 could not start 13 cameras at once
I have a multiserver.
Now I transferred the web and the base to a new one, I left only recording and viewing on this. Until no longer freeze.
the logs were disabled, I thought there are a lot of them and load fs, what settings should I put on the log in files?
And also, I have been observing the problem for a long time, sometimes, on a rented camera, the recording lasts longer than a given hour. Maybe 2-4-6 hours. Maybe for a minute.
Now I transferred the web and the base to a new one, I left only recording and viewing on this. Until no longer freeze.
the logs were disabled, I thought there are a lot of them and load fs, what settings should I put on the log in files?
And also, I have been observing the problem for a long time, sometimes, on a rented camera, the recording lasts longer than a given hour. Maybe 2-4-6 hours. Maybe for a minute.
Re: 1.36.11 could not start 13 cameras at once
https://zmeventnotification.readthedocs ... ks-logging
Applies for general ZM debugging as well. Except for LOG_DEBUG_TARGET. We are interested in _zmc
Applies for general ZM debugging as well. Except for LOG_DEBUG_TARGET. We are interested in _zmc
Re: 1.36.11 could not start 13 cameras at once
example log
- Attachments
-
- cam.zip
- (9.08 KiB) Downloaded 47 times
Re: 1.36.11 could not start 13 cameras at once
Okay so that log shows one monitor, number 11 successfully capturing a 1080p stream.
So not much use.
So not much use.
Re: 1.36.11 could not start 13 cameras at once
You need more ram, and probably more cpu. Decoding 1080p streams takes a lot.
-
- Posts: 349
- Joined: Sun Jun 05, 2016 2:53 pm
Re: 1.36.11 could not start 13 cameras at once
Also, reduce frame rate in the cameras. Most people dont need NFL broadcast-grade high frame rate. Mine run at 10FPS (set in cameras) and seems to work pretty well in live view. This is 10 FPS: https://rumble.com/vqbg4j-turkeys-being ... of&mrefc=2
-
- Posts: 349
- Joined: Sun Jun 05, 2016 2:53 pm
Re: 1.36.11 could not start 13 cameras at once
You effectively increased the available RAM by removing the DB from the server.