ZoneMinder Forums

Hello.
there are three servers, updated to the latest version. And on one server it stopped updating the size of the recording file.
Where to look?

The logs?

the log is empty. Tell me who is responsible for this, otherwise they made edits to the zmaudit and zmfilter

update to 1.35.6~20200925151411-bionic

everything is back

I had a similar problem and updated to the most current 1.35.6 without resolution. I updated to 1.35.7 and still have the same issue. What am I missing here? There are two filters in the standard build ... PurgeWhenFull and UpdateDiskSpace. Why is there a filter to update disk space? From the sql error you can see the where clause isn't correct.

(E.Archived = '0' and >= '95')

It is missing the Diskspace reference

??

I thought I fixed that several days ago. We are up to 1.35.8 now...

Will apply 1.35.8 and test.

Thanks

One more thing .. can you explain the relationship between the disk space metric and the UpdateDiskSpace filter?

Thanks

The Update Disk Space filter updates the db entry....

It is too resource intensive to constantly query the fs for this, so we do it once in the background.

I jumped to 1.35.9 but continue to see no function from the purge filter. I enabled debug and ran the exposed sql. The events diskspace column is null.

Is it the diskspace filter that is supposed to update this column?

Any help appreciated

I'm going to jump to Ubuntu 20.04 and redo my zoneminder install. Something is jacked in my filters.

Related?

v1.34.23

I have just resized my storage partition and it is reflected in fdisk but I need to tell zoneminder that the disk space has increased. Zoneminder still shows the pre-rezize value.

How do I get ZM to refresh that value?

Rebooting seems to work here.

The partition change wasn't reflected with df, I neglected to resize2fs after rezizepart... that fixed it.