A targeted service restart can recover a failed daemon or apply a validated configuration change. It also interrupts dependent connections, so identify the affected component and preserve useful evidence first.
IN THIS ARTICLE
01 What you need before you begin
Confirm administrator authorisation and an appropriate interruption window. Save relevant logs and verify that no transfer, backup restore or upgrade would be disrupted by the restart.
02 Restart one affected service from WHM
- Check Service Status and reproduce the affected function to confirm which service needs attention.
- Review recent configuration changes and validate their syntax through the supported mechanism before restarting. A bad configuration can prevent the service returning.
- Open the specific service under Restart Services and read its confirmation. Restart only that component once.
- Wait for the operation’s result, then inspect Service Status and the service log for startup errors.
- Test the original customer function and monitor for recurrence. Record the restart time and any underlying corrective action.
03 Confirm the expected result
The selected service should start cleanly and the affected function should work. Confirm dependent applications reconnect successfully rather than judging only the daemon’s status.
04 Troubleshoot unexpected results
If it fails again, stop repeated restarts and investigate the reported configuration, resource or application cause. Use the established console recovery route if a management-service restart affects your session. A whole-server reboot is a separate broader action.
05 Example: restart a service after checking the evidence
A website problem does not automatically require restarting every service. Record the symptom first. If email and database connections still work, keep those services running while you investigate the web service.
- Read the relevant error log and confirm which service is failing. Check whether a configuration change happened just before the fault.
- Use the service's supported configuration test where available. A restart with an invalid configuration may turn a partial problem into a complete outage.
- Restart only the identified service through WHM during an appropriate window. Notify affected users when active connections may be interrupted.
- Test the original customer-facing action, then check the service status and new log entries.
What if the service fails again immediately?
Repeated restarts can obscure the first useful error. Preserve the log around the failure and investigate the underlying configuration, dependency, resource or permission problem. Do not schedule a repeated restart as a substitute for diagnosis.
Root-level WHM instructions are for server administrators. If you use our shared hosting or a reseller account without the required permissions, contact us with the affected service and time of the problem. Do not attempt to bypass your account's access restrictions.
Will a restart repair a full disk?
No. Services still need writable storage and available resources. Correct the storage problem safely, preserving required data and logs, then recover the affected service.