Question

How do I find debug logs for the Enterprise Agent?

 

Answer

Windows:

If the Agent won't install:

  1. Follow the steps for Manually Installing the Windows Enterprise Agent
  2. When entering the msiexec command to install the agent, add the following to the end of the command:
    /lv "C:\AgentInstallLog.txt"
  3. Any errors encountering during installation will be found in C:\AgentInstallLog.txt

 

If the Agent won't start:

  1. Open a Command Prompt (as Administrator)
  2. Navigate to the Agent's installation folder (typically "C:\Program Files\AccessData\Agent")
  3. Run the following command:
    agentcore.exe -d
  4. Any error with starting the agent will be output in the command prompt

 

If the Agent starts but encounters problems:

  1. Open services.msc (as Administrator)
  2. Stop "AgentService"
  3. Open Windows Explorer
  4. Navigate to the Agent's installation folder (typically "C:\Program Files\AccessData\Agent")
  5. 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
  6. Start "AgentService"
  7. 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:

  1. Open Terminal (as root)
  2. Stop "agentcored" /etc/init.d/agentcored stop
  3. Navigate to the Agent's installation folder (typically "/usr/AccessData/agent")
  4. Create a file called "debuglogs.txt" with following contents 
    echo "loglevel=all" > debuglogs.txt
  5. Start "agentcored" /etc/init.d/agentcored start
  6. 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//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.