Update
tealc update [AGENT_NAME] [BINARY_PATH] sends a new agent binary to a connected agent and instructs it to restart with the new version. This allows you to upgrade agents in place without manual intervention.
Before you update
- Confirm that the binary matches the target operating system and architecture.
- Keep the previous binary available so it can be restored manually if the new agent does not reconnect.
- Check that the agent is online and that an SSH session can be opened.
- Use a test agent before updating a larger deployment.
Quick usage
tealc update AGENT_NAME BINARY_PATH
The client transfers the binary over SSH, waits for the agent’s receipt confirmation, and the agent then restarts with the uploaded binary.
After the command returns, verify the new version with tealc list or the TUI. An update is not complete until the agent reconnects and is reachable.
Example
# Upgrade agent 'production-001' with a new binary
tealc update production-001 ./goauld-agent-linux-amd64
# Upgrade agent 'target-machine' with a binary from a different path
tealc update target-machine /opt/binaries/goauld-agent-v2.0
Options
Update uses the common client connection options documented in the configuration reference, including --server, --access-token, --password, and --wait-timeout.
The agent must be online and reachable via SSH for the upgrade to succeed. If the agent is not currently connected, you can use --wait-timeout to wait for it to come online before attempting the upgrade.
If the agent has a static password configured, you will be prompted for it unless the password is cached via --save-password or explicitly provided with -P.
Failure and rollback
The update is not transactional from the operator’s perspective. If the new binary cannot start or reconnect, Goauld cannot automatically reach that agent to restore the previous binary. Keep an approved out-of-band recovery method and the previous binary available for important targets.