You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
storage directory change were not accepted, i create storage dir to an usb disk, the new storage dir is listet in the zm interface but it is not used. I disabled and later delete the default storage dir ( var(cahce/zoneminder ) but the error still persists. Sometimes in the past i got this problem, so i create a symlink in /var/cache/zoneminder to /storage/dir.
This works great but some routines overwrite the symlink with a directory, so zoneminder delete all records using the "disk full " filter if the default storage is used.
The sollution is now to remount the target storage dir into the zm default dir ( mount --bind </storage/dir> /var/cache/zoneminder )
Should work but a working configuration in the zm interface is better.
regards speefak
The text was updated successfully, but these errors were encountered:
speefak, when you create a storage area for Zoneminder, in order for zm to use it, you have to configure it in the monitor(s) you want stored there, else is going to show as configured but is not going to record in that location...
zm on Debian 10 / php 7.3
storage directory change were not accepted, i create storage dir to an usb disk, the new storage dir is listet in the zm interface but it is not used. I disabled and later delete the default storage dir ( var(cahce/zoneminder ) but the error still persists. Sometimes in the past i got this problem, so i create a symlink in /var/cache/zoneminder to /storage/dir.
This works great but some routines overwrite the symlink with a directory, so zoneminder delete all records using the "disk full " filter if the default storage is used.
The sollution is now to remount the target storage dir into the zm default dir ( mount --bind </storage/dir> /var/cache/zoneminder )
Should work but a working configuration in the zm interface is better.
regards speefak
The text was updated successfully, but these errors were encountered: