Troubleshooting Private Agent Not Running or Is Stopped or Unreachable

The “Agent Not Running or Unreachable” error message can be caused by these factors:

• You are on an older version of the Agent.
  • Solution: Upgrade to the latest version of the Agent.

• The Jitterbit Services are not running.
  • Solution: Services can be started in %windir%\system32\services.msc; OR

• • Solution: In the install directory you will find a StartServices.bat script that will start the relevant services; OR

• • Solution: For Windows, you will find an option to Start Jitterbit Services in the Start Menu.
    

• • Usually, if a service is not starting, you will find an error during the restart.
    • For Windows: Look for an error in C:\Program Files (x86)\Jitterbit Agent\log. Ensure they are running as Local System and check the Event Log for any error message.
    • For macOS: Look for an error in /Users/USERNAME/Library/Application Support/JitterbitCloudDataLoader.
    • For Linux: Look for an error in Maintenance/logs.

• Services are running but not able to communicate with Jitterbit Cloud.

  • Solution: Check:

    • If the Internet is working.

    • The log file, to see if there is an obvious error message:

      • For Windows: Either C:\Program Files (x86)\Jitterbit Cloud Data Loader\log\jitterbit-agent.log or C:\Program Files (x86)\Jitterbit Agent\log\jitterbit-agent.log.

      • For macOS: /Users/USERNAME/Library/ApplicationSupport/JitterbitCloudDataLoader/log/jitterbit-agent.log.

      • For Linux: Maintenance/logs/jitterbit-agent.log.

• Proxy problems can also cause the Agent Not Running or Unreachable error message. Troubleshooting this, is a little more difficult, as there are so many different network configurations.

  • Solution: During install, you may have to check or uncheck the Negotiate Ntlm Proxy. This depends on which proxy you have. It is also very helpful to see the Denied Log from the Proxy Server.