Updated: 11 October 2026 · Applies to: SolusVM 1 (administrators)
If the SolusVM panel or a node stops responding, restart its services from the server's command line.
Find and restart the SolusVM services
systemctl list-units --all | grep -i -E "solus|svm" # service names on this server systemctl restart <service-name> systemctl status <service-name>
On older SysV-init systems the services are in /etc/init.d/. If a script there cannot be run, check that it is executable (chmod 755) and owned by root.
If it still fails
- Look at the SolusVM logs in
/usr/local/solusvm/and the system log (journalctl -xe). - Check free disk space (
df -h): full disks are a common reason for services not starting. - Make sure the node can reach the master on the SolusVM ports through the firewall.
Note: This guide is for administrators of a SolusVM installation. Ucartz VPS customers manage their VPS in the Ucartz client area (Virtualizor), and can ask our support team to set reverse DNS or restart a VPS.