[BlueOnyx:22568] Re: Odd Wordpress issue

Michael Stauber mstauber at blueonyx.it
Sun Dec 23 22:48:16 -05 2018


Hi Don,

> /var/log/httpd/error_log
> [Sun Dec 23 19:08:42.892735 2018] [core:error] [pid 6765] [client
> 172.241.112.92:65032] End of script output before headers: index.php
> [Sun Dec 23 19:14:40.902367 2018] [core:error] [pid 6766] [client
> 172.241.112.92:65418] End of script output before headers: index.php
> Dec 23 19:23:36 [servername] kernel: php-cgi[7665]: segfault at
> 7fff041bdff8 ip 00000000008069ae sp 00007fff041be000 error 6 in
> php-cgi[400000+a67000]

Yeah, that is pretty odd all things considered. Which PHP implementation
are you using? Is it suPHP or PHP-FPM? Sounds like it is suPHP.

What happens here is this: You visit the site and the index.php starts
processing. But while doing so, PHP dies with a segmentation fault even
before any output was rendered and even before even the headers of an
HTML page had been sent to the browser.

Apache doesn't take this very well and shows a generic error message in
the browser, but the logs tell us what the real culprit was: The
segmentation fault.

Now this is a bitch to diagnose further, as we don't really know why
your PHP-5.6.24 craps out with Wordpress. It might not even be Wordpress
itself that causes the issue, but maybe it is a certain plugin that
causes the crash.

So if you still have access to the wp-admin page then you could try to
disable all plugins and see if the index page loads. Just to check if
it's plugins or Wordpress in general.

The next recommendation would be to try the latest PHP-5.6, which is
5.6.39. You're fairly well behind there and there have been a plethora
of fixes in the 5.6 code tree.

Another idea might be to try a different version of PHP altogether. Such
as PHP-7.0, 7.1 or 7.2. Or to switch from suPHP to PHP-FPM or vice versa.

Please give these things a try and see how it turns out.

-- 
With best regards

Michael Stauber



More information about the Blueonyx mailing list