v0.4.0

Added

• Server Chief can reboot the server from the dashboard with the new reboot command. The agent waits for a running package manager to finish, schedules the reboot a minute ahead with shutdown -r +1 so logged-in users are warned, and reports the result with the new boot time after the server is back. Application containers such as Docker cannot be rebooted and report why.
• Server Chief can install package updates from the dashboard with the new upgrade_packages command: the security updates or all pending updates, never the serverchief package itself, keeping local configuration files. When the dashboard asks for it, the agent first updates itself the usual way, with its readiness check and rollback. Services that use updated libraries can be restarted afterwards (needrestart on Debian and Ubuntu, needs-restarting -s on RHEL and derivatives), so most updates take effect without a reboot, and the result says whether a reboot is still required. The upgrade runs in its own serverchief-upgrade unit, survives the agent restarting and reports what it ran. Its output streams to the dashboard while it runs, step by step, so an update can be followed live.
• A reboot can be asked to happen only when the server needs one (if_required): the agent checks right before rebooting and reports when no reboot was needed, or when it could not tell, instead of rebooting.
• Reboots and package updates can carry a deadline (not_after): the agent does not start them later than that, also not after waiting for a running package manager, and reports them as too late instead.
• serverchief disable, serverchief enable and serverchief capabilities turn remote actions (reboot and upgrade_packages) off and on again on the server itself. The setting is stored in /etc/serverchief/disabled-capabilities.json, and the dashboard shows a turned-off action as such.
• The dashboard can turn reboots and package updates off on a server with the new disable_capability command, so nobody has to log in to do it. Only serverchief enable on the server turns them on again.
• Command results include the output of what the command ran, so the dashboard can show it.
• The Debian package installs /etc/needrestart/conf.d/serverchief.conf, so needrestart never restarts the agent.
• The agent speaks revision 1.2.0 of the agent protocol.

Fixed

• Fixed the agent collecting the sites, certificates and applications of busy Plesk servers every minute. Every request writes a site's access log under /var/www/vhosts/system, which the agent took for a change of the web server configuration, so it ran apachectl -S several times a minute. Only the generated configuration in each domain's conf directory counts now, without the files of Plesk's daily statistics run.
• One inventory round runs apachectl -S and the Plesk queries once instead of once for each of the sites, certificates and applications datasets.
• A source that keeps changing is collected at most once every 5 minutes. A first change is still collected right away.
• Fixed configuration changes of some Plesk domains going unnoticed until the next scheduled collection on servers with many domains, because their logs counted towards the limit of entries checked for changes.
• Fixed one application being listed twice when its sites use document roots linked to the same directory, such as DirectAdmin's private_html linked to public_html. These sites are now one application, reported at the directory itself rather than at the link.

---

More information: README · install with curl -fsSL https://pkg.server.chief.app/install.sh | sudo bash, then run the setup command from Server Chief