Update agent

Reading Time: < 1 minute

When to use

Update the agent when the version on the server lags behind latestAgentVersion in Vezha.

What happens during the upgrade

• Backend sends the upgrade command to the agent.
• Agent downloads new binary for download_url.
• Verifies SHA-256 checksum.
• Atomically replaces the current binary.
• Relaunches through the system service manager (systemd/launchd/Windows SCM).

Steps

1. In the list of servers, find the node with the outdated version of the agent.
2. Start the Upgrade Agent.
3. Wait for the server to return online after restarting the agent.

What to check

• agentVersion is equal latestAgentVersion.
• Telemetry continues to arrive without fail.
• Managed functions (terminal/vnc/services/containers) work normally.

Typical causes of failure

• Agent is offline while sending command.
• Network restrictions up to /api/downloads/....
• Problems with restarting the system service on the server.