I'm trying to run Zoneminder-1.34 on a Proxmox-based Ubuntu18.04 server guest. I keep getting error messages (see attachment) and am not sure what is going wrong.
I've set "Purge when full" to 50%, but this did not resolve the issues. It gets worse (more frequent crashes) when I have more than one camera.
I don't think it's bandwidth-related. I've had ZM-1.32 running before as a Xen guest with up to 5 cameras. No problems with that.
Looks like your events directory does not have www-data ownership. If you set another storage drive it too needs www-data ownership in the events directory.
Thanks for the idea. But it looks like the owner (and contents) all belong to www-data.
I've noticed that there are errors in the "timezone" (see below). I'm getting this even though "php.ini" and the ZM system setting are both "America/New_York". Could this be the problem? Why am I getting such errors?
I also am seeing some new errors that seem to relate to not having enough storage (???) How do I increase the storage for ZM on Ubuntu18.04 server? I gave the VM 50GB, but ZM seems to have only a couple of GB available for videos.
I'm definitely suspecting a video-storage-space problem. On the console, the used storage slowly increases to 100%, then ZM crashes. But, the filter is set to purge at 50%. So what's going on? Do I need to allocate more space? (the VM has 50G and the ZM installer only seems to be allocating 4G). How do I adjust this? The disk space that ZM is using seems to be the "3.9G" one (shown below).
You might be out of inodes instead of actual space. Try df -i
You may be storing jpeg's instead of .mp4, so each event is a billion jpeg files instead of 1 .mp4.
Switch to h264 passthrough or x264 encode and turn off jpeg storage.
The inode usage stays at about 41% and doesn't change much. What does happen is that, upon initial launch, the "Storage" display on the console shows about 85% usage, and this slowly ramps up to 100%, then ZM crashes. The "purge when full" filter doesn't seem to be doing anything.
I tried switching to mpg rather than jpg as you suggested. I set the camera to x264 and h264 in turn. The same pattern prevailed - slow rise to 100%, then crash.
The weird thing is that this is happening with ONE camera. I used to run 5 cameras on a less-capable computer and had no problems. I'm basically just trying to move ZM to a new, faster machine (while changing from Xen to KVM). The new machine uses fast SSD storage rather than HDs, if that matters.
Your help is appreciated. By the way, thank you for your ppa.
Eric
So, after multiple attempts to get this working, I finally switched from Ubuntu18 to Debian10. Works much better now. I never did determine the original problem.
