zmtrigger.pl dying with exit code 9

[mpco]

I'm running 1.25.0 on Centos 5. I've installed it roughly according to this guide:
http://www.zoneminder.com/wiki/index.php/CentOS

I'm using zmtrigger.pl for around 6 Axis cameras per this guide:
http://www.zoneminder.com/wiki/index.ph ... nDetection

Intermittently, I'd say around 30 minutes after starting zmtrigger.pl, it will exit with status 9 and report:
variable is not a string at /usr/lib/perl5/site_perl/5.8.8/ZoneMinder/Memory/Mapped.pm line 109

That line is doing munmap( ${$monitor->{MMap}} );

Unfortunately, I'm not too much of a perl wizard, but I've tried putting some checks to make sure $monitor->{MMap} is defined, but that didn't seem to help.

Anyone have any ideas on the root cause, or a better check to make sure it doesn't blow up? I'd like to get to the bottom of it instead of just making a cron job to constantly restart zmtrigger...

[Carrier82]

Does the zmtrigger.pl work without the Axis hack? There are alternatives for camera based motion detection. Perhaps sending a http message could work better? Also make sure you have unwanted protocols commented out of zmtrigger.
http://www.zoneminder.com/forums/viewto ... 21&t=19540

[mpco]

I haven't tried it with a stock zmtrigger.pl. I wouldn't think that the regex on that string would cause it to barf like that, but, like I said, I'm not a perl expert. That's the only edit to zmtrigger I did with the exeption of only having it listen to the tcp interface.

If that is what causes it to die, I'd be really interested if anyone had an idea why that happens if for nothing other than my own curiosity.

[Carrier82]

Testing stock zmtrigger would give clues whether the problem is within the stock code or the Axis patch. Stock works for me at least.

[mpco]

To follow up on this, recompiling zoneminder with --enable-mmap=no appears to have fixed the problem for me.