Trend Micro - Securing Your Journey to the Cloud Business
Success
Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Enabling or disabling debug logging in Vulnerability Protection Manager (VPM)

    • Updated:
    • 8 Apr 2020
    • Product/Version:
    • Vulnerability Protection 2.0
    • Platform:
    • Windows 2003 Server R2
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Server R2 Enterprise
    • Windows 2012 Server Essential R2
    • Windows 2012 Standard R2
Summary

You need to activate debug logs to generate more details in the logs when troubleshooting certain issues in VPM. This article shows you how to configure debug logging to help you resolve VPM issues. 

Details
Public

The server0.log file is the main log output for errors and activities in VPM. You can add specific debug logs in this file depending on the issue you are troubleshooting.

  1. Go to Services.
  2. Locate Vulnerability Protection Manager from the list, right-click on it and select Stop.
  3. Open Windows Explorer and go to %ProgramFiles%\Trend Micro\Vulnerability Protection Manager\jre\lib\.
  4. Modify the logging.properties file using Notepad and append the option on the file depending on what you need to debug. You can choose among the different debugging options listed below.

    For example, you want to generate debug logs for UI Related issues. At the end of the file, append “com.thirdbrigade.manager.webclient.screens.level=ALL”.

  5. Save the file.
  6. Start the VPM service.

Debugging options

 
All parameters are case-sensitive.
Option 1: UI Related Issues
  • com.thirdbrigade.manager.webclient.screens.level=ALL
Option 2: Configuration and Protocol Issues
  • com.thirdbrigade.manager.webclient.screens.level=ALL
  • com.thirdbrigade.manager.core.protocol.session.CommandProtocolSession.level=ALL
  • com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.HostUpdaterJob.level=ALL
Option 3: Scan Management Issues
  • com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.HostUpdaterCommand.level=ALL
  • com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.HostUpdaterCommandGetStatusEvents.level=ALL
  • com.thirdbrigade.manager.core.db.AgentEventPeer.level=ALL
Option 4: All screens, including Wizard-related Issues
  • com.thirdbrigade.manager.webclient.screens.level = ALL
Option 5: Database-related Issues
  • com.thirdbrigade.persistence1.level = ALL
Option 6: Startup Information Logging
  • com.thirdbrigade.manager.webclient.initialization.level = ALL
  • com.thirdbrigade.manager.core.Core = ALL
  • com.thirdbrigade.manager.core.security.ClientSecurityManager.level=ALL
Option 7: Host Updater Job (including the Agent Security Configuration XML) Debugging
  • com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.HostUpdaterJob.level=ALL
  • com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.HostUpdaterCommand.level=ALL
Option 8: Agent Communication Protocol Logging
  • com.thirdbrigade.manager.core.protocol.level = ALL
Option 9: Detection Engine (e.g. Recommendation Scans) Logging
  • com.thirdbrigade.manager.core.detectionengine.level=ALL
Option 10: Manager Job-related Issues
  • com.thirdbrigade.manager.core.scheduler.jobschedulers.HostJobScheduler.level=ALL
  • com.thirdbrigade.manager.core.scheduler.JobQueuingThread.level=ALL
  • com.thirdbrigade.manager.core.scheduler.JobCreationThread.level=ALL
  • com.thirdbrigade.manager.core.scheduler.ManagerJobs.level=ALL
Option 11: AD Synchronization Issues
  • com.thirdbrigade.manager.core.util.UserUtilities.level=ALL
Option 12: Dashboard Bean Performance Issues
  • com.thirdbrigade.manager.webclient.screens.DashboardBean.level=ALL
  • com.thirdbrigade.manager.webclient.ScreenServlet.level=ALL (to replace the preceding bullet)
Option 13: Active Update Issues
  • com.thirdbrigade.manager.core.au.level=ALL
  • com.thirdbrigade.manager.webclient.ActiveUpdateServlet.level=ALL
Option 14: Maintenance Job and Entity Purge-related Issues
  • com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.MaintenanceJob.level=ALL
  • com.thirdbrigade.manager.core.db.EntityPeer.level=ALL
Option 15: Enable ALL Logging on the manager
  • com.thirdbrigade.level = ALL

  1. Open Windows Explorer and go to %ProgramFiles%\Trend Micro\Vulnerability Protection Manager\jre\lib\logging.properties.
  2. Remove the debugging options added at the end of the logs.
  3. Restart VPM by going to Services, right-click the Vulnerability Protection Manager service and select Restart.
Premium
Internal
Partner
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1107707
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.
Related Articles