ZoneMinder Forums

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...

I thought I saw you get an answer to this in another board (cross-posting's frowned upon, BTW), but the answer is probably that you don't have enough shm (shared memory) for the number and size of frames configured for both cameras. Switch both -- in both ZM and the camera -- to 640x480 by maybe 5fp...

bbunge wasn't being an asshole.

I won't comment on my opinion of you just now, though.

I updated to 1.32.3 about a week ago, atop U18, and it worked fine for me as well.

Are the users not created, or is *authentication not turned on to require them*, a separate proposition?

Shared memory; ZM needs enough to keep around a number of frames from each camera at its framerate and depth of motion detect overlap. The control console tells you what percentage of shm is in use.

I note also that your URL is rtsp:user:password...

If that's not a typo, it must be rtsp://user:password...

And yeah, you might run out of shm with a raster that big, even with only one camera.