User manual MCAFEE EPOLICY ORCHESTRATOR 4.0 LOG FILES FOR TROUBLESHOOTING

[. . . ] 12 Using Log Files for Troubleshooting in ePolicy Orchestrator 4. 0 3 Troubleshooting with Log Files ePolicy Orchestrator includes many log files that you can use for troubleshooting. This document describes how to use the log files and provides the following information: · Name and location of log files. · Typical issues requiring troubleshooting, and the log files likely to be helpful. [. . . ] The default location of the ePolicy Orchestrator 4. 0 server software is C:\PROGRAMFILES\MCAFEE\EPOLICY ORCHESTRATOR <INSTALLATION PATH> Log file size and BACKUP logs When a log file reaches it maximum size, BACKUP is added to the file name extension and a new log file is created. For example, when AGENT_<SYSTEM>. LOG reaches it maximum size, its name becomes AGENT_<SYSTEM>_BACKUP. LOG. Depending on how recently the BACKUP was created, it may contain current entries. To change the 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 desired. For example, 2=2MB. 6 Using Log Files for Troubleshooting in ePolicy Orchestrator 4. 0 Troubleshooting with Log Files Typical issues addressed by logs Typical issues addressed by logs Table 3 identifies the types of issues recorded in each ePolicy Orchestrator 4. 0 log file. Table 3: Typical issues and the log files to consult For issues with. . . Agent: in general; client communication tasks See these log files AGENT_<SYSTEM>. LOG, AGENT_<SYSTEM>_BACKUP. LOG FRMINST_<SYSTEM>. LOG EPOAPSVR. LOG UPDATERUI_<SYSTEM>. LOG EPOAPSVR. LOG SERVER. LOG SQL2K5bCINST. LOG Agent: installation; uninstallation Agent: push Agent: updating client, managed products Agent: wake-up Agent-server communication Backward Compatibility for SQL (if installed during ePolicy Orchestrator installation) Client tasks: communication AGENT_<SYSTEM>. LOG AGENT_<SYSTEM>_BACKUP. LOG PRDMGR_<SYSTEM>. LOG PRDMGR_<SYSTEM>_BACKUP. LOG PRDMGR_<SYSTEM>. LOG PRDMGR_<SYSTEM>_BACKUP. LOG, MCSCRIPT. LOG AGENT_<SYSTEM>. LOG, SERVER. LOG, SERVER_BACKUP. LOG REPLICATION. LOG, EPOAPSVR. LOG, ORION. LOG ERRORLOG. <CURRENT_DATETIME> STDERR. LOG, JAKARTA_SERVICE_<DATE>. LOG, LOCALHOST_ACCESS_LOG. <DATE>. TXT EVENTPARSER. LOG, EVENTPARSER_BACKUP. LOG CORE-INSTALL. LOG, ENV-CORE-INSTALL. LOG, EPO-INSTALL. LOG, ENV-TOMCAT-INSTALL. LOG EPO400COMMONSETUP. LOG EPO400-INSTALL-MSI. LOG ORION. LOG LICENSING. LOG MIGRATION. LOG, EPO400-INSTALL-MSI. LOG ORION. LOG PRDMGR_<SYSTEM>. LOG, PRDMGR_<SYSTEM>_BACKUP. LOG Client tasks: scripts Communication: client-server Distributed repositories Error: Apache web server Error: Tomcat servlet container Events, event update Installation: ePolicy Orchestrator calls to background, foundation, or other platforms and technologies Installation: ePolicy Orchestrator custom actions Installation: ePolicy Orchestrator Interface: Issues arising after changes to. . . License Migration: from earlier version Notifications Plug-in files Using Log Files for Troubleshooting in ePolicy Orchestrator 4. 0 7 Troubleshooting with Log Files Logging levels for debugging For issues with. . . Policies 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 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 Adjusting the Tomcat log level. 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. · When a setting is changed using the registry, the interval is usually a minute or less. The DWORD registry value that controls logging is: HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES\EPOLICY ORCHESTRATOR\LOGLEVEL. · When a setting is changed in an INI file or an XML file, the change usually takes effect immediately. · In some instances, when a change takes effect upon restarting the system, the user controls the interval. [. . . ] This utility is distributed with Microsoft Visual Studio Agent activity log The agent activity log (AGENT_<SYSTEM>. XML) contains copies of messages from the AGENT_<SYSTEM>. LOG, including translated messages, of types "e", "w", and "i", (corresponding to logging levels 1 ­ 3). This file is not intended for debugging, but as information for users not likely to be troubleshooting. Messages of type "x" (logging level 4) can be included in the activity log. [. . . ]