The WHM panel provides two options for a server reboot:

• Forceful Server Reboot
• Graceful Server Reboot

The recommended option is Graceful Reboot. This way the reboot will be queued, and when all services are stopped the server will be restarted.

In a case there is a very high load on the server, the Graceful Reboot might not be sufficient. Then you will need to use the Forceful Server Reboot option.

Restarting a VPS or Dedicated server with WHM

Log into WHM.
Type "restart" in the search box at the top left to find the "Restart Services" section.
To restart Apache, select HTTP Server (Apache) and click yes.

Steps to restart your VPS in AMP

Log into AMP.
Locate your server and click the Restart VPS button. 
Expand the Restart VPS drop box and click the "Restart VPS" button. Then, allow time for the server 
to restart.

Restarting VPS and dedicated server with command line

Customers can restart their server services through the WHM or through Shell access. Please see the below tutorials on how to restart your services through WHM and through command line. You can shell into your server and stop and start your httpd services for your website. See the following commands.

Stop Apache

[email protected]### [~]# service httpd stop

Start Apache

[email protected]### [~]# service httpd start

Checks the Apache server status

[email protected]### [~]# service httpd status

You can also restart MySQL also with the following commands

Stop MySQL

[email protected]### [~]# service mysql stop

Start MySQL

[email protected]### [~]# service mysql start

Checks the MySQL server status

[email protected]### [~]# service mysql status

Applies to:

Plesk 12.5 for Linux

Symptoms

1. Plesk is not accessible due to stopped sw-engine service.
2. sw-engine cannot be started:

# service sw-engine start
/usr/sbin/sw-engine-fpm: error while loading shared libraries: libxmlrpc_cpp.so.4: 
cannot open shared object file: No such file or directory

     3. Library libxmlrpc_cpp.so.4 is missing from the server:

# ls -l /usr/lib64/libxmlrpc_cpp.so.4*
#

4. Package xmlrpc-c-c++-1.16.24-1210.1840.el6.x86_64.rpm is not installed:

# rpm -qa | grep xmlrpc
xmlrpc-c-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-1.16.24-1210.1840.el6.i686
plesk-php70-xmlrpc-7.0.9-centos6.16072211.x86_64
xmlrpc-c-c++-1.16.24-1210.1840.el6.i686

Cause

Missing libxmlrpc_cpp.so.4 library.

Resolution

1. Download xmlrpc-c-c++- package for the Linux distribution installed, e.g. for Centos6, 64-bit:

# wget ftp://fr2.rpmfind.net/linux/centos/6.8/os/x86_64/Packages/xmlrpc
-c-c++-1.16.24-1210.1840.el6.x86_64.rpm

2. Install such package:

# rpm -ivh xmlrpc-c-c++-1.16.24-1210.1840.el6.x86_64.rpm

3. Start sw-engine service

# service sw-engine start

Mail is Deferred: Delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused

Applies to:

• Plesk for Linux/Unix

Symptoms

• There are many emails in mail queue
• In /var/log/maillog the following can be found:

 servername postfix/error[15666]: 8875414912DE: [email protected], relay=none, delay=0.16, 
 delays=0.12/0/0/0.04, dsn=4.4.1, status=deferred (delivery temporarily suspended: 
 connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)

Cause

Milter service in a postfix either is not started or not working properly.

Resolution

In /etc/postfix/main.cf find a service configured on port in the error message using the following command:

 # grep 10024 /etc/postfix/main.cf /etc/postfix/main.cf:content_filter = amavis:[127.0.0.1]:10024

If output is identical consider to analyze and resolve the issue with content filter amavis.

As a temporary workaround amawis can be disabled by commenting the following lines in /etc/postfix/main.cf:

 #content_filter = smtp-amavis:[127.0.0.1]:10024
 #receive_override_options = no_address_mappings  # <- it's ok if you don't have this line

Then comment out below line in /etc/postfix/master.cf,

 -o content_filter=smtp-amavis:[127.0.0.1]:10026

Restart postfix:

 # service postfix restart

Linux

How to install Plesk additional components (like Backup Manager, PHP etc.) with autoinstaller?

There are 2 ways to install additional Plesk Components:

1. Installation from the Web Interface:

Plesk Control panel->tools and Settings->Updates and Upgrades button. Please make sure that port 8447 is opened. It is used by autoinstaller, please refer to this article for information at (Updates and Upgrades page cannot be opened: it just loads continuously I have already written).

Step 1: 

Step 2:

Step 3: 

Step 4: 

2.Installation from the Command Line:

Login to the server by SSH and launch autoinstaller:

/usr/local/psa/admin/sbin/autoinstaller

Just follow instruction on the screen and you will be able to install additional components.

Applies to:

Plesk for Linux/Unix

Symptoms

The password for the “admin” user in Plesk has been lost.

Resolution

For Plesk versions 10.x and above:

Use the ${PRODUCT_ROOT_D}/bin/admin utility to prompt the password for the “admin” user:

 # /usr/local/psa/bin/admin --show-password

Use  ${PRODUCT_ROOT_D}/bin/init_conf to reset the password for the “admin” user:

 # /usr/local/psa/bin/init_conf -u -passwd <new_password>

If the init_conf utility cannot connect to the Plesk database, follow the steps from article #112492 “Cannot log into Plesk due to incorrect admin password” to reset the Plesk database password.

For Plesk versions up to 9.x:

The Plesk admin password is stored in a hidden file on the server. Use this command to get it:

 # cat /etc/psa/.psa.shadow

This authenticates the “admin” user by trying to authorize access to the Plesk database using the password provided.