ZoneMinder Forums

changing filter from the original conditions to this has solved my problem. imgur com g5JIlG3 Now cooldown tick is dependent on time set in options. (Weird!) Thanks for all your help. Could a malformed SQL check be imposed on filters before they are saved? (Cannot save : invalid) I used 'not equal ...

Well, this brings out the real problem!! The SQL query being formed is not correct. Look at the logs which are displaying the SQL queries: You will notice irrespective of the current time, the SQL Event Start Time does not change. For approximately 5 minutes it is saying "Give me events with a ...

1) Can you please use the updated zmfilter script I posted above?
2) Looks like you have enabled Frame Server - just for now, please disable it

I just noticed you have Asc in the filter match. Can you please change it to descending just for now?

Also, please use this latest zmfilter.pl https://gist.github.com/pliablepixels/5 ... f595cbd9d7
I've added more logs so we can see what is going on

zmfilter.pl is back to being stable. Getting SQL queries every 20 seconds, but same batch processing as far as filters go; anywhere from 2 to 5 minutes until filters will see an event. i'll re-run the scenario and gather logs in a little bit. Okay. Look forward to the uncut logs Please sort them by...

Whoops looks like there was a typo in line 1175
dbh needs to be $dbh

Please make that change - I don't know how that $ got removed

That explains why the new zmfilter crashed the moment it matched first - this is in the "execute" subroutine which gets called on match

Does it crash/display any error if you run it manually after triggering an event? Good question. something new. ╰─$ zmfilter.pl alertFile 130 ↵ Name "Net::SFTP::Foreign::debug" used only once: possible typo at /usr/bin/zmfilter.pl line 821. Can't locate object method "prepare_cached&...

Does it crash/display any error if you run it manually after triggering an event?

I'll break up each file with a new line or the filename or something next time I combine them to make it easier to think about. here's a time sorted one. gist github com segordon c612301a61c8a39ff50a the same big gist, but sorted. *sigh* You're right. It's crashing every time the event matches, but...

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

I don't see zmfilter crashing at all in the large gist you provided at https://gist.github.com/segordon/53558a3a0552f180f1b8 IT only crashed right at the start - lets assume thats because all of ZM did not start. It's hard to debug logs if you only post a small snapshot like the latest one which is ...

I just re-created your settings at home: a) set a filter to send email b) reload 300 c) interval 20 Force generated events and each time my logs showed the filter executing and I get the email right then (in a matter of seconds) I'm curious why zmfilter is crashing for you. I am using the same zmfil...

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

Here is the modified zmfilter.pl --> please keep a backup of the original, replace with this one, restart ZM https://gist.github.com/pliablepixels/5bb2e1408af595cbd9d7 It adds 2 things: a) Adds a log of the query b) Forcibly reconnects to DB every 20 seconds (not a good idea, but lets go with this f...