Professional Documents
Culture Documents
Epo 510 RG Log Files 0-00 En-Us
Epo 510 RG Log Files 0-00 En-Us
Installer logs Include details about installation path, user credentials, database used, and
communication ports configured.
Server logs Include details about server functionality, client event history, and administrator
services.
Agent logs Include details about agent installation, wakeup calls, updating, and policy
enforcement.
Variable Description
[Agent DATA To determine the actual location of the agent data files, view this registry key
Path] HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES\TVD\SHARED COMPONENTS
\FRAMEWORK\DATA PATH. For more information, see Agent installation directory in
the ePolicy Orchestrator Product Guide or Help.
%temp% This is the Temp folder of the currently logged on user. To access this folder, select
Start | Run, then type %temp% in the Open text box, and click OK.
[InstallDir] The default location of the ePolicy Orchestrator server software is C:\PROGRAM
FILES\MCAFEE\EPOLICY ORCHESTRATOR.
1
Installer logs
Installer log files list details about the ePolicy Orchestrator installation process.
These logs provide information about:
2
File name Log type Location Description
EPO500InstallMSI.log Installation %temp%\McAfeeLogs The primary ePolicy Orchestrator
installation log. Contains installation
details such as installer actions and
installation failures.
<ExtensionFileName> Temporary %temp%\McAfeeLogs Created by the ePolicy Orchestrator
.cmd \ePO500 installer. Contains the command
troubleshoot (sent to RemoteClient) to check in
\OutputFiles extensions.
Server logs
Server log files contain details on server functionality and various administrator services used by
ePolicy Orchestrator.
Localhost Tomcat [InstallDir] Records all McAfee ePO server requests received
_access_log \Server\logs * from client systems.
.<DATE>.txt
This file is not present until after the initial
Tomcat service startup.
3
File name Log type Location Description
Orion.log Primary [InstallDir] Contains McAfee Foundation Services platform
\Server\logs * details and all extensions loaded by default.
Replication Server [InstallDir]\DB The McAfee ePO server replication log file. This
.log \Logs file is only generated when all these are true:
There are distributed repositories.
A replication task has been configured.
A replication task has run.
4
Agent logs
Agent log files contain actions triggered or taken by the McAfee Agent.
Agent_<system> Agent [Agent DATA Generated on client systems when the server
.log Path]\DB deploys an agent to them. This file contains details
related to:
Agent-server communication
Policy enforcement
Other agent tasks
MCScript.log Agent [Agent DATA Contains the results of script commands used
Debug Path]\DB during agent deployment and updating. To enable
the DEBUG mode for this log, set this DWORD
value on the clients registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK
ASSOCIATES\TVD\SHARED COMPONENTS\FRAMEWORK
\DWDEBUGSCRIPT=2
MfeAgent.MSI Agent %temp% Contains details about the MSI installation of the
.<DATE>.log \McAfeeLogs agent.
PrdMgr_<SYSTEM> Agent [Agent DATA Contains details about agent communications with
.log Path]\DB other McAfee products.
UpdaterUI Agent %temp% Contains details of the updates to managed
_<system>.log \McAfeeLogs products on the client system.
5
McAfee Agent error logs
When the McAfee Agent traps errors, they are reported in Agent error logs. Agent error logs are
named for their primary log counterpart. For example, when errors occur while performing client
tasks, the MCScript_Error.log file is created. Error logs contain only details about errors.
To change the log size, create the DWORD value LOGSIZE in the registry key HKEY_LOCAL_MACHINE
\Software\Network Associates\ePolicy Orchestrator, then set the value data to the size wanted.
For example, 20=20MB.
Task
1 From [ePOInstallDir]\Apache2\conf, open the httpd.conf file.
CustomLog "|C:/PROGRA~1/McAfee/EPOLIC~1/Apache2/bin/rotatelogs.exe
-l C:/PROGRA~1/McAfee/EPOLIC~1/Apache2/logs/accesslog.%Y-%m-%d 86400" common
This file path applies to the default ePolicy Orchestrator installation. For custom installations, use the
path specified in the httpd.conf file.
Messages logged at each level include all messages at the current level and all lower logging levels.
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.
6
Messages reported at each log level
Location of values controlling log levels and when they take effect
7
Log file name Log level value location Update duration
Replication.log Not applicable Not applicable
Server.log DWORD registry value at: HKEY_LOCAL_MACHINE Upon startup of ePolicy
\SOFTWARE\NETWORK ASSOCIATES\EPOLICY Orchestrator Server
ORCHESTRATOR\LOGLEVEL service.
Stderr.log Not applicable Not applicable
UpdaterUI_<SYSTEM> DWORD registry value at: HKEY_LOCAL_MACHINE 1 minute (approximate)
.log \SOFTWARE\NETWORK ASSOCIATES\EPOLICY
ORCHESTRATOR\LOGLEVEL
If you enable remote access to the agent activity log file, you can also view the agent debug log files
remotely by clicking View debug log (current or previous) in the header of the Show Agent Log display. For
instructions, see Agent Activity Logs and Viewing the agent activity log in the McAfee ePolicy
Orchestrator Product Guide or Help.
Task
1 Using a text editor, open the LogConfig.xml file, located at:
C:\PROGRAMFILES\McAfee\ePolicyOrchestrator\Server\conf\orion
Use debug only when troubleshooting for a short time. Setting the priority value to debug causes
the old log files to be deleted frequently.
Tomcat automatically adjusts the log level when the ePolicy Orchestrator Application Server services
restart.
8
Troubleshoot product issues
Use logs to troubleshoot product issues.
Tasks
Troubleshoot policy updates on page 9
Troubleshoot incremental policy update issues from the server-side.
Interpret Windows error codes on page 9
To understand Windows error messages, identify the error code and look it up in the MSDN
library.
Task
1 Create the DWORD registry value SAVEAGENTPOLICY = 1 in:
HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES\EPOLICY ORCHESTRATOR
Task
1 Locate messages of type e or E in the log file.
3 Note the Windows error code associated with the problem event.
You can also use the ERRLOOK.EXE utility to determine the cause of these error codes. This utility is
distributed with Microsoft Visual Studio.
9
Copyright 2013 McAfee, Inc. Do not copy without permission.
McAfee and the McAfee logo are trademarks or registered trademarks of McAfee, Inc. or its subsidiaries in the United States and
other countries. Other names and brands may be claimed as the property of others.
10 0-00