Service Status shows the services monitored by WHM alongside system and disk information. Use it to narrow an incident before restarting components that may be healthy.
IN THIS ARTICLE
What you need before you begin
Record the affected customer function, error and time. Determine whether the failure affects one account or many, and check for an ongoing approved maintenance task.
01 Check WHM service status before restarting anything
- Open Service Status and inspect the relevant service, such as web, mail or database.
- Distinguish down from pending. Pending can mean monitoring is temporarily paused during a restart or installation, rather than that the service itself is suspended.
- Review disk, memory and load information. A full filesystem can cause several services to fail together and will not be fixed by repeated restarts.
- Perform a representative external test and inspect the affected service’s recent logs. Compare the monitoring result with the actual user symptom.
- Document the likely cause and choose a targeted correction, escalation or service restart only when justified.
Confirm the expected result
You should know whether the incident is a monitored service failure, a broader resource problem or an account/application issue. Keep the observation time with the result.
Troubleshoot unexpected results
A service marked up can still have an application-specific problem. The server profile and monitoring settings also determine which services appear. If a customer cannot connect while the service is healthy, inspect DNS, firewall and account restrictions before restarting it.
Does an up status prove every website works?
No. It indicates the monitored service responds to its check. Individual virtual hosts, PHP applications, databases and external dependencies still need functional tests.