About Server Health agent
The Server Health agent is the main RootManage agent. It sends a heartbeat to your dashboard and does a daily hardening and package check, so you can see how a server is doing without logging in. It works on Ubuntu, Debian, RHEL, CloudLinux, AlmaLinux and Rocky Linux.
You install it with one command from your dashboard. It uses a low priority so it stays out of the way of your sites.
What it does
- Heartbeat to the dashboard with load, memory, disk and network figures
- Daily scan at 01:00 IST: hardening score and known package vulnerabilities, with copy-paste solve commands
- Picks up Run now requests from the dashboard on the next heartbeat (about a minute)
- Shows the heaviest processes so an administrator can stop a runaway one
- Detects common control panels and backup tools
What it does not do
- It is not a DDoS shield
- It is not a complete vulnerability list for every application
- It does not change your server settings by itself
Schedule: Heartbeat about every minute, scan every day at 01:00 IST
How it updates
The agent checks for a newer version itself and replaces its own script. You normally do nothing. To check by hand, run the command below.
sudo rootmanage-agent --self-updateServer Health agent version history
- UpdateNew
Heavy processes panel and the activity log
The dashboard can now show the processes using the most CPU, and an administrator can stop a runaway one. Every action is recorded in an activity log.
The version number was not recorded. The date is the date of the database change that shipped it.
What changed
- The agent reports the top processes by CPU for the heavy-process panel
- An administrator can stop a process through the same safe job queue as Run now. Clients cannot stop processes
- An activity log records who did what, for both administrators and clients
How it affects you
- You can see why a server is slow without logging in
- Every stop request is recorded with the name of the person who made it
What to do. Nothing to do. The agent updates itself.
- UpdateNew
Run now from the dashboard
You can ask the Server Health agent for an immediate check or scan from your dashboard instead of waiting for the next scheduled run.
The version number was not recorded. The date is the date of the database change that shipped it.
What changed
- Run now in the dashboard queues a job for the server
- The agent picks it up on its next heartbeat, about a minute later, and shows the result and a log tail
- Jobs are queued and run with a low priority
How it affects you
- Useful right after a fix, to see the result at once
What to do. Nothing to do. The agent updates itself.
- v2.3.0ImprovedNew
Daily refresh of the hardening and package-scan engines
The daily job now refreshes its checking engines before it scans, so the results use up-to-date information.
Released at 21:15 IST.
What changed
- At 01:00 IST the agent refreshes the hardening and package-scan engines from their official sources, using little CPU, then runs the scan
- If an engine is missing, the daily job tries to install it again
- Inactive or unpaid servers stop before any update or scan
- Detects common control panels and backup tools
- Server Health and the Admin Live Monitor show the hardening score, package vulnerabilities and copy-paste solve commands
- Commands: rootmanage-agent --once, --scan, --self-update and --version
How it affects you
- The daily scan can take a little longer because the engines are refreshed first
- Scans only run for servers with an active plan
What to do. Nothing to do. The agent updates itself.
- v2.1.0New
Daily scan, CPU limit and self-update
The agent got its daily scan and the ability to update itself.
What changed
- Daily scan at 01:00 IST with a CPU limit
- Stops early on inactive servers
- Detects the software stack on the server
- Uses Lynis and Trivy when they are installed
- Updates itself
How it affects you
- Low impact on your sites, and servers update without your help
What to do. Nothing to do. The agent updates itself.
- UpdateNew
Live server monitoring starts
The first version of live server monitoring: an agent on your server reports to your dashboard.
The version number was not recorded. The date is the date of the database change that shipped it.
What changed
- Each server gets its own agent token
- A heartbeat sends the latest load and usage figures
- Alerts appear in the dashboard, and administrators see every server in the Live Monitor
How it affects you
- You can see how a server is doing without logging in
What to do. Install the agent with the command from your dashboard.
Questions about Server Health agent updates
Do I need to update the Server Health agent myself?
No. It updates itself. You can check the installed version with rootmanage-agent --version and update at once with sudo rootmanage-agent --self-update.
Why do the release notes stop at 2.3.0?
Versions 2.4.0 to 2.7.1 were released but their notes were never written down, so they are not listed. Every update from now on is listed here with its date.