|
Posted by Andy Hassall on 08/18/06 22:21
On 18 Aug 2006 15:08:33 -0700, "lawrence k" <lkrubner@geocities.com> wrote:
Re: the subject line:
http://www.google.co.uk/search?q=segmentation+fault
This first hit is informative.
>We made some changes to our server yesterday,
What changes did you make?
>and ever since, every
>single installation of WordPress that was on the server has stopped
>running. Other PHP scripts still run fine, but WordPress is dead.
OK, so you should reverse the changes you made.
And, this should serve as a lesson to make changes to a test server first,
assuming this is a server where the application is worth some amount of money
greater than zero.
>I logged into the server using ssh and looked the Apache error_log. The
>only thing there was a whole bunch of lines like this:
>
>[Fri Aug 18 18:00:25 2006] [notice] child pid 27827 exit signal
>Segmentation fault (11)
>
>I'm not finding any PHP errors that might tell me what is wrong with
>WordPress.
>
>Can anyone give me advice about what to do?
PHP should never suffer a segmentation fault; if it does, then there is
either:
(a) a bug in PHP
(b) a bug in a PHP extension
(c) a bug in a library loaded by PHP core
(d) a bug in a library loaded by a PHP extension
(e) something bizarrely wrong with your system as a whole
In any case:
http://bugs.php.net/how-to-report.php
And to make a bug report that is possible to act on, you need a backtrace to
identify what's causing the segfault:
http://bugs.php.net/bugs-generating-backtrace.php
Without this it's impossible to even guess what's wrong.
--
Andy Hassall :: andy@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Navigation:
[Reply to this message]
|