Question
How do I find debug logs for the Enterprise Agent?
Answer
Windows:
If the Agent won't install:
- Follow the steps for Manually Installing the Windows Enterprise Agent
- When entering the msiexec command to install the agent, add the following to the end of the command:
/lv "C:\AgentInstallLog.txt"
- Any errors encountering during installation will be found in C:\AgentInstallLog.txt
If the Agent won't start:
- Open a Command Prompt (as Administrator)
- Navigate to the Agent's installation folder (typically "C:\Program Files\AccessData\Agent")
- Run the following command:
agentcore.exe -d
- Any error with starting the agent will be output in the command prompt
If the Agent starts but encounters problems:
- Open services.msc (as Administrator)
- Stop "AgentService"
- Open Windows Explorer
- Navigate to the Agent's installation folder (typically "C:\Program Files\AccessData\Agent")
- Create a file called "debuglogs.txt" with following contents
loglevel=all
Note: "debuglogs.txt" can also be placed in each of the modules' folder to get module-specific logs - Start "AgentService"
- Debugging information should now be found in a file called "agent.log" in the Agent's installation directory
Linux:
Should you need to enable debug for the agent on a Linux system:
- Open Terminal (as root)
- Stop "agentcored" /etc/init.d/agentcored stop
- Navigate to the Agent's installation folder (typically "/usr/AccessData/agent")
- Create a file called "debuglogs.txt" with following contents
echo "loglevel=all" > debuglogs.txt
- Start "agentcored" /etc/init.d/agentcored start
- Debugging information should now be found in a file called "agent.log" in the Agent's installation directory
MacOS:
Indexing and Agent logs are found in /Library/AccessDataAgent/<version>/Logs.
Overview
Debug logs can be used to indicate why the Agent might not install or start, or any errors that occur while it's running.