Loading...

Knowledge Center


How to enable Orion debug logging for the Application Control and Change Control (Solidcore) extension
Technical Articles ID:   KB81604
Last Modified:  4/9/2017
Rated:


Environment

McAfee Application Control (MAC) 6.x
McAfee Change Control (MCC) 6.x
McAfee ePolicy Orchestrator (ePO) 5.x, 4.x

Summary

You can configure the ePO orion.log to receive verbose debug output for issues occurring with the Application Control and Change Control (Solidcore) extension. Use debug logging only to troubleshoot existing extension issues and disable it after you obtain the debug logs.

Solution

The ePO Application Server (Tomcat) log file sends information to the common orion.log file. By default, the log is located in c:\Program Files\McAfee\ePolicy Orchestrator\Server\Logs.

You can configure the file output debug level in the log configuration file. This file is located in c:\Program Files\McAfee\ePolicy Orchestrator\Server\conf\orion\log-config.xml.

You can change the warn default log level, identified in the <root> tag, to debug in the log-config.xml file.

Example:

<root>
<priority value ="warn" />
<appender-ref ref="ROLLING" />
<appender-ref ref="STDOUT"/>
</root>

The valid logging levels in increasing level of verbosity are:

  • info
  • warn
  • error
  • debug

If you change the <root> tag, it changes the default log level for all modules running on the Tomcat server. However, this is likely to be very verbose.

Alternatively, you can increase logging specifically for the Application Control and Change Control extension module by adding a <logger> section in the log-config.xml file. For example, to enable debug logging on the Application Control and Change Control extension classes, the <logger> section would look like:

<logger name="com.mcafee.scor">
      <level value="debug" />
</logger>


Restart the Tomcat (ePO Application Server) Service
Technical Support recommends that you use the following procedure to automatically restart the service. However, debugging is enabled (after editing log-config.xml) within five minutes by default, even without restarting this service. Restarting the service automatically adjusts the log level.

  1. Click StartRun, type services.msc, and click OK.
  2. Right-click the following service and select Restart:

    McAfee ePolicy Orchestrator Application Server
     
  3. Close the services window.
     

Solution

Other ePO debug log setting values are located in the registry as follows:
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator]

LogLevel – REG_DWORD  (8 – verbose)
LogSize – REG_DWORD  (10 – 10MB)
 
The following registry values save debug files to the ePolicy Orchestrator\DB\Debug\ folder:

 

SaveAgentPolicy – REG_DWORD (0=off, 1=on)
SaveAgentProps – REG_DWORD  (0=off, 1=on)
CreateCrashDump – REG_DWORD  (0=off, 1=on)

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Languages:

This article is available in the following languages:

English United States
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.