Hello, I'm not good at computer technology, on Ubuntu 24.04.1 server Zoneminder v1.36.35 is installed, 8 cameras 1600x1200 (main channels) which are controlled by sub channels 352x288.
Sub channels perform motion detection and main channels only record.
The problem is that the main channel does not always work (records) when a signal comes from a sub channel, let's say there are 26 records in the sub channel but only 20 in the main channel.
The system constantly curses: "Found iterator at beginning of queue. Some thread isn't keeping up"
According to the forum recommendation: Maximum Image Buffer Size (frames) is 150
Image Buffer Size (frames) (?) 3
Nothing changes.
system load is 3-4
system is:
Intel(R) Xeon(R) CPU X5650 @ 2.67GHz, 24 cores
RAM 32Gb
Storage 9Tb.
If you need logs, please tell me which ones and where to look.
Skips alarms
Re: Skips alarms
I asked the same question to chatgpt, he thinks that the HDD speed is not enough to be able to record events.
I use a hardware ride card in a ride5 configuration with 4 4TB HDD disks for storing events.
Since the Proxmox system disk I use is a ZFS mirror with SSD disks, I created a 100Gb virtual disk for the ZM container.
When I move the cameras to the ZFS disk, the situation does not change, the error does not change "Found iterator at beginning of queue. Some thread isn't keeping up"
If I use "force alarm" from the secondary channel, "Found iterator at beginning of queue. Some thread isn't keeping up" immediately appears on the main channel
Please help.
P.S. Sorry for the spelling.
I use a hardware ride card in a ride5 configuration with 4 4TB HDD disks for storing events.
Since the Proxmox system disk I use is a ZFS mirror with SSD disks, I created a 100Gb virtual disk for the ZM container.
When I move the cameras to the ZFS disk, the situation does not change, the error does not change "Found iterator at beginning of queue. Some thread isn't keeping up"
If I use "force alarm" from the secondary channel, "Found iterator at beginning of queue. Some thread isn't keeping up" immediately appears on the main channel
Please help.
P.S. Sorry for the spelling.
Re: Skips alarms
Hello, I don't want to but I will have to switch to the Agent DVR system, because ZM is not able to work with 4K (2688x1522) 10FPS. cameras. I left 1 camera in the system, and of course "zmc_m8 2064 WAR Found iterator at beginning of queue. Some thread isn't keeping up" is the only error, the camera uses the H264 protocol, initially the system saved .JPG I tried switching to video decoding, then the camera passthrough, and nothing changes.
Yes and by the way with one camera ZM uses 2Gb of ram... at the same time in the Agent DVR system currently working 5pcs. 2K10fps cameras and 2pcs. 4K 10fps and uses only 2.5Gb in operations. I don't mind high memory consumption in operations but the fact that the system constantly misses events is not satisfactory.
Yes and by the way with one camera ZM uses 2Gb of ram... at the same time in the Agent DVR system currently working 5pcs. 2K10fps cameras and 2pcs. 4K 10fps and uses only 2.5Gb in operations. I don't mind high memory consumption in operations but the fact that the system constantly misses events is not satisfactory.
Re: Skips alarms
Yeah. I'm missing lots of events with ZMES. I thought it was because I'm stupid.
And the events I do catch start too late on high-rez (triggered by lo-rez), even with Pre Event Image Count set to 20 frames.
Post Event Image Count = 20 seems to work, but Pre doesn't. I tried setting Pre to 40, but just got gray screen.
And the events I do catch start too late on high-rez (triggered by lo-rez), even with Pre Event Image Count set to 20 frames.
Post Event Image Count = 20 seems to work, but Pre doesn't. I tried setting Pre to 40, but just got gray screen.