ZoneMinder Forums

Perhaps I am misinterpreting lines 142-166? Abnormal exit status on zmfilter being reported by zmdc, along with new pids every restart? Referring to that big gist. I think those should be ignored - that's happening when ZM is initializing. I've forced DB connections that may be causing this. If you...

Perhaps I am misinterpreting lines 142-166? Abnormal exit status on zmfilter being reported by zmdc, along with new pids every restart? Referring to that big gist.

I'll take a look at you logs - how often is the new zmfilter crashing for you? each time a new event occurs? The crashes coincide with the modified entries we added, zmfilter seems to crash when those appear in the log. gist github com segordon 0b307b0239b6859548f5 worst case i'll purge the PPA and...

Can you please post detailed logs of what is going on? Please don't truncate. Sure. Here is /var/log/zm/* with logging enabled. gist github com segordon 53558a3a0552f180f1b8 Four events forced in that log. 14:57:43, 15:00:59, 15:03:35, and 15:04:10. take a look at the zmdc lines in the linked log. ...

The 'Force closing..' message stops re-appearing every 20 seconds after the first abnormal exit, and then the timer is increased from the every 20s to every 3-5 minutes. The abnormal exit seems to happen every time it hits a valid event, so it'll hit that first event quickly and then revert back to ...

So I'm confused - where are we now? The "PP - Force closing DB just to test" log should occur every 20 seconds. Your latest log seems to show it recurring in minutes. You might have changed the wrong variable. Please make sure: FILTER_RELOAD_DELAY = 300 FILTER_EXECUTE_INTERVAL = 20 and re...

So I'm confused - where are we now? 3 to 5 minute batch processing, still. I thought I had seen an improvement, but it was just likely early in the tick cycle when I hit the alarm, so the results were fast. gist github com segordon 2087ccb611440c7beb56 Also, we're now getting this : 2015-08-12 13:4...

Seems to have sped things up, looks like the test script is getting hit within the minute now. I am going to reduce the filter interval back to 300. Here's the log. gist github com segordon 7865cc0dd9db25023b62 The test event was at 13:34:05 edit: looks like its firing around 3 minutes now.. gist gi...

Sure, that's easy. gist github com segordon 05f12db6dad483fca114 This is a non-crashing copy of zmfilter.pl correct? Correct. I also changed the filter reload delay. Event occured at : 13:20:50, filter hit it at 13:25:16 2015-08-12 13:25:16.504460 zmfilter 6983 INF Executing '/tmp/eventcatch.sh /us...

Sure, that's easy.

gist github com segordon 05f12db6dad483fca114

Two things : After info line insertion, zmfilter is failing.. 2015-08-12 12:42:49.427750 zmdc 22138 ERR 'zmfilter.pl ' exited abnormally, exit status 9 zmdc.pl I think it may be caused by the extraneous space between Info and the parenthesis; but I don't know enough about perl to know if it is white...

Sure Practically instant. the huge wait was me typing my password

(out to lunch, replies may be a bit slow for a bit)

Okay, lets see if its a caching issue. Make a backup of zmfilter.pl, then replace all occurrences of "prepare_cached" with "prepare" and run again. Does that help? same behavior, everything getting processed in batches. Forced two alarms at 6:34:08 and 6:35:02, neither were proc...

same behavior, everything getting processed in batches. Forced two alarms at 6:34:08 and 6:35:02, neither were processed until 6:38:41. Here is a snippet from the weblog, the first two event hits were existing when I first created the filter, the second two are the ones that are part of the manual a...

Okay so far: 1. Zmfilter is not crashing 2. It is being invoked every 20s but your filter is executing late So my suspicion then is either alert filter or the sendmail command. Can you please post how you've defined your filter? I'll take a look tomorrow. As a next step lets modify zmfilter to writ...