How to Restart Services in WHM: Complete Guide Print

  • restart services, whm, apache, mysql, dns server, email server, ftp server, service management
  • 0

You can restart essential server services like Apache, MySQL, DNS, and FTP directly through WHM's Restart Services interface. This tool allows you to quickly restart running services without using command-line access, helping you resolve common issues like unresponsive web servers or email services.

What is the Restart Services Interface?

The Restart Services interface in WHM provides a simple way to restart critical server services through a web-based control panel. When you make configuration changes or need to clear service issues, restarting the affected service often resolves the problem immediately. This interface only works for services that are currently running; you cannot restart a service that has been stopped.

Important: If you need to start or stop services (rather than restart them), use the Service Manager interface instead. Navigate to WHM, then go to Service Configuration and select Service Manager.

Which Services Can You Restart?

OBHost's WHM interface allows you to restart the following core services. Each restart requires confirmation to prevent accidental disruptions.

DNS Server

Restart your DNS service (BIND, NSD, or MyDNS) when DNS changes aren't taking effect or domain name resolution issues occur. Click the DNS Server option and confirm when prompted to restart the service.

FTP Server (ProFTPD/Pure-FTPd)

Restart the FTP service to resolve file upload issues or connection problems. This applies to both ProFTPD and Pure-FTPd implementations. Click Yes when the system prompts for confirmation.

HTTP Server (Apache)

Restart Apache web server when website configuration changes need to take effect or when sites become unresponsive. This is one of the most commonly restarted services after making changes to virtual hosts or Apache settings.

IMAP Server (Dovecot)

Restart the Dovecot IMAP service when email clients cannot connect or retrieve messages. This helps resolve email access issues without affecting mail delivery.

Mail Server (Exim)

Restart Exim when you experience email sending or receiving problems. Changes to mail configuration typically require an Exim restart to take effect.

Mailing List Manager (Mailman)

Restart Mailman when mailing list functionality stops working properly or after making changes to list configurations.

PHP-FPM Service for Apache

Restart PHP-FPM when PHP scripts become unresponsive or after changing PHP configuration settings. This service manages PHP processes separately from Apache.

SQL Server (MySQL)

Restart MySQL database server when database connections fail or after making changes to MySQL configuration files. Be aware this briefly interrupts database access for all websites.

SQL Server (PostgreSQL)

Restart PostgreSQL database service when PostgreSQL databases become unresponsive or configuration changes need to be applied.

SSH Server (OpenSSH)

Restart the SSH service when remote access via SSH stops working or after changing SSH configuration settings. Existing SSH connections will be terminated.

How to Restart a Service

Restarting a service through WHM is straightforward:

  1. Log into WHM as the root user or an administrator
  2. Navigate to the Restart Services interface
  3. Select the service you want to restart from the list
  4. Click the restart option for that service
  5. Click Yes when the confirmation prompt appears
  6. Wait for the system to confirm the service has restarted successfully

What to Do If a Service Won't Restart

If the Restart Services interface fails to restart a service, the service likely has underlying configuration errors or conflicts. In these cases, you should check the service's error logs for specific issues. Common problems include syntax errors in configuration files, port conflicts, or insufficient system resources.

You can also try using command-line methods to restart services with more detailed error output. The Service Manager interface provides additional options for troubleshooting, including the ability to view service status and manually start stopped services.

When Should You Restart Services?

Restart services in these common scenarios:

  • After modifying service configuration files
  • When a service becomes unresponsive or slow
  • After installing or updating software that affects the service
  • When implementing security updates
  • To clear temporary service errors or connection issues
  • After changing DNS records or email settings

Frequently Asked Questions

Can I restart multiple services at once in WHM?

No, the WHM Restart Services interface requires you to restart each service individually. This design prevents accidentally disrupting multiple services simultaneously and allows you to monitor each service restart separately.

Will restarting Apache disconnect active website visitors?

Apache restarts typically complete in seconds with minimal disruption. Most modern configurations use graceful restarts that allow existing connections to complete before restarting. However, very brief interruptions may occur for new connections during the restart process.

Why does WHM say I cannot restart a stopped service?

The Restart Services interface only works for services that are currently running. A restart command requires an active service to stop and then start again. If a service is already stopped, you need to use the Service Manager interface to start it instead.

How long does it take for a service to restart?

Most services restart within 5 to 15 seconds. Larger services like MySQL or Apache with many virtual hosts may take slightly longer. If a restart takes more than 30 seconds or fails, check the service's error logs for configuration problems.

If you need assistance restarting services or troubleshooting service issues, OBHost's support team is available 24/7. Visit our contact page or email support@obhost.org for expert help.


Was this answer helpful?

« Back