• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

PHP5 FastCGI - FastCGI process exited unexpectedly

chris.dempsey

New Pleskian
We have Plesk 9.5.2 installed on Windows Server 2008 R2 and have an issue running websites as PHP5 via FastCGI. Simple functions such as phpinfo() and echo 'something' work fine but there is an issue using a mysql database with the mysql extension. I think specifically with the mysql_close() command but not 100% sure. The same issue appears to present with sites using PDO to connect to MySQL.

The server will return a HTTP Error 500.0 - Internal Server Error:
C:\Program Files (x86)\Parallels\Plesk\Additional\PleskPHP5\php-cgi.exe - The FastCGI process exited unexpectedly

The server is running MySQL 5.1.51 instead of 5.0.45 that Plesk ships with.

Windows Event Viewer shows:

Error:

Faulting application name: php-cgi.exe, version: 5.2.13.13, time stamp: 0x4b853880
Faulting module name: php5ts.dll, version: 5.2.13.13, time stamp: 0x4b853813
Exception code: 0xc0000005
Fault offset: 0x0000ac6a
Faulting process id: 0x31c
Faulting application start time: 0x01cc2dbcda3f65b9
Faulting application path: C:\Program Files (x86)\Parallels\Plesk\Additional\PleskPHP5\php-cgi.exe
Faulting module path: C:\Program Files (x86)\Parallels\Plesk\Additional\PleskPHP5\php5ts.dll
Report Id: 190ed077-99b0-11e0-9333-005056b6002b

Information:

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: php-cgi.exe
P2: 5.2.13.13
P3: 4b853880
P4: php5ts.dll
P5: 5.2.13.13
P6: 4b853813
P7: c0000005
P8: 0000ac6a
P9:
P10:

Other symptoms:
- PHP5 via CGI also throws an error for the same site:

HTTP Error 502.2 - Bad Gateway
The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "".

This does not create an entry in the Windows Event Viewer though.

More symptoms:
- PHP5 via ISAPI throws a PHP Access Violation Error. This only presents every 15-20 days and displays this error for all sites running PHP5 ISAPI. Resolution thus far has been to restart IIS. Engineers at the datacentre have made some tweaks to the Server but we've not waited long enough yet to see if the symptoms present again.

Can anyone advise if these issues could be caused by the upgrade from MySQL 5.0.45 to 5.1.51?

If not could anyone make a recommendation about how we can troubleshoot this to identify and correct the issue?

Thanks,

Chris
 
I looked back through my email history and according to correspondence with the engineers at the data centre the PHP5 FastCGI issue first presented one day after MySQL was updated from 5.0.45 to 5.1.51.

Coincidence? Or should the first thing we do be to roll back to the original version of MySQL.
 
Anyone got any thoughts they can add? Is there a chance that Plesk 9.5.2 is somehow incompatible with MySQL 5.1.51? The data centre have advised us not to roll back to MySQL 5.0.45 as this is likely to cause more issues.
 
Back
Top