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. Confirm the SysWard entry is still present:
grep -r sysward /etc/crontab /etc/cron.d/ 2>/dev/null
Check connectivity
The agent needs outbound HTTPS to reach SysWard and to download updates. From the host:
curl -sSI https://sysward.com | head -1
curl -sSI https://updates.sysward.com | head -1
If these fail, check the server’s firewall, proxy, or DNS.
Verify the API key
The agent’s API key lives in /opt/sysward/bin/config.json. If you rotated your
organization’s key, re-run the installer from the Install Agent page to
refresh it.
Reinstalling the agent
Re-running the one-line installer is safe — it replaces the agent binary and configuration in place:
curl https://sysward.com/install.sh | API_KEY=YOUR_API_KEY bash
Checking the agent version
/opt/sysward/bin/sysward -version
Removing an agent
To unregister and remove the agent entirely, see Uninstall.