Table of Contents
Advertisement
Troubleshooting with Log Files
Adjusting the Tomcat log level
Log file name
UPDATERUI_<SYSTEM>.LOG
Adjusting the Tomcat log level
The file name of the Tomcat log is ORION.LOG. To adjust its logging level, do the following.
Task
1
Open the LOG-CONFIG.XML file, located at:
C:\PROGRAMFILES>\McAfee\ePolicyOrchestrator\Server\conf\orion
2
In the following line of text, replace "warn" with "info" or "debug": <root><priority value
="warn"/><appender-ref ref="ROLLING" /><appender-ref ref="STDOUT/></root>
3
Save and close the file.
Tomcat automatically adjusts the log level when the service is restarted.
Logging agent updating and deployment scripts
The agent uses MCSCRIPT.LOG to report script commands used during updating and deployment.
To enable, set the following DWORD value on the client's registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES\TVD\SHARED
COMPONENTS\FRAMEWORK\DWDEBUGSCRIPT=2
McAfee recommends that you delete this key when you are done troubleshooting.
Troubleshooting policy updates
To troubleshoot incremental policy update issues from the server-side, do the following:
Task
1
Create the DWORD registry value
HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES\EPOLICY
ORCHESTRATOR.
2
Restart all ePolicy Orchestrator services.
Detailed descriptions of failures, including source files and line numbers, appear in the
application log for the component experiencing issues. The ePolicy Orchestrator server
creates the file <AGENTGUID>-<TIMESTAMP>.XML at <INSTALLATION PATH>\DB\DEBUG,
which contains a copy of the content that the server deployed.In the following line of text,
replace "warn" with "info" or "debug".
3
Save and close the file.
Using Log Files for Troubleshooting in ePolicy Orchestrator 4.0
Setting change takes effect...
Within one minute
in
SAVEAGENTPOLICY = 1
11
Advertisement
Table of Contents
Troubleshooting
