ZoneMinder Forums

I'm running V1.34.9 on a Centos 8 VM, with a system disk and a separate 'events' disk mounted at /home/events. Events are setup to use this 'events' disk as their storage.

It has been running well for a couple of weeks, and I could see the disk filling as expected - however earlier today I spotted the disk was completely full and so had to delete events from the GUI. Separately I've updated the 'PurgeWhenFull' filter to pick up events from the new location so all works as expected.

Only minor issue I've seen is that the log is now full of warnings from the zmfilter.pl file :

DiskSpace: Event does not exist at /home/events/3/2020-04-27/10355:ZoneMinder::Event: AlarmFrames => 7 AvgScore => 50 Cause => Linked DefaultVideo => 10355-video.mp4 EndTime => 2020-04-27 15:57:26 Frames => 107 Height => 1536 Id => 10355 Length => 17.61 MaxScore => 50 MonitorId => 3 Name => Event- 10355 Notes => Linked: BackGarden_Shed Orientation => ROTATE_0 SaveJPEGs => 3 Scheme => Medium StartTime => 2020-04-27 15:57:09 StateId => 1 StorageId => 2 TotScore => 350 Width => 2048

I'm not sure how this has happened - I assume there are entries still in the Database - is there a way to remove these 'orphan' events ?

zmaudit.pl will delete them.

OK, still seems to be a problem :

2020-04-28 20:17:24 zmfilter_2 15983 WAR DiskSpace: Event does not exist at /home/events/3/2020-04-27/10355:ZoneMinder::Event: AlarmFrames => 7 AvgScore => 50 Cause => Linked DefaultVideo => 10355-video.mp4 EndTime => 2020-04-27 15:57:26 Frames => 107 Height => 1536 Id => 10355 Length => 17.61 MaxScore => 50 MonitorId => 3 Name => Event- 10355 Notes => Linked: BackGarden_Shed Orientation => ROTATE_0 SaveJPEGs => 3 Scheme => Medium StartTime => 2020-04-27 15:57:09 StateId => 1 StorageId => 2 TotScore => 350 Width => 2048 zmfilt

Is there a way I can force a clean up?

OK, just in case anyone else trips over this, this is resolved - reviewing the logs the two things I did :

1. A number of my monitors were linked. I removed the linkages in case they were referring across between events ( that had since been deleted on the 'other' monitor ) hence triggering the errors

2. Looking at the logs, there appeared to be an issue with the 'Update Disk Space' Filter. Running it to show the events returned gave me some results unexpectedly. I then deleted these specifically.

Logs now clean.