Page tree
Skip to end of metadata
Go to start of metadata

Overview

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.

Unable to render {include} The included page could not be found.

Restart services in the WHM interface

Unless problems prevent this, you can restart most services in WHM's Restart Services interface (Home >> Restart Services).

Restart services from the command line

Important:

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:

  • For cPanel & WHM version 11.52 and earlier, run the /etc/init.d/cpipv6 restart command after you restart the network service. 
  • For cPanel & WHM version 54 and later, run the /scripts/restartsrv_cpipv6 command after you restart the network service.

Use the restartsrv script

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.

  • When you run this command, replace * with the correct value for that service. 
  • For more information, read our WHM Scripts documentation.

Direct service restart

If the /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:

/etc/rc.d/init.d/service restart

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:

systemctl restart service-name.service

Service error logs

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:

ServicesLog locationNotes

Apache web server

/usr/local/apache/logs/error_log

Details errors encountered during Apache requests.

  • BIND nameserver
  • ProFTP FTP server
  • Pure-FTP FTP server

/var/log/messages

 

Exim mail transfer agent (MTA)

 

 

/var/log/exim_mainlog

Details all Exim transactions.

/var/log/exim_rejectlog

Details rejected messages and reasons.

/var/log/exim_paniclog

Details configuration and similar errors.

Important:

If this log is not empty, Exim has serious problems and will not run on some distributions.

  • Courier mail server
  • Dovecot mail server

/var/log/maillog

Unable to render {include} The included page could not be found.

MySQL database server

/var/lib/mysql/hostname.err

Substitute hostname with your server's hostname.

OpenSSH secure shell service

/var/log/messages

The log file's location depends on the configuration of the syslog service.

/var/log/secure
/var/log/auth

Additional documentation