1. Open Windows Explorer and navigate to <ePO_Install_folder>\Server\conf\orion.
2. Right-click LOG-CONFIG.XML and click Edit to open the file in Notepad.
3. Scroll down to the bottom of the file and locate the following section:
   
   -->
       <root>
            <priority value ="warn" />
            <appender-ref ref="ROLLING" />
            <appender-ref ref="STDOUT"/>
       </root> 
    
4. Change <priority value ="warn" /> to <priority value ="debug" />.
    
   NOTE: If needed, you can adjust the size of Orion.log by following steps 5 and 6. Skip to step 7 to retain the default size.
    
5. Locate the appropriate line by searching for the term MaxFileSize.
6. Change <param name="MaxFileSize" value="2MB"/> to <param name="MaxFileSize" value="20MB"/>.
    
   NOTE: You can set a smaller or higher value, for example 10 MB or 80 MB, if needed.
    
7. Click File, Save.
8. Click File, Close.
    

Restart the Tomcat (ePO Application Server) service
McAfee recommends that you use the following procedure to automatically restart the service. But, note that after editing LOG-CONFIG.XML, debugging is enabled within a few minutes by default, even without restarting this service. Restarting the service automatically adjusts the log level.

1. Click Start, Run, type services.msc, and then click OK.
2. Right-click on either of the following services and select Restart:
   
   McAfee ePolicy Orchestrator x.x Application Server

3. Close the services window.
4. The Orion.log file is created in the Server\logs folder.

 

1. Open Windows Explorer and navigate to <ePO_Install_Folder>\Server\conf\orion.
2. Right-click LOG-CONFIG.XML and click Edit to open the file in Notepad.
3. Scroll down to the bottom of the file and locate the following section:
   
   -->
       <root>
            <priority value ="warn" />
            <appender-ref ref="ROLLING" />
            <appender-ref ref="STDOUT"/>
       </root> 
    
4. Change <priority value ="debug" /> to <priority value ="warn" />.
5. Locate the appropriate line by searching for the term MaxFileSize.
6. Change <param name="MaxFileSize" value="20MB"/> to <param name="MaxFileSize" value="2MB"/>.
7. Click File, Save.
8. Click File, Close.
9. Restart the Tomcat (ePO Application Server) service, using the previous procedure. 
   
   NOTE: After editing LOG-CONFIG.XML, the changes take effect within few minutes by default, even without restarting this service.

A new user-friendly graphical interface has been introduced in ePO 5.10 Update 5 and later. It can be used to modify the log-config.xml, as explained above,

To access the interface, navigate to the below URL on your ePO server:
 

• lcalhost - Can be the name as your ePO server,
• Port 8443 - Is the default tomcat port, adjust the port to your own environment

NOTES:

• The above URL requires ePO administrative credentials. If a user without administrator rights tries to log on, a message is displayed: "Only administrators can access this page"
• After the user authenticates, a set of loggers is displayed. Some of them are ON by default. Others are set to OFF by default. Some of the loggers are meant to be OFF by default, and must not be turned on, unless specified by Technical Support. Turning on the loggers for an indefinite period, can lead to performance issues on your ePO server. Issues similar to the ones described in KB86593 - Performance issues on ePO 5.x when debug logging is enabled.
• After you edit LOG-CONFIG.XML via the user interface, the changes take effect within minutes by default, even without restarting this service.

Technical support might provide you specific loggers to debug different extensions. You can debug by clicking the '+' symbol, and adding the logger provided by support.