Get your server issues fixed by our experts for a price starting at just 25 USD/Hour. Click here to register and open a ticket with us now!

Author Topic: Command line utility for checking 12 known issues in Plesk.  (Read 2646 times)

0 Members and 1 Guest are viewing this topic.

Karun

  • Guest
Command line utility for checking 12 known issues in Plesk.
« on: December 09, 2013, 03:49:17 pm »

Command line utility for checking 12 known issues in Plesk.


Problem:
Web server configuration fails for websites and reconfiguring does not help. The reason for the failure is unclear and it is impossible to troubleshoot it.

Solution:

There is  a command-line tool called webserver_configuration_checker.php which  performs the same operations as the "Checker" tab of the Web Server Configurations Troubleshooter in Plesk 11 and above.  It can be downloaded and run from the console by means of the following commands:
 
#wget
http://kb.parallels.com/Attachments/23693/Attachments/webserver_configuration_checker.php
   
# /usr/local/psa/bin/sw-engine-pleskrun webserver_configuration_checker.php

The known issues include:

- Web server reconfiguration fails with error: "JkWorkersFile only allowed once"
- Unable to manage domains with "Forwarding" hosting type
- Parallels Plesk Panel generates empty domain-level Apache config files due to corrupted records in Parallels Plesk Panel database
- Reference between several subscriptions and APS applications has been broken
- Wrong order of loading Zend extensions/ionCube declaration in php.ini can cause to Apache fail
- Webserver (Apache/Nginx) configs regeneration fails because files with the same names as the   -Apache symlinks you are trying to create already exist
-Apache configs regeneration fails if vHost directories or system users are missing
-Apache fails to regenerate its configuration files due to incorrect vhosts_bootstrap.conf files
-Database records with empty "Name" field in Configurations table cause a fatal PHP error during -Apache reconfiguration
-Webserver reconfiguration fails with "Permission denied" error when SELinux is in enforced mode
-If there are more than 256 domains, Nginx fails with "Too many open files" error
-In some cases, extra webserver configuration files remaining after domain removal might cause conflicts at webserver configurations rebuild proccess