Remote Agent Troubleshooting (version >= 2.2.1)

If you see an error on the Remote Agents page, the suggestions in this topic can help you determine how to address the problem.

Determine Whether the Remote Agent is Currently Running

Unix

Run this command:
systemctl | grep running | grep logichub-remote-agent-supervisor

If the command doesn't generate any output, it means that the remote agent isn't running. To start the remote agent again, run this command:

sudo bash install_and_run.sh

Windows

  1. Open Services.
  2. Find Logichub Remote Agent and Logichub Remote Agent Supervisor.
  3. Check whether the status is 'Running' for both of them.
  4. If the supervisor/agent isn't running, restart the supervisor. Open Windows PowerShell, go to the folder where the remote agent was downloaded, and restart the supervisor using the following commands.

cd <download location>
./remote-agent-supervisor --startup=auto install
./remote-agent-supervisor start

Remote agent not set up to start on reboot

Unix

Run this command:

systemctl list-unit-files | grep enabled | grep logichub-remote-agent-supervisor

If no output is generated, it means that the remote agent is not enabled.

To re-enable the agent run the following command. Include the --now if the remote agent service is not currently running.

systemctl enable --now logichub-remote-agent.service

Windows

  1. Open Services.
  2. Find Logichub Remote Agent.
  3. Check whether the startup type is Automatic.
  4. If the startup type isn't Automatic, open Windows PowerShell, go to the folder where the remote agent was downloaded, and set the startup option to auto install.
    cd <download location>
    ./remote-agent-supervisor --startup=auto install

If the agent isn't already started, run the following command.
./remote-agent-supervisor start

Remote Agent Isn't Able to Connect

Do the following for Unix and Windows,

  1. Start a terminal or PowerShell session.
  2. Go to the location where the remote agent is installed.
  3. Use the following command to examine the logs for messages similar to 'Lost connection to LogicHub'.

tail -f logs/agent.log

If you see messages of this type, there could be an error on the LogicHub server, or a misconfiguration in agent.config. If you edited the agent.config file manually, try to revert the changes made and restart the agent. If that doesn't work, try downloading the latest version of the remote agent from the Settings > Advanced Settings page.

If you still see connection errors, send a message to [email protected] Attach the agent.config, supervisor.log, and agent.log files. Include the version of the remote agent as shown on the Settings > Advanced Settings page and any other relevant information.


Did this page help you?
© 2017-2021 LogicHub®. All Rights Reserved.