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.
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.
- Go to Services.
- Locate Vulnerability Protection Manager from the list, right-click on it and select Stop.
- Open Windows Explorer and go to %ProgramFiles%\Trend Micro\Vulnerability Protection Manager\jre\lib\.
- 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”.
- Save the file.
- Start the VPM service.
Debugging options
- com.thirdbrigade.manager.webclient.screens.level=ALL
- 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
- 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
- com.thirdbrigade.manager.webclient.screens.level = ALL
- com.thirdbrigade.persistence1.level = ALL
- com.thirdbrigade.manager.webclient.initialization.level = ALL
- com.thirdbrigade.manager.core.Core = ALL
- com.thirdbrigade.manager.core.security.ClientSecurityManager.level=ALL
- com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.HostUpdaterJob.level=ALL
- com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.HostUpdaterCommand.level=ALL
- com.thirdbrigade.manager.core.protocol.level = ALL
- com.thirdbrigade.manager.core.detectionengine.level=ALL
- 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
- com.thirdbrigade.manager.core.util.UserUtilities.level=ALL
- com.thirdbrigade.manager.webclient.screens.DashboardBean.level=ALL
- com.thirdbrigade.manager.webclient.ScreenServlet.level=ALL (to replace the preceding bullet)
- com.thirdbrigade.manager.core.au.level=ALL
- com.thirdbrigade.manager.webclient.ActiveUpdateServlet.level=ALL
- com.thirdbrigade.manager.core.scheduler.jobschedulers.jobs.MaintenanceJob.level=ALL
- com.thirdbrigade.manager.core.db.EntityPeer.level=ALL
- com.thirdbrigade.level = ALL
- Open Windows Explorer and go to %ProgramFiles%\Trend Micro\Vulnerability Protection Manager\jre\lib\logging.properties.
- Remove the debugging options added at the end of the logs.
- Restart VPM by going to Services, right-click the Vulnerability Protection Manager service and select Restart.