What to Do If the Hard Size Limit of the Log Viewer Database Is Reached

The Log Viewer database has an internal size limit to prevent uncontrolled growth that could lead to a full hard drive. There are two size limits, which are handled differently once reached. First, the soft size limit serves as a functional size limitation, where upon reaching this limit, the Log Viewer repository will try to prune older logs so it can replace them with the new incoming logs. When the soft limit is reached, the database may further grow in size. Second, the hard size limit serves as a security guarantee that the Log Viewer database won’t be larger than this limit. Upon reaching the hard limit, the Log Viewer will not store any more logs. Note that the final size may not be exactly the limit but a couple of MBs larger.

The fact that the hard size limit has been reached will be reported in the textual log file of the Service Utility: "Hard limit of the size of the database has been reached. Current size: … bytes. Limit: … bytes. No further logs will be accepted. Please consult the documentation for further steps."

There are two ways of resolving the situation where the Log Viewer is not accepting any more logs because the hard size limit has been reached.

Force Prune Older Executions

This property is documented here: Manta Log Viewer

Delete Database Files

This is a much faster way of handling this if you want to prune everything from the Log Viewer database.

1. Close the application or stop the Service Utility service.

2. Navigate to the mantaflow/serviceutility/manta-admin-ui-dir/data folder.

3. Remove all the following files.

   • manta_logs.h2.db

   • manta_logs.h2.db.*.part

   • manta_logs.trace.db

   • manta_logs.lock.db (if present)

4. Restart the application or stop the Service Utility service. A new empty Log Viewer database will be created upon start up.