Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Debugging the InterScan Messaging Virtual Appliance (IMSVA) application

    • Updated:
    • 14 Oct 2015
    • Product/Version:
    • InterScan Messaging Security Virtual Appliance 9.0
    • Platform:
    • N/A N/A
Summary

This article provides the steps on how you can debug IMSVA.

When troubleshooting an issue reported in the IMSVA, one of the items needed to be done is to debug and collect the logs for analysis. Since there is no feature to export debugging files, generating the debug logs can be done via the options in this article.

Details
Public

Option 1: Debugging via IMSVA management console

  1. Log on to the IMSVA management console.
  2. Go to Logs > Settings.
  3. Select Debug under Log Files.
  4. Click Save.
  5. To populate the logs accordingly, proceed in replicating the issue.

    For additional information, below is an explanation for each of the Log Level selection.

    Select one of the following Application log detail level:

    • Normal - The standard level of detail. This level provides the basic information needed by an administrator for daily monitoring and maintenance.
    • Detailed - A high level of detail. All IMSVA processes write detailed information to the logs, including telnet session information, the policy matched, the filter executed, and the action taken.
    • Diagnostic - Comprehensive information on each event or action. Diagnostic level logs include all information from the detailed level, plus SMTP routing information, and the route match information that determined which policy was applied.
    • Debug - The most complete and verbose level of detail. Debug logs are only recommended when troubleshooting.

Option 2: Debugging via the IMSVA configuration file

 
Make a backup of the imss.ini file since this procedure will require modification of the configuration file.
  1. Log on to the IMSVA machine as root or superuser.
  2. Go to the $IMSS_HOME$/config/ folder and then open the imss.ini file using a text editor.
  3. Look for the [general] section and change the "log_level" parameter to "debug".
  4. Save and close the file.
  5. Restart the imssd services using this command:
    $IMSS_HOME/script/S99IMSS restart
 
Diagnostic or debug logs may consume excessive IMSVA resources and can lower system performance. Therefore, after debugging is complete, you need to revert back to the previous settings.
In addition, the debug-level output is written into the standard IMSS log file, log.imss..in the/log directory.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1057052
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.