[ 1 Installing the Remote Agent (version >= 2.2.1) ] [ 1.1 Verifying the installation ] [ 1.2 Configuration ] [ 1.3 Installing the Remote Agent (version < 2.2.1) ] [ 1.4 Upgrade Remote Agent ]

Installing the Remote Agent (version >= 2.2.1)

You can download and install the remote agent on a Unix or Windows system.

For Unix, the system must have systemd and minimum glibc version 2.12. To check the glibc version, run the command

ldd --version

The remote agent package for Unix contains the following files.

Remote agent package for Unix

lhub-remote-agent/
     |____ remote-agent-supervisor    : The executable supervisor application to manager agent.
     |____ remote-agent               : The executable agent application.
     |____ agent.config               : The agent configuration file. 
     |____ install_and_run.sh         : The script to install and run the agent.

The remote agent package for Windows contains the following files.

Remote agent package for Windows

lhub-remote-agent/
     |____ remote-agent-supervisor    : The executable supervisor application to manager agent.
     |____ remote-agent               : The executable agent application.
     |____ agent.config               : The agent configuration file.

remote-agent-supervisor is the executable supervisor application which manages the agent.
remote-agent is the executable agent application.
agent-config is the agent configuration file.

To download a remote agent package to a Unix or Windows system:

On the Settings > Advanced Settings page, click the Unix or Windows button for the remote agent. A zip file containing the remote agent software is downloaded to your local system.
Unzip the file to a convenient location.

Unix

Follow the steps to install and upgrade the remote agent for Unix.

Install and run the agent

Navigate to the directory on the Unix system that contains the unzipped remote agent package.
Run the following script as root. The script sets up the remote agent as a Unix service and starts it.

sudo bash install_and_run.sh

Windows

Follow the steps to install and upgrade the remote agent for Windows.

Install and run the agent

Navigate to the Windows folder that contains the unzipped remote agent package.
Open a command window and run the following commands. The first command installs the remote agent as a Windows service, and the second starts the remote agent.

.\remote-agent-supervisor --startup=auto install
.\remote-agent-supervisor start

The remote agent requires Windows Server 2016 or newer.

You can manage the remote agent as you would for any other Unix or Windows service. By default, the agent restarts automatically when the system reboots.

Verifying the installation

After executing above step please check for the following

The supervisor.log file should have these lines

Text

2022-07-19 09:47:00.691 INFO agent_win_service.py:SvcDoRun:42 [Dummy-2] - Started Logichub Remote Agent Supervisor.
2022-07-19 09:47:00.695 INFO commands.py:restart:26 [Thread-1] - Initializing remote agent restart process
2022-07-19 09:47:00.702 INFO commands.py:restart:28 [Thread-1] - Remote agent client termination complete
2022-07-19 09:47:03.908 INFO commands.py:start_ra_client:82 [Thread-1] - RA Client Initiated successfully.
2022-07-19 09:47:03.939 INFO supervisor.py:run:76 [Thread-1] - Commands Received: []
2022-07-19 09:47:03.939 INFO supervisor.py:run:83 [Thread-1] - Sleeping for 180 seconds

The agent.log file should have these lines

Text

Configuration

SUPERVISOR_FREQUENCY_IN_SECONDS

This property sets the frequency at which supervisor polls the service to fetch for commands. By default it's set to be 3 minutes. It's value should be at least 10 seconds otherwise the remote agent won't work.

On Unix machines the systemd service file will go into error and on Windows machine the supervisor will keep running but the logs will contain this line.

Text

PLATFORM

This property represents the platform you are on. Currently, only Unix and Windows values are supported.

On Unix machines the systemd service file will go into error and on Windows machine the supervisor will keep running but the logs will contain this line.

Text

HTTPS_PROXY

If your infrastructure doesn't allow direct access to Devo SOAR instance from the machine remote agent is installed on then we can specify the above property to route all the HTTPS requests from remote agent to this server.

To check if it's correctly set look for this line in log file

Text

HTTP_PROXY

If your infrastructure doesn't allow direct access to Devo SOAR instance from the machine remote agent is installed on then we can specify the above property to route all the HTTP requests from remote agent to this server.

Text

NO_PROXY

If you want to avoid proxy for certain URL then the URL should be put here. Ideally, this shouldn't be required since remote agent only try to connect to the Devo SOAR instance.

Text