RunCloud Warning: Server Is Not Running the Latest Agent

March 4, 2023 . 2 MIN READ

RunCloud is a cloud server management platform that helps you easily manage web applications and servers. However, in some cases, RunCloud may fail to automatically update your server due to reasons such as network issues, firewall restrictions, or package conflicts.

If your server is not running the latest version of the RunCloud agent, you’ll see a warning on the RunCloud dashboard stating “Server not running latest agent.”

This warning indicates that your server is using an outdated RunCloud agent. An outdated agent can cause certain features to malfunction or leave security vulnerabilities unpatched. To resolve this issue, the agent must be updated manually via SSH.


Updating the RunCloud Agent

Follow the steps below to update the RunCloud agent manually:

  1. Log in to your server via SSH.

  2. Update system packages:

    apt update && unattended-upgrade -d

    This command checks for available updates and installs them automatically.

  3. Update the RunCloud agent based on your server type:

    • For Nginx servers:

      apt upgrade runcloud-agent -y
    • For OpenLiteSpeed servers:

      apt upgrade runcloud-agent-lsws -y
    • For Docker servers:

      apt upgrade runcloud-agent-docker -y
  4. Restart the RunCloud agent:

    service runcloud-agent restart

    This allows the agent to apply changes and resync with the RunCloud API.


Sync Agent Version on the Dashboard

After updating the agent via CLI—or if you restore your server from a provider-level snapshot (such as DigitalOcean or Vultr), which may revert the agent to an older version—the dashboard may not immediately reflect the updated version.

In this case, use the “Sync Agent” button in the server settings to resolve any discrepancies between the installed agent version and the version shown on the RunCloud dashboard.


Troubleshooting Package Update Errors

On older Ubuntu versions, you may encounter errors while updating package lists due to outdated or moved repositories. These errors occur when the system attempts to access repositories that no longer have a valid release file.

Fixing MariaDB Repository Errors

  1. Open the sources list using a text editor (for example, Nano):

    sudo nano /etc/apt/sources.list
  2. Locate the problematic repository entries, such as:

    deb [arch=amd64,arm64,ppc64el] http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.2/ubuntu bionic main
  3. Comment out these lines by adding # at the beginning:

    # deb [arch=amd64,arm64,ppc64el] http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.2/ubuntu bionic main
  4. Save the file and exit the editor.

  5. Update the package list:

    sudo apt update

After completing these steps, retry updating the RunCloud agent. Once the update is successful, your server will run the latest agent and fully benefit from RunCloud’s features.

Reference:

https://runcloud.io/knowledgebase/articles/server-management/server-not-running-latest-agent-warning

 

Leave a Reply

Your email address will not be published. Required fields are marked *