ZoneMinder Forums

For some historical context, we used to store events in /usr/share/zoneminder/events and that dir has to be owned by www-data. Same with /usr/share/zoneminder/images etc. I fixed that in 1.32. So there should be no need for write access to anything under /usr/share/zoneminder. all that stuff got mov...

Could be. I don't have any experience with that cam.

However I have seen lots of cams that can't handle multiple streams at the same time. YMMV

ON the low res camera Monitor->Storage tab, set it to not store jpegs and nothing for Video Writer. db events will still be created, but files won't be stored on disk.

You can wait for 1.34.3, where the code will be updated to use the Options->Images->PATH_FFMPEG setting, at which point you could add -hwaccel cuda to that setting. In the meantime, you can edit /usr/share/zoneminder/www/views/image.php line 203 to add whatever you want. The place you SHOULD be seei...

Yes it is.

This is the #1 reported problem here. Someone asks every single day. Hopefully I'll be able to do something about that in the next release. Two possibilities: #1 your apache is configured wrong with respect to the cgi-bin path. Since you didn't say which distro, I can't advise about the right settin...

Post the settings from the source tab of your monitors. I suspect that the url to the camera is wrong.

I don't think this is needed... if it is then I would like to fix that in zm... sed -i "15i default_authentication_plugin= mysql_native_password" /etc/mysql/my.cnf The long and short is that we don't want to be dependent on the old mysql password stuff... add-apt-repository ppa:iconnor/zoneminder-ma...

Mostly looks ok to me,

One thing, don't add an index on ObjectScore.. adding indexes adds more work for the db to do on every insert and update, and we are likely to be filtering on something else that is already indexed, like StartTime.

In 1.32 and in 1.34 the Analysis Images has been moved to a per-monitor setting under Monitor->Storage->Save Jpegs.

I don't have the login for readthedocs. Have contact fixxermet etc.

You are probably running out of ram. default php settings allows 128Mb. Increase this in php.ini to something higher.

I believe this was fixed in 1.34.1

Archived events cannot be deleted, by design.
However Unarchiving them should work, at which point you should be able to delete them . I will test.

I would say the answer is "no".