Error: Agent failed to register to the cluster. Access Token is invalid.

Full error message:

The SWO Agent has failed to register to the cluster at xx-yy.cloud.solarwinds.com. Access Token is invalid.

If you encounter this error when installing the Agent using the bash installation script, check the API token in the script. Make sure the API token is the same as the -AccessToken used in Add Host wizard. If it is different, copy the token from the wizard and use it in the script. See Add a self-managed host.

Error: Agent failed to register to the cluster. Connection problem. Verify SWO_URL.

Full error message:

The SWO Agent has failed to register to the cluster at na-01.cloud.solarwinds.com. Connection problem. Please verify SWO_URL.

If you encounter this error when installing the Agent using the bash installation script, verify the following:

• Make sure the SWO_URL used in the script is the same as the SWO_URL used in the Add Host wizard.

  

• Check the operation status of SolarWinds Observability and its services at https://status.cloud.solarwinds.com/

• Make sure that the firewall on the host allows access to all SolarWinds Observability SaaS endpoints. See Data centers and endpoint URIs.

Error: SWO Agent already installed and deactivated

Full Linux messages:

• Warning: The SWO Agent is already installed on this machine. The installation might not succeed. It is recommended to uninstall the SWO Agent before performing a new installation.

• Error: SWO Agent is already installed and deactivated. Please uninstall the SWO Agent before performing a new installation.

Full Windows message:

• Warning: Client is deactivated. Please uninstall client and run script again.

If you encounter this issue when installing the Agent using the bash or PowerShell installation script, the SWO Agent was already installed on this host and removed from the Agents page in SolarWinds Observability SaaS. The Agent is thus deactivated and needs to be completely uninstalled and reinstalled.

See Reinstall the Agent.

Warning: Agent already installed. The installation might not succeed.

Full warning message:

SWO Agent is already installed on this machine. The installation might not succeed. It is recommended to uninstall the SWO Agent before performing a new installation.

If you encounter this warning when installing the Agent using the bash or PowerShell installation script, the Agent is installed on this host.

To address the issue, uninstall the Agent and then re-install it. See Reinstall the Agent

Error: rpmdb open failed

If you encounter the rpmdb open failed error when installing the Agent on a private EC2 instance, rebuild the RPM database.

Error message:

Error: rpmdb open failed

To address the issue, run the following script to rebuild the RPM database:

mkdir /var/lib/rpm/backup
cp -a /var/lib/rpm/__db* /var/lib/rpm/backup/
rm -f /var/lib/rpm/__db.[0-9][0-9]*
rpm --quiet -qa
rpm --rebuilddb
yum clean all

Issues with the Agent service startup after the target host restart

When you have deployed the SolarWinds Observability Agent on a Windows computer and you stop receiving data after the computer restarts, complete the following steps.

1. In SolarWinds Observability SaaS, click Settings > Agents.

2. Locate the computer hosting the Agent and review the Agent status. If it is disconnected, the service was not restarted correctly.

3. On the computer hosting the Agent, open Services.

4. In Services, locate the SolarWinds UAMS Client service and check its status.

5. If the service is not running, restart it.

6. If restarting the service doesn't resolve the issue, right-click the service and set the Startup type to Automatic (Delayed Start).

The automatic startup type will resolve the issue, the Agent in SolarWinds Observability SaaS will be connected, and you should be receiving data.

The Agent fails to install because enabled cipher suites do not match supported ciphers

Enable the supported cipher suites on your servers. See Cipher suites supported by SolarWinds Observability Agent.