Preclusive zone goes into la-la land

[schuitz]

Everything working great here with 4 zones on 1 monitor. I decided to try a preclusive zone to eliminate false alarms from overall brightness changes in my image. I have a roadway in the upper corner of my monitor, and large objects going by cause the camera exposure to auto-adjust. My central zone can have a legitimate alarm pixel max of 90,000, which is the majority of the zone. But if I get this many alarmed pixels in my secondary zone as well, it generally indicates an exposure change.

Not fully understanding how to apply preclusive zones, I added a fifth zone that was rather large and overlapped my other 4, figuring that I could set the min alarmed to something like 120,000 pixels. This now strikes me as probably a bad idea from a computational standpoint. It may not be relevant, I don't know. But now I have:

Code: Select all

Jun 10 13:59:14 pc-00101 zmdc[2143]: INF ['zma -m 2' crashed, signal 10] 
Jun 10 13:59:15 pc-00101 zmc_m2[2722]: WAR [Buffer overrun at index 0, slow down capture, speed up analysis or increase ring buffer size]
Jun 10 13:59:15 pc-00101 zmu[3267]: ERR [Shared memory not initialised by capture daemon]
Jun 10 13:59:16 pc-00101 zmwatch[2184]: INF [Restarting capture daemon for GarageCam, shared memory not valid] 
Jun 10 13:59:16 pc-00101 zmdc[2143]: INF ['zmc -m 2' stopping at 06/06/10 13:59:16] 
Jun 10 13:59:16 pc-00101 zmc_m2[2722]: INF [Got signal (Terminated), exiting]
Jun 10 13:59:16 pc-00101 zmc_m2[2722]: ERR [Select error: Interrupted system call]
Jun 10 13:59:16 pc-00101 zmdc[2143]: ERR ['zmc -m 2' exited abnormally, exit status 255] 
Jun 10 13:59:16 pc-00101 zmwatch[2184]: INF ['zmc -m 2' stopping at 06/06/10 13:59:16] 
Jun 10 13:59:19 pc-00101 zmu[3275]: ERR [Shared memory not initialised by capture daemon]
Jun 10 13:59:23 pc-00101 zmu[3282]: ERR [Shared memory not initialised by capture daemon]
Jun 10 13:59:26 pc-00101 zmu[3288]: ERR [Shared memory not initialised by capture daemon]

Whoops, bail. Something has gone wrong, so I delete the zone. But the problem logs remain, zma is still ill. Restart all processes, even reboot the machine. Zones table in the db looks ok.

I think I broke this once before, and eventually rebuilt all the zones from scratch. It won't take me long, but just wondering if anyone had any brighter ideas. I'm still on 1.22.1.

MikeS

[schuitz]

Deleting all the zones and putting them back indeed clears the problem. But I can't replicate the failure now . Please disregard.
MikeS

[zoneminder]

Thanks for the update. There _shouldn't_ be any problem with the zones set up as you describe and your errors unfortunatley don't contain enough detail to track down the problem.

There were some zone irregularities in previous 1.22.x versions which 1.22.2 should have fixed on the fly but in some cases broken zones may have remined. In which case cleaning them out and redefining them should fix the problem as you have found. As you are still on 1.22.1 you should check that the zones don't exceed the image boundary and I think that version sometimes let you define a zone from 0 -> 320 in width where the legal values are only 0->319 if your image is 320 wide for instance.

[schuitz]

OK, thanks. I noticed the image boundary issue and will upgrade to the latest when I get a chance. In the event that I'm able to reproduce this, where should I go digging for more useable debug info? I searched most of the logs in /tmp and sifted through the db a bit, but didn't see anything that looked relevant.

Cheers
MikeS

[jeffshern]

I also had this error in my /var/log/messages.

Shared memory not initialised by capture daemon

I was not able to view any camera via stream or still image. Realized when I got back from vacation that there was not one image captured... eeck, oh well, lucked out...

I must have had a boundry issue, I removed the zoning on a camera that is no longer in use (the dog chewed through the cable), restarted ZM, and was instantly able to see my other cameras.