https://docs.sysward.com/docs/getting-started/Recent content in Getting Started onHugo -- gohugo.ioen-USThu, 09 Jul 2026 00:00:00 +0000https://docs.sysward.com/docs/getting-started/quick-start/Mon, 16 Nov 2020 13:59:39 +0100https://docs.sysward.com/docs/getting-started/quick-start/Install the agent Sign in to your dashboard and open the Install Agent page. You’ll see a one-line installer prefilled with your organization’s API key: curl https://sysward.com/install.sh | API_KEY=YOUR_API_KEY bash Run it on any Linux server you want to manage, as root or with sudo. The installer: creates /opt/sysward/bin and downloads the agent binary matching your server’s architecture (x86_64, aarch64, …), writes the agent configuration with your API key, and runs the agent once so the server checks in immediately.https://docs.sysward.com/docs/getting-started/install/Tue, 13 Oct 2020 15:21:01 +0200https://docs.sysward.com/docs/getting-started/install/The Install Agent page in your dashboard shows a one-line installer with your organization’s API key already filled in. Run it on each Linux server you want to manage. The one-line installer curl https://sysward.com/install.sh | API_KEY=YOUR_API_KEY bash Run it as root or with sudo — the installer writes to /opt/sysward. What the installer does Creates /opt/sysward/bin. Downloads the agent binary for your server’s architecture (sysward_$(uname -m), e.g. x86_64 or aarch64). Downloads the default agent configuration and writes your API key into it.https://docs.sysward.com/docs/getting-started/troubleshooting/Thu, 12 Nov 2020 15:22:20 +0100https://docs.sysward.com/docs/getting-started/troubleshooting/An agent isn’t checking in If a server isn’t showing up on the Agents page, or is marked dead, work through the following on that host. Run the agent manually with debug output DEBUG=true /opt/sysward/bin/sysward This prints what the agent is doing and surfaces most problems — connectivity, configuration, or package-manager errors — directly. Check the logs The agent logs to syslog, tagged SYSWARD: grep SYSWARD /var/log/syslog | tail Confirm the agent is scheduled The agent checks in on a schedule via cron.https://docs.sysward.com/docs/getting-started/uninstall/Tue, 13 Oct 2020 15:21:01 +0200https://docs.sysward.com/docs/getting-started/uninstall/💡 Make sure you clear out your crontab Uninstalling SysWard Remove the SysWard agent directory: rm -rf /opt/sysward Then open your /etc/crontab file and remove the SysWard line so the agent stops checking in.