Hi,
For anyone facing the same issue:
We just installed Plesk 12 on some of our machines and noticed that WHMCS was no longer working. We got an "Internal Server Error", and the logs indicated that PHP was segfaulting:
[Fri May 16 12:31:14 2014] [error] mod_fcgid: process /var/www/cgi-bin/cgi_wrapper/cgi_wrapper(7983) exit(communication error), get unexpected signal 11
[Fri May 16 12:33:31 2014] [notice] child pid 5258 exit signal Segmentation fault (11)
[Fri May 16 12:31:13 2014] [warn] [client 10.0.0.1] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: https://www.X.nl/admin/login.php
[Fri May 16 12:31:13 2014] [error] [client 10.0.0.1] Premature end of script headers: login.php, referer: https://www.X.nl/admin/login.php
After some debugging I discovered using gdb that the issue was with ionCube loader. I dont understand how upgrading to Plesk 12 could have broken ionCube, but it did. There is also a somewhat related KB article, which is talking about the same issue: http://kb.parallels.com/en/5244.
As explained in the KB, the solution for me was to upgrade ionCube from the ionCube website, thus replacing the loader in the standard Debian 7 x64 package php5-ioncube-loader.
For anyone facing the same issue:
We just installed Plesk 12 on some of our machines and noticed that WHMCS was no longer working. We got an "Internal Server Error", and the logs indicated that PHP was segfaulting:
[Fri May 16 12:31:14 2014] [error] mod_fcgid: process /var/www/cgi-bin/cgi_wrapper/cgi_wrapper(7983) exit(communication error), get unexpected signal 11
[Fri May 16 12:33:31 2014] [notice] child pid 5258 exit signal Segmentation fault (11)
[Fri May 16 12:31:13 2014] [warn] [client 10.0.0.1] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: https://www.X.nl/admin/login.php
[Fri May 16 12:31:13 2014] [error] [client 10.0.0.1] Premature end of script headers: login.php, referer: https://www.X.nl/admin/login.php
After some debugging I discovered using gdb that the issue was with ionCube loader. I dont understand how upgrading to Plesk 12 could have broken ionCube, but it did. There is also a somewhat related KB article, which is talking about the same issue: http://kb.parallels.com/en/5244.
As explained in the KB, the solution for me was to upgrade ionCube from the ionCube website, thus replacing the loader in the standard Debian 7 x64 package php5-ioncube-loader.