This document describes several methods to restart the services (often daemons) on your server. Daemons are small processes that run in the background of your server.
You may wish to restart a service if, for example, you changed a service’s configuration, or if the service experiences problems.
Whenever you change the server's hostname, you must use one of the following methods:
/usr/local/cpanel/bin/set_hostnameutility as the
These methods ensure that all of the necessary system and service changes occur.
If you update your hostname, the system blocks user access to the following interfaces and services:
The system restores access to these interfaces and services after the hostname update finishes. For more information, read our Interface Lock Scripts documentation.
Unless problems prevent this, you can restart most services in WHM's Restart Services interface (Home >> Restart Services).
If you use IPv6, the
service network restart command will remove the IPv6 addresses from the network device. To restart your IPv6 configuration after you run the
service network restart command, you must run the appropriate command for your version of cPanel & WHM:
/etc/init.d/cpipv6 restartcommand after you restart the network service.
/scripts/restartsrv_cpipv6command after you restart the network service.
If a service will not restart from WHM, use the
/usr/local/cpanel/scripts/restartsrv_* command to attempt to restart the service from the command line.
*with the correct value for that service.
/usr/local/cpanel/scripts/restartsrv_* script does not restart the service, you can attempt to restart the service directly.
For servers that run CentOS, CloudLinux™, Red Hat® Enterprise Linux (RHEL) 6, or Amazon Linux, run the following command, where
/etc/rc.d/init.d/service is the path to the service:
For servers that run CentOS 7, CloudLinux 7, or RHEL 7, run the following command, where
service-name is the service that you wish to restart:
If the restart fails, check the service’s error log for help to diagnose the issue. Because each service logs its errors differently, check the service’s documentation to find the error log’s location.
The following table lists common locations for some service's error logs:
Apache web server
Details errors encountered during Apache requests.
Exim mail transfer agent (MTA)
Details all Exim transactions.
Details rejected messages and reasons.
Details configuration and similar errors.
If this log is not empty, Exim has serious problems and will not run on some distributions.
We removed the Courier mail server in cPanel & WHM version 54. The Courier mail server only exists for cPanel & WHM version 11.52 and earlier.
MySQL database server
OpenSSH secure shell service
The log file's location depends on the configuration of the
There is no content with the specified labels