Enabling debug logging level on MetaDefender Core should only be used when absolutely necessary, and advised by the OPSWAT team.
Letting MeteDefender Core operate for a long time under debug logging mode will likely cause performance degradation, out of disk space, and possibly an IO bottleneck issue on the system.
Tips: We should only enable the debug logging level when:
- We already know the steps to reproduce or trigger the issue symptom.
- Or, we already know the issue will very likely come back very soon.
- Or, the OPSWAT team checked and confirmed there should be more useful information tracked with the debug log and relevant to the issue.
To provide debug logs for the OPSWAT support team, the level of the logfile for the given service ometascan must be set to
debug(see how at How to enable debug logging for MetaDefender Core).Execute the scenarios requested by the support team
Collect the generated log files by following the steps at
After collecting the debug logs, the log level should be set back to
info, as the size of the logfile will increase significantly in debug mode.
For information on how to interpret the log files, consult: Log Message Format
If Further Assistance is required, please proceed to log a support case or chat with one of our support engineers.
