Facebook
TwitterAfter installing MU30, I can no longer access my control panel. Domains are working fine, so this issue only applies to the panel itself.
I tried all the KBs related to this issue and none have solved it. Except it switches between Bad Gateway and Gateway Timeout.
I see the following in the sw-cp-server error_log:
2015/01/12 16:17:58 [error] 24208#0: *27 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.0.2, server: , request: "GET /login.php3 HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock", host: "www.host.com:8443"
I changed the buffer and timeout values as proposed is some KBs and posts. I reinstalled the patch using the autoinstaller. The bootstrapper repair option seems to be "hanging" after:
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
At this stage I have no idea how to solve this.
I noticed that after the MU30, the following change was made to /etc/sw-cp-server/config
error_page 497 https://$hostname:$server_port$request_uri;
However, disabling this, does not solve it either.
Plesk 12.0.18 on CentOS release 5.11 (Final)
I tried all the KBs related to this issue and none have solved it. Except it switches between Bad Gateway and Gateway Timeout.
I see the following in the sw-cp-server error_log:
2015/01/12 16:17:58 [error] 24208#0: *27 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.0.2, server: , request: "GET /login.php3 HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock", host: "www.host.com:8443"
I changed the buffer and timeout values as proposed is some KBs and posts. I reinstalled the patch using the autoinstaller. The bootstrapper repair option seems to be "hanging" after:
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.
Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative APS controller database (apsc) upgrade and repair has been started.
===> Cumulative upgrade and repair of APS controller database has been completed.
At this stage I have no idea how to solve this.
I noticed that after the MU30, the following change was made to /etc/sw-cp-server/config
error_page 497 https://$hostname:$server_port$request_uri;
However, disabling this, does not solve it either.
Plesk 12.0.18 on CentOS release 5.11 (Final)
