ZoneMinder Forums

Issue reappeared for some reason - out of nowhere.
Testing the stability again with FPS Report Interval of "360" frames...

Everything works fine now.
FPS Report Interval was the culprit.

Issue is resolved.

10 alarmed events later - the FPS Report Interval value of "720" @ "12fps" camera setup seems to have resolved my issue - but additional testing is still required. Will keep an eye out throughout this week for any inconsistencies and will post final conclusion in the start of next week. :D @iconnor ...

I have always set it as high as possible since its only function to my knowledge was to spam the logs. Please advise on its optimal value and if you could explain its function. Will perform testing with the value of 720 today (that means reporting every 1m for my camera setup). Will post results ...

Manual SQL querry: Fresh start of zoneminder service: mysql> SELECT * FROM `Monitor_Status` WHERE `MonitorId`=1; +-----------+-----------+------------+-------------+------------------+---------------------+ | MonitorId | Status | CaptureFPS | AnalysisFPS | CaptureBandwidth | UpdatedOn ...

I recreated the DB from scratch (from /usr/share/zoneminder/db/zm_create.sql) in my initial attemt to fix the issue myself. Executed your code with following result (no change to db it seems): mysql -h x.x.x.x -u zoneminder -p zm < /usr/share/zoneminder/db/zm_update-1.36.34.sql mysql: [Warning ...

Dear all. I'm having issues with the frontend since upgrade to 1.36.34 . Please help. The issue appeared after the upgrade from 1.36.33 . Tried recreating the Mariadb DB, reconfigured almost everything from scratch, can't seem to find a solution. ZmNinja shows the same status issues. The monitor ...