Documentation forSolarWinds Observability

Troubleshoot SolarWinds Observability Agent installation issues

When you experience issues with a SolarWinds Observability Agent (SWO Agent), consider reinstalling it.

Error: rpmdb open failed

If you encounter the rpmdb open failed error when installing the SWO 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

Reinstall the SWO Agent used for adding hosts via a ready-made PowerShell script

  1. On the server hosting the SWO Agent, uninstall the SWO Agent. See Uninstall the SWO Agent.

  2. Remove the SWO Agent from SolarWinds Observability.

    1. In SWO Agent, click Settings > Agents.

    2. In Agents, locate the entity hosting the SWO Agent.

    3. Click the vertical ellipsis at the end of the row, and then click Delete.

      See Remove the SWO Agent from SolarWinds Observability.

  3. Install SWO Agent.

    1. In SolarWinds Observability, click Add Data in the upper-right corner.

    2. Click Host.

    3. On the Add Host dialog, copy the PowerShell script.

    4. Run the script on the server hosting the SWO Agent. Use PowerShell with administrator permissions.

Reinstall the SWO Agent used by Network Collector via a ready-made PowerShell script

  1. On the server hosting the SWO Agent, uninstall the SWO Agent. See Uninstall the SWO Agent.

  2. Remove the SWO Agent from SolarWinds Observability.

    1. In SWO Agent, click Settings > Agents.

    2. In Agents, locate the entity hosting the SWO Agent.

    3. Click the vertical ellipsis at the end of the row, and then click Delete.

      See Remove the SWO Agent from SolarWinds Observability.

  3. Install the SWO Agent:

    1. In SolarWinds Observability, click Add Data in the upper-right corner.

    2. Click Network Device.

    3. On Add Network Device, copy the PowerShell script.

    4. Run the script on the server hosting the SWO Agent. Use PowerShell with administrator permissions.

Reinstall the SWO Agent used by a host via the MSI file with parameters

If you prefer using the MSI file, add the additional parameter METADATA="role:host-monitoring".

  1. On the server hosting the SWO Agent, uninstall the SWO Agent. See Uninstall the SWO Agent.

  2. Remove the SWO Agent from SolarWinds Observability.

    1. In SWO Agent, click Settings > Agents.

    2. In Agents, locate the entity hosting the SWO Agent.

    3. Click the vertical ellipsis at the end of the row, and then click Delete.

      See Remove the SWO Agent from SolarWinds Observability.

  3. Copy or create an API token (Ingestion type), found in the settings area of SolarWinds Observability. You will need it later. See API Tokens for details.

  4. Start PowerShell with administrator privileges.

  5. In the PowerShell console, go to the folder with uamsclient.msi.

  6. In the following command, replace ....... with the token copied previously, and then run the command.

    msiexec /i uamsclient.msi ACCESSTOKEN="........." METADATA="role:host-monitoring"

Reinstall the SWO Agent used by Network Collector via the MSI file with parameters

If you prefer using the MSI file, add the additional parameter METADATA="role:SiteCollector".

  1. On the server hosting the SWO Agent, uninstall the SWO Agent. See Uninstall the SWO Agent.

  2. Remove the SWO Agent from SolarWinds Observability.

    1. In SWO Agent, click Settings > Agents.

    2. In Agents, locate the entity hosting the SWO Agent.

    3. Click the vertical ellipsis at the end of the row, and then click Delete.

      See Remove the SWO Agent from SolarWinds Observability.

  3. Copy or create an API token (Ingestion type), found in the settings area of SolarWinds Observability. You will need it later. See API Tokens for details.

  4. Start PowerShell with administrator privileges.

  5. In the PowerShell console, go to the folder with uamsclient.msi.

  6. In the following command, replace ....... with the token copied previously, and then run the command.

    msiexec /i uamsclient.msi ACCESSTOKEN="........." METADATA="role:SiteCollector"

Issues with the SWO Agent service startup after the target host restart

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

  1. In SolarWinds Observability, click Settings > Agents.

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

  3. On the computer hosting the SWO 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 SWO Agent in SolarWinds Observability will be connected, and you should be receiving data.