agent commands

Agent commands

remotepower-agent status        # Show enrollment info, version, all interfaces
sudo remotepower-agent enroll   # Enroll interactively
sudo remotepower-agent re-enroll  # Re-enroll preserving history/tags/group/notes
sudo remotepower-agent update   # Force self-update check immediately
sudo remotepower-agent integrity  # Verify binary SHA-256 vs server
sudo remotepower-agent run      # Run in foreground (debug)

systemctl status remotepower-agent
journalctl -u remotepower-agent -f
systemctl restart remotepower-agent

Optional: metrics collection

pip install psutil --break-system-packages
sudo systemctl restart remotepower-agent

Read-only audit mode (v5.0.0)

To make an agent refuse every command (exec, reboot, config apply, self-update) while it keeps observing and reporting, create an operator-owned marker file:

sudo touch /etc/remotepower/audit-mode        # Linux / macOS
#  Windows: create  %ProgramData%\RemotePower\audit-mode  (no extension)

The agent then rejects all commands at the source, reports audit_mode: true in its heartbeat (the device shows an AUDIT badge), and the server refuses to even queue commands for it. The server cannot clear the file — only someone with access to the host can. Remove the file to restore normal operation. Enforced identically by the Linux, Windows and macOS agents.

Per-command timeout (v5.0.0)

A queued exec command can carry its own timeout with a to=<seconds>: prefix, for example exec:to=600:restic backup …. The value is clamped to 1–3600s and overrides the default (300s, or 1800s for package-upgrade/reboot commands). All three agents honour it.

Agent / server version compatibility (v5.0.0)

The server tracks each agent's version against its own. An agent on the same major version is fine; one a major behind is offered an update; one more than a major behind is flagged for a clean reinstall rather than a self-update; an agent newer than the server (downgrade risk) is flagged so you upgrade the server first.

Backup integrity verification (v4.10.0)

Point the agent at backup files/repos to verify (restic / borg / tar check) via backup_monitors in the agent config. Results ride the heartbeat and raise backup_verify_failed / backup_verify_passed events so a silently-corrupt backup is caught before you need it.

---

← Back to docs index · Back to main README