[SOLVED] What is this found iterator at beginning of queue warning

Discussions related to the 1.36.x series of ZoneMinder
Post Reply
LoriM
Posts: 3
Joined: Sun Apr 27, 2025 9:02 pm

[SOLVED] What is this found iterator at beginning of queue warning

Post by LoriM »

Found iterator at beginning of queue. Some thread isn't keeping up

I get this warning every time an alarm goes off on every camera
I'm on Ubuntu 24.04 LTS server
ZM - v1.36.35
using Modect

Fresh install this week, used these directions (https://zoneminder.readthedocs.io/en/la ... 2-04-jammy). My cameras are old, maybe I need to upgrade, maybe it's a setting, everything is pretty much on the defaults still, just started to tinker/tweak. I used Zoneminder a few years back and really liked it but I have no clue what my settings were. My old server crashed and I just didn't get around to replacing it until last week.
Attachments
Screenshot 2025-04-27 170548-zm.png
Screenshot 2025-04-27 170548-zm.png (63.19 KiB) Viewed 3579 times
LoriM
Posts: 3
Joined: Sun Apr 27, 2025 9:02 pm

Re: [SOLVED] What is this found iterator at beginning of queue warning

Post by LoriM »

Took some tinkering but I got rid of the warning

First thing I did was went into the camera settings (not in zoneminder) and turned down the frames. From what I found searching the forums is that the Frame Rate doesn't need to be so high (not making movies) so I set mine to 15. Then the Key Frames should be 2xs that number so I set that to 30.
This did not solve the iterator issue but it certainly fixed my CPU usage issue, everything on my server looks so much butter and the ZM load went way down. Live stream doesn't look too bad with these settings either.

All of this in ZM settings.
Next thing I tried was entering a number in the Maximum Image Buffer Size (frames), I read on the forums that suggested 121 so I tried that, didn't do anything so I bumped it to 150. May have helped but issue remained so I bumped it to 200. Seemed better but still getting the warnings.

Next thing I did was dumb luck because my recordings had like no pre frames, the alarm start was practically the start of the event. I set the Image Buffer Size (frames) the suggestion is 3-5 so I split went in the middle with 4. I then set my Pre Event Image Count to 2. This seemed to fix the issue and I have a smidge more frames before the alarm when viewing. It rained last night so my cameras have a ton of recordings and no warnings.. Happy camper!

Got a new error this morning when watching the events, I've seen this one but never really dug in and it was so easy to fix.
getCmdResponse stream error: socket_sendto( /run/zm/zms-198095s.sock ) failed: Connection refused - checkStreamForErrors()
A little digging and I changed my Video Writer to passthrough and disabled the Save JPEGs. Seems to have worked and I have a lot more pre event images. I also understand that this setting is less taxing on the system to as it makes MP4s vs JPEGS.
Attachments
Zoneminder Storage Settings.png
Zoneminder Storage Settings.png (38.9 KiB) Viewed 2128 times
Zoneminder Buffer Settings.png
Zoneminder Buffer Settings.png (34.5 KiB) Viewed 2128 times
Foscam video settings.png
Foscam video settings.png (22.66 KiB) Viewed 2128 times
LoriM
Posts: 3
Joined: Sun Apr 27, 2025 9:02 pm

Re: [SOLVED] What is this found iterator at beginning of queue warning

Post by LoriM »

Oops, made a mistake.. setting the save JPEGs to disabled created a flood of new errors and warnings. I use MODECT so I'm analyzing, had to change that to Analysis image only (if available). Now things are looking better.. lol
Attachments
Zoneminder Storage Settings.png
Zoneminder Storage Settings.png (51.88 KiB) Viewed 2115 times
Post Reply