ZoneMinder Forums

The only really safe solution to this is to fork when you have to introduce a compatibility-break; create a new separate app called, frex, "zmNinja 2.2", and then put new updates into that. If you're really nice, you'll backport security fixes... :-) This may introduce it's own problems; I don't kno...

Gotcha.

The thing you need an answer to is a Docker question, and I'm not (yet, at least) a Docker guy; hopefully one will wander along.

Is your separate storage volume visible inside the container, and how did you make that be so?

Correct -- while it's a bit obscure, you can disable autoupdates for a single app in the Play Store App. Go to Hamburger Menu -> My Apps -> Installed [tab] and pick the app. Then drop the three-dots menu in the top right corner, and uncheck "Enable auto update". You can probably do it from the app s...

#nice

In fact, it appears applying that patch to 1.32.3 makes it ...

Oh goodie.

Not only can't I load MR anymore, I don't even seem to be able to load the console, even after backing the patch out.
[ ... ]
Nope, there's the console.

Hmmm...

Sadly, applying that fix didn't help; I can see the events for the various monitors in the scrool, but while it happily counts across the timeline, all the monitors all say No Data (over some frozen image intended to tell which which camera they are).

Well, in trying to look at montage review history for a time range I find that I now *only* get No Data for all 12 monitors, and when I look for getImageSource in montagereview.js in that path, that function doesn't appear to be defined in that file in 1.32.3. Huh? Oh. I was looking at montagereview...

Yup, it appears you do... unless that's not the /cgi-bin/ that it's complaining about.

It's not possible you have more than one apache installed on that machine, is it?

I think the next thing you need to do is make sure your zoneminder user has at least search (x) permission on all the components of /usr/lib/zoneminder/cgi-bin If your ls(1) has the switch, you can use^W^W^W^W^W^W^W Well, I *thought* ls had a switch to show all the directories in a pathname... Anywa...

"One camera won't work until I disable the other" is very often "I don't have enough shared memory".

Assuming this is a new install; try setting both cameras and both monitors down to 640x480 24-bit at about 6fps, and see if that works.

Generally, this has to do with the Apache config on the linux -- in your case, Raspbian -- server. Exactly what's not happy depends on how Apache got installed; I think Raspbian has a package for it. I'd try # find / -name cgi-bin -print to locate that directory, and then # ls -ld $FULLPATHNAME to s...

Datapoint: I'm on 1.32.3 updated from 1.30.2 on U18LTS, and I've seen this *a couple times*. Reloading the montage review webpage has generally cleared it, maybe twice.

In general, it seems to work a lot better and faster than the old MR, for me.

Interesting.

Having recently updated to 1.32.3, I've been finding that the ability to see an event timeline for a single monitor helps a lot in this task; how's your New Thing going to work? Or are you that far along yet?

There is a parameter in monitor setup -- I don't recall which one right now, but the online help says -- which you should make sure is set to a higher FPS than your camera is actually configured for, and this symptom is exactly what you see if it's not. Go to the monitor setup, and check the help te...