Technical Support may request debug-level log files when troubleshooting an issue:
- Default logging has a value of 1
- Debug-level logging requires a value of 2
Debug logging produces more log entries about all MA activity, regardless of whether there's an error. Debug logging provides all communication details needed to troubleshoot common issues, for example:
- Communication failures
- Update failures
- Policy management issues
Guidance for enabling debug logging on non-Windows is as follows:
- It's important to enable debug logging before you try to reproduce a problem. Enabling debug logging for an issue that can't be reproduced doesn't provide adequate information for troubleshooting.
- If client and server issues are being investigated, you must enable debug logging on the client, and log level 8 on the ePO server, before you try to reproduce the problem. These actions are needed to successfully capture the additional logging that's needed to help investigate the issue.
- The software IDs for MA for non-Windows are platform-specific.
McAfee Agent 5.x
Log levels are set using the
maconfig command.
Maconfig is located in one of the following places:
| Non-Windows platform |
Fixed path to maconfig |
| Linux |
/opt/McAfee/agent/bin/ |
| macOS |
/Library/McAfee/agent/bin/ |
To enable debugging on Agents 5.x, run
maconfig with the following command:
maconfig -enforce -loglevel XX
Here,
XX is the needed log level.
The log levels correspond to the following:
| Info |
1 |
Info message is mostly localized |
| Debug |
2 |
Debug logs for all components |
| Detail |
3 |
Extra trace logs for some components |
Example command:
maconfig -enforce -loglevel 2
- Restart the MA process. (This step is needed to enable debug logging on non-Windows.)
- For AIX and HP-UX agents, type the following command and press Enter:
/sbin/init.d/cma restart
- For Linux and Solaris agents, type the following command and press Enter:
/etc/init.d/cma restart
- For Mac agents, type the following command and press Enter:
SystemStarter restart cma
- Fully replicate the issue and capture information in the logs.
- Reset the logging level.
IMPORTANT: Follow the procedure in Step 1. Then, reset the logging level back to 1 after you've successfully replicated the issue and collected the logs. This reset avoids the generation of excessively large log files.
