ZoneMinder Forums

Is it turned off in Options->Logging?

There probably is a log message in apache logs. Blank screen indicates a problem with the php.

#Changes since 1.36.29 - Test for definition of ZM_LOG_INJECT. We don't include the config when not logged in. So it won't be defined and an error will be logged - Fix saving from the function modal (and other modals) - left align option value column - when a config value is overridden via *.conf fi...

In 1.36 if zms has a problem sending fast enough, it reduces it's target fps. There is no code to make it go back up though. I have rewritten a lot of this in 1.37.

The problem is with your apache config.. The default apache config uses /usr/lib/cgi-bin but ZoneMinder's zms is in /usr/lib/zoneminder/cgi-bin.

ZoneMinder's default config for apache has a ScriptAlias line too, but they conflict.

Maybe try
sudo a2dissite 000-default
sudo systemctl reload apache2

Can you please follow the proposed ppa in your testing? It contains fixes prior to release and it would be great to get more testing. ppa:iconnor/zoneminder-proposed Currently should have a 1.36.30 package available. Alternatively build for the release-1.36 branch which is what the ppa is built from.

Probably when that was written an i3 was essentially a celeron, 1 core pretending to be 2. An i5 was a core2duo pretending to be a quad core. Nowadays the labels are almost meaningless. I think the gist of it was, get an i7 as they are the only decent intel cpu's out there. My real 8 core i7 3770 is...

Fixed. New packages building.

You can use cron job to run the filter. Don't check the run in background box .. then in cron job run zmfilter.pl --filter_id=[whatever the id is]

You could also sponsor the addition of the needed conditions in the filters...

And which version didn't consume ram?

There's not much in there that would eat more ram than before.

Which process is consuming ram?

Use the main monitor edit instead of the function popup for now

Packages should be available now

You must upgrade to the latest. 1.36.29. This issue was fixed a long time ago.

The last thing zmc does before dying is update the db record. If it crashes before doing this, or the db table is locked and the update fails, then it doesn't get update and the web ui thinks it is still running. I am adding a background task to clear these out but we should check your logs as to wh...