ZoneMinder Forums

.11 has database issues.

viewtopic.php?f=43&t=31390

After numerous unsatisfying experiences with various versions of Zoneminder™, I decided build a Bullseye box and try to roll in backports .11, but ran into this: root@ryzen:~# /usr/bin/zmupdate.pl DBI connect('database=zm;host=localhost','zmuser',...) failed: Access denied for user 'zmuser'@ ...

Certainly. Who wants that? The sub stream is just a grainy 640x480.

Betcha Reolink marketing figured they'd undercut the pricing on these POE bullets by offering high-res optics using crap processors. Most people who buy these things have 1 or 2 cams and never look at anything except the proprietary client view. Forget trying to connect it to something in any sort ...

Hikvision gets: rtsp://login:password@ip.address:554/H264/ch1/main/av_stream Reolink gets: rtsp://login:password@ip.address:554/h264Preview_01_main One clue I see in the Reolink client is a "Performance" section showing CPU utilization on the camera itself. At minimal settings (6fps) the cam still ...

Wow, I had a line in my sources.list some time ago long before I upgraded, and that version never changed. Whodathunkit?

I believe the problem is Reolink simply does not play well with Zoneminder (for whatever ACTUAL reason). I squelched mine down to very minimal frame rates/colorspace h.264 profiles, etc. - anything to lower the load on the system, until I had 11 cams idling along in modect not even breaking a sweat ...

I thought the little round console buttons on the left were just a network connection state. Then I noticed when I stop ZM, some cams show a red button and some show orange. The Reolinks show red and the Hikvisions show orange. Anybody know what that means or why they might show a different status ...

Sorry, but I wouldn't be spending my time on it unless it was aimed at proper integration with the OS. Two major releases hosting the same "abomination" is all the exposure to that sort of attitude I can tolerate.

Which brings us to zmrepo. If using zmrepo, and there is a running mysql or mariadb server running, the db will be automatically created. Otherwise you have to create it yourself. Been there, done that. A number of times. When doing upgrades you should take a db backup. You should ACTUALLY have a ...

Versioning and major releases are purely development issues. Users running production systems in environments with real implication for day-to-day operations don't play those games. Debian releases are planned and executed in a systematic, forthright manner. Package maintenance for ZM? Does anybody ...

1.32.23 is working flawlessly for me on Buster. If that's what comes with Bullseye, that's what I'll use.

It's trivially telling how CPU temp tracks across a 30°F range, depending on what ZM features are active at any given time.

i am just curious why with the same setup (hardware, fps, resolution, number of cameras etc) has the 1.36.5 showing higher cpu load and iowait compared to 1.30.4. Timing. The faster code simply has time to do more work. There's alot going on after you start recording a dozen or more cams. I proved ...

Mine's been on 1.32.3 with a sources.list entry showing 1.34 since day 1.

I won't waste my time trying to figure it out and just build a new box at 1.4x someday. See how that goes.

You're not getting any support here.