Article ID: 113466, created on Mar 15, 2012, last review on Dec 13, 2015

  • Applies to:
  • Plesk 9.5 for Linux/Unix

Symptoms

When trying to access the Parallels Plesk Panel (PP) Control Panel interface, the following error is shown:

500 - Internal Server Error

Note: Make sure you check out the main article as well: #114882:[HUB] 500 - Internal Server Error

Cause

According to documentation for lighthttpd-1.4.13 that is used in PP 9.5.4, there is a known issue related to min/max-procs setting.
In short, the service refuses to work properly if min-procs is set to 0.
The problem was first noted in lighthttpd-1.3.14.

Resolution

PP has been patched so as not to be affected by the issue since the release of version 10. Thus, the recommended solution is to upgrade to the latest version.

Workaround

You may work around the issue by editing this file: /etc/sw-cp-server/applications.d/plesk.conf

This line should be changed:
"min-procs" => 0,
to:
"min-procs" => 1,

In this section:

$SERVER["socket"] == ":8443" {
include_shell "/usr/local/psa/admin/conf/ssl-conf.sh"
index-file.names = ("index.php")
server.document-root = "/usr/local/psa/admin/htdocs"
setenv.add-response-header = ( "X-UA-Compatible" => "IE=EmulateIE7")
accesslog.filename = "/usr/local/psa/admin/logs/httpsd_access_log"
mimetype.assign += (".png" => "image/png",
".jpg" => "image/jpeg",
".jpeg" => "image/jpeg",
".gif" => "image/gif",
".html" => "text/html",
".htm" => "text/html",
".js" => "text/javascript",
".css" => "text/css")
fastcgi.map-extensions = ( ".php3" => ".php" )
fastcgi.server = (
".php" => (
(
"socket" => "/usr/local/psa/tmp/sw-engine.sock",
"bin-path" => "/usr/bin/sw-engine-cgi -c /usr/local/psa/admin/conf/php.ini -d auto_prepend_file=auth.php3 -u psaadm",
"bin-username" => "root",
"max-procs" => 1,
"min-procs" => 1,
"idle-timeout" => 60,
"bin-environment" => (
"PATH" => "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"PHP_FCGI_CHILDREN" => "3",
"PHP_FCGI_MAX_REQUESTS" => "10"

Note: Do not forget to replicate all of your changes in the section for port 8880.

60d3e722783ac7177a2b4b4c13af4062 a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 6ef0db7f1685482449634a455d77d3f4 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF