ZoneMinder Forums

This is more of a FYI. Ubuntu 22.04.02. As part of Canonical's standard updates a firmware update as also done. In order for the the firmware update to take effect the system needed to be restarted. Shut down Zoneminder normally waited for activity to stop, rebooted and after the restart all of the archives were deleted. Lost three weeks of archives. I checked the disks and sure enough all of the archives are deleted. All archive data is stored two individual drives dedicated solely to Zoneminder. Both drives were cleared. I have a backup server that runs Ubuntu 20.04.06 and it does not appear to be affected. Before the update the 22.04 system was running great. The 22.04 system is starting over using the same storage method. The 20.04 system also uses the same storage method one drive dedicated to two cameras, four cameras total, so two drives. This is the second time this has happened on the 22.04 system. Logs are cleared on a daily basis since the non increasing dts, and decompression messages fill up the queue daily. This appears to be isolated to Ubuntu 22.04 only.

And maybe only 1.36 -
And maybe only if you shutdown zm first - yeah that doesn't make any sense either.
Anyway, I just upgraded my 22.04 system running 1.37 and it went fine. I do not shutdown zm for upgrades - I let the system do it.

You used the term archives but it seems you refer to all recordings?

All events stored on the HD's were deleted. I normally shut down ZM before a reboot to prevent orphan events. If one just restarts with ZM running you get orphaned events and the audit has to clean it up. I just discovered the event counter was not reset. I scanned some Ubuntu logs to find out what deleted the events, but so far I have not found anything.

We may need a judge to rule on this, but the shutdown of the system sends a normal shutdown request to ZM. I do not think they are different other than the user doing 2 things instead of 1. This user is super lazy...

Who? US?

There are only two things that can delete events, a filter and zmaudit. zmaudit shouldn't be running so make sure that's turned off.

Turn on debugging and see what is logged in the fitlers. Also maybe post screen shots of your filters for us to see.

I suspect a counter was reset to zero, but I'm unsure what counter since events continued to the next sequential number.
This is only on Ubuntu 22.04 BTW, 20.04 is working as planned. Zmstorage and Zmstoragec are the disks used for events. Unable to post print screens since the board does not accept graphic content.

Filters:

These delete old events when disk is > 92%, both Run in Background, Delete All Matches
1 PurgeWhenFull2*: Disk Percent > 92, AND Storage Area = Zmstoragec, Sort by ID, Asc, Limit to first 100,
3 PurgeWhenFull2*: Disk Percent > 92, AND Storage Area = Zmstorage, Sort by ID, Asc, Limit to first 100

These clean up orphaned directories. both Run in Background, Delete All Matches, Update used disk space.
5 cleanup2*: Exists In File System = False AND Storage Area = Zmstorage
4 cleanup2*: Exists In File System = False AND Storage Area = Zmstoragec

This updates disk space.
2 Update DiskSPACE*: Event Disk Space = NULL AND End Date/Time is not NULL

The forum does accept pictures.

Let me clarify.

The server running ZM is not used for the internet except for updates. All this server does is run ZM and check for updates. I have to move debug files and other info to this workstation. Attachments only accept .TXT.