Why is the analyzed zip file very large and invalid after running the vacuum tool?

Issue: The analyzed zip file became very big (i.e 2GB+) and invalid after running the vacuum tool “ometascan-vacuum-db.exe”. The log shows:

Running vacuum DONE QProcess: Destroyed while process (“C:\\Program Files\\OPSWAT\\MetaDefender Core\\7z.exe”) is still running.

Possible causes:

When compressing the vacuum output, the compress task compresses all the Postgres log, vacuum log, and vacuum output. It’s possible that the Postgres log files are too large due to database corruption. As a result, the analyzed zip file becomes big. The compression process needs more time to compress the files. The process timed out and was killed while running, resulting in an invalid zip file.

Solution:

Check the Postgres logs to confirm the size of postgres logs and delete/move those postgres logs to free up space.