Agent issues

Troubleshooting guide for Alpamon agent issues.

Agent installation failure

Incorrect OS family selection

Selecting the wrong OS family for your server during agent installation can cause installation to fail.

The default installation script works regardless of OS type, so installation usually succeeds. However, when installing the agent manually, the installation script differs by OS family, so selecting the wrong OS will cause installation to fail.

What to do:

1. Verify server’s actual OS family:

   • Debian family: Ubuntu, Debian, etc.
   • RedHat family: RHEL, CentOS, Fedora, Amazon/Rocky/Oracle Linux, etc.

2. When registering the server on Server register page, select the correct OS family

3. If using manual installation script, install the agent using a script that matches the selected OS family:

   • Debian family selected: Use script that includes apt-get install -y alpamon command
   • RedHat family selected: Use script that includes yum install -y alpamon command

4. If server was registered with wrong OS family, delete the server and register again with correct OS family

Workspace migration

If you register a server from another workspace to a new workspace without removing the agent first, the agent may continue to be connected to the old workspace. In this case, server connection is not possible in the new workspace.

What to do:

1. In old workspace, delete server with automatic agent removal enabled (removes previously installed agent from server)

2. If cannot access old workspace, refer to Remove server and remove agent manually

3. In new workspace, perform server registration and agent installation from scratch

Agent upgrade issues

Content needs to be written