Logging Levels For Debugging - McAfee EPOLICY ORCHESTRATOR 4.0 - LOG FILES FOR Troubleshooting Manual

Using log files for troubleshooting guide
Table of Contents

Advertisement

Troubleshooting with Log Files

Logging levels for debugging

For issues with...
Policies
Policy update
Product property update
Pull
Push agent
Replicate
Script: client task
Scripts: engine; messages
Server: in general
Server: installation
Updating
Upgrading: from earlier version
User interface:
HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK
ASSOCIATES\EPOLICY ORCHESTRATOR, issues arising
after changes to...
Logging levels for debugging
This section provides information about setting logging levels for logs in general. For information
about adjusting the logging of the Tomcat servlet container, see
The scope and depth of the information in most log files are determined by the log level, a
value ranging from 1 to 8.
• Messages logged at each level include all messages at the current level and all lower logging
levels.
• The default value is 7, generally considered adequate for ordinary debugging.
• Log level 8 produces output, including every SQL query, whether or not there is an error.
Log level 8 also provides communication details for troubleshooting network and proxy server
issues.
8
Using Log Files for Troubleshooting in ePolicy Orchestrator 4.0
See these log files
AGENT_<SYSTEM>.LOG,
AGENT_<SYSTEM>_BACKUP.LOG, SERVER.LOG
<AGENTGUID>-<TIMESTAMP>.XML (if registry value
has been set)
SERVER.LOG
EPOAPSVR.LOG, ORION.LOG, REPLICATION.LOG
EPOAPSVR.LOG
EPOAPSVR.LOG, ORION.LOG, REPLICATION.LOG
AGENT_<SYSTEM>.LOG
MCSCRIPT.LOG
SERVER.LOG, SERVER_BACKUP.LOG, ORION.LOG
EPO400COMMONSETUP.LOG, EPO400-INSTALL-MSI.LOG
AGENT_<SYSTEM>.LOG,
AGENT_<SYSTEM>_BACKUP.LOG
UPDATERUI_<SYSTEM>.LOG
<AGENTGUID>-<TIMESTAMP>.XML (if registry value
has been set)
MIGRATION.LOG, EPO400-INSTALL-MSI.LOG
ORION.LOG
Adjusting the Tomcat log
level.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Epolicy orchestrator 4.0

Table of Contents