Debugging Endpoint Protection Manager

Products

• Endpoint Protection

Issue/Introduction

Use the steps in these documents to enable debug logging for the various components of Symantec Endpoint Protection Manager (SEPM). You can enable logging for all components of the manager, or just the specific components you need to.

Resolution

Enabling Tomcat server debugging

Tomcat server debug logs are needed to trace Symantec Endpoint Protection (SEP) service failures and crashes. They are also useful for debugging manager functions, like content distribution, or replication. For more information, see Enabling Tomcat server debugging for the Endpoint Protection Manager.

Enabling client-server communications (secreg and secars) debugging

Turn on secars and secreg debugging when troubleshooting problems with client-to-server communications, specifically when the problems are related to client registrations or heartbeats. For more information, see Enabling SECARS and SECREG debugging for Endpoint Protection Manager.

Enabling Apache server debugging

Apache server debug logs are needed to trace Symantec Endpoint Protection Webserver service failures/crashes. They are also useful for debugging content distribution from managers to their Symantec Endpoint Protection clients, client-to-server communications failures, or reporting server failures. For more information, see Enabling Apache server debugging for the Endpoint Protection Manager.

Enabling Cloud Bridge debugging

Cloud Bridge debugging is useful in troubleshooting issues with the 14.1, and newer, Cloud enrolled SEP Manager. For more information, see Enabling debug logging for Endpoint Protection Manager Cloud Bridge.

Enabling API service debugging

API service debugging is useful in troubleshooting issues with the 14.1 and newer SEP manager API calls. For more information, see Enable debug logging for Endpoint Protection Manager API Service