McAfee EPOLICY ORCHESTRATOR 4.0 - LOG FILES FOR Troubleshooting Manual
McAfee EPOLICY ORCHESTRATOR 4.0 - LOG FILES FOR Troubleshooting Manual

McAfee EPOLICY ORCHESTRATOR 4.0 - LOG FILES FOR Troubleshooting Manual

Using log files for troubleshooting guide

Advertisement

Using Log Files for Troubleshooting in
ePolicy Orchestrator 4.0
Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EPOLICY ORCHESTRATOR 4.0 - LOG FILES FOR and is the answer not in the manual?

Questions and answers

Summary of Contents for McAfee EPOLICY ORCHESTRATOR 4.0 - LOG FILES FOR

  • Page 1 Using Log Files for Troubleshooting in ePolicy Orchestrator 4.0 Guide...
  • Page 2 SITEADVISOR, THREATSCAN, TOTAL PROTECTION, VIREX, VIRUSSCAN, WEBSHIELD are registered trademarks or trademarks of McAfee, Inc. and/or its affiliates in the US and/or other countries. McAfee Red in connection with security is distinctive of McAfee brand products. All other registered and unregistered trademarks herein are the sole property of their respective owners.
  • Page 3: Table Of Contents

    Contents Troubleshooting with Log Files ............Log file names and locations.
  • Page 4: Troubleshooting With Log Files

    • Setting the size of log files and the depth and scope of logging. • When changes to logging settings take effect. • Types of log files: McAfee Agent log files and ePolicy Orchestrator log files. Five of the files are associated with the McAfee Agent: AGENT_<SYSTEM>.LOG...
  • Page 5: Log File Names And Locations

    EPOAPSVR.LOG <INSTALLATION PATH>\DB\LOGS EPO400COMMONSETUP.LOG <CURRENT USER’S TEMP DIRECTORY>\NAILOGS EPO-INSTALL.LOG <CURRENT USER’S TEMP DIRECTORY>\NAILOGS\MERCURY FRAMEWORK EPO400-INSTALL-MSI.LOG <CURRENT USER’S TEMP DIRECTORY>\NAILOGS ERRORLOG.<CURRENT_DATETIME> <INSTALLATION PATH>\MCAFEE\APACHE2\LOGS EVENTPARSER.LOG, EVENTPARSER_BACKUP.LOG <INSTALLATION PATH>\DB\LOGS FRMINST_<SYSTEM>.LOG C:\WINDOWS\NAILOGS or C:\WINDOWS\TEMP\NAILOGS or C:\DOCUMENTS AND SETTINGS\<CURRENT USER\LOCAL SETTINGS\TEMP\NAILOGS JAKARTA_SERVICE_<DATE>.LOG PROGRAMFILES\MCAFEE\EPOLICY ORCHESTRATOR\SERVER\LOGS LICENSING.LOG <CURRENT USER’S TEMP DIRECTORY>\NAILOGS...
  • Page 6 Open text box, and click OK. <INSTALLATION PATH> The default location of the ePolicy Orchestrator 4.0 server software is C:\PROGRAMFILES\MCAFEE\EPOLICY ORCHESTRATOR 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.
  • Page 7: Typical Issues Addressed By Logs

    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... See these log files Agent: in general;...
  • Page 8: Logging Levels For Debugging

    Troubleshooting with Log Files Logging levels for debugging For issues with... See these log files Policies AGENT_<SYSTEM>.LOG, AGENT_<SYSTEM>_BACKUP.LOG, SERVER.LOG Policy update <AGENTGUID>-<TIMESTAMP>.XML (if registry value has been set) Product property update SERVER.LOG Pull EPOAPSVR.LOG, ORION.LOG, REPLICATION.LOG Push agent EPOAPSVR.LOG Replicate EPOAPSVR.LOG, ORION.LOG, REPLICATION.LOG Script: client task AGENT_<SYSTEM>.LOG...
  • Page 9 DWORD registry value at: HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES\EPOLICY ORCHESTRATOR\LOGLEVEL FRMINST_<SYSTEM>.LOG DWORD registry value at: HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES\EPOLICY ORCHESTRATOR\LOGLEVEL ORION.LOG C:\PROGRAMFILES\MCAFEE\EPOLICY ORCHESTRATOR\SERVER\CONF\ORION \LOG-CONFIG.XML. See “MaxFileSize” parameter value in “Rolling log file” section. See also Priority Value in <root> section. PRDMGR_<SYSTEM>.LOG DWORD registry value at: HKEY_LOCAL_MACHINE\SOFTWARE\NETWORK ASSOCIATES\EPOLICY ORCHESTRATOR\LOGLEVEL SERVER.LOG...
  • Page 10: When Setting Changes Take Effect

    Troubleshooting with Log Files When setting changes take effect When setting changes take effect This section defines the interval between the moment that a log file setting is changed and the moment the change takes effect. • 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.
  • Page 11: Adjusting The Tomcat Log Level

    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:...
  • Page 12: Interpreting Windows Error Codes

    Troubleshooting with Log Files Interpreting Windows error codes Interpreting Windows error codes To understand Windows error messages, identify the error code and look it up in the MSDN library. Locate messages of type e or E in the log file. Identify the time that the problem occurred, if known.

This manual is also suitable for:

Epolicy orchestrator 4.0

Table of Contents