zmtrigger is being killled...how to diagnose?

[MichaelTiemann]

I have several AXIS cameras (mostly 215) managed by Zoneminder. There are several things not quite right, but the one vexing me most right now is zmtrigger, which seems to be badly misbehaving on one particular camera. zmdc.log shows this:

zmdc.log:08/14/2012 04:49:14.094423 zmdc[26746].ERR ['zmtrigger.pl ' exited abnormally, exit status 9]

and this shows up in messages, too:

Aug 14 04:49:14 bbsvr zmdc[26746]: ERR ['zmtrigger.pl ' exited abnormally, exit status 9]

Looking at the source code, it appears that somehow an fwrite is failing to write something of IMAGE_SIZE to a pipe, but why that fails completely eludes me. I don't know what parameters/environment variables to use to run zmtrigger from the command line or a perl debugger to get more info. Any ideas?

[MichaelTiemann]

For the six or seven of you following this thread, I have a new datapoint: when I only enable TCP notification (Tn) it works as expected. When I also enable email notification (En), zmtrigger gets itself killed. Any thoughts why?