Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
  1. Server setup
  2. The problem
  3. Diagnostic information
  4. What I've tried
  5. Specific Help needed

1. I have the following server setup:

(Running in a VM using Hyper-V)

Debian Squeeze

Linux 2.6.32-5-amd64

Apache2-mpm-prefork 2.2.16-6+squeeze10

PHP 5.3.3-7+squeeze14

This server is protected with the Suhosin Patch

Max Requests Per Child: 0 - Keep Alive: on - Max Per Connection: 100

Timeouts Connection: 300 - Keep-Alive: 15

Loaded Modules core mod_log_config mod_logio prefork http_core mod_so mod_alias mod_auth_basic mod_auth_digest mod_authn_file mod_authz_default mod_authz_groupfile mod_authz_host mod_authz_user mod_cgi mod_deflate mod_dir mod_env mod_mime mod_negotiation mod_php5 mod_reqtimeout mod_rewrite mod_setenvif mod_ssl mod_status

Wordpress 3.4.2 (Upgrading to 3.5 soon :)

2. The problem

When I restart the server (sudo shutdown -r now), going to any website page results in the following error from the web browser (in this case, Google Chrome, but other browsers also show the same error). This error can also occur an hour or so after all is working ok, seemingly randomly, which is my biggest concern as it means my server is not reliable:

No data received Unable to load the web page because the server sent no data. Here are some suggestions: Reload this web page later. Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without >sending any data.

3. Diagnostic information The apache error log contains the folowing entries:

[Fri Dec 14 22:23:27 2012] [notice] child pid 1955 exit signal Floating point exception (8)

[Fri Dec 14 22:23:27 2012] [notice] child pid 1956 exit signal Floating point exception (8)

[Fri Dec 14 22:23:29 2012] [notice] child pid 1957 exit signal Floating point exception (8)

[Fri Dec 14 22:23:30 2012] [notice] child pid 1958 exit signal Floating point exception (8)

[Fri Dec 14 22:23:32 2012] [notice] child pid 1959 exit signal Floating point exception (8)

[Fri Dec 14 22:23:32 2012] [notice] child pid 1960 exit signal Floating point exception (8)

[Fri Dec 14 22:23:34 2012] [notice] child pid 1961 exit signal Floating point exception (8)

[Fri Dec 14 22:23:34 2012] [notice] child pid 1962 exit signal Floating point exception (8)

4. What I've tried

a) I can 'fix' the website temporarily by resetting the server twice (resetting it once does not work) using the following commands. NB: the 'reload' option does not work, I have to use restart twice. However, the error can reoccur sometime later.

sudo /etc/init.d/apache2 restart sudo /etc/init.d/apache2 restart

b) I have tried disabling suhosin by uninstalling php5-suhosin, but a php info page still shows "This server is protected with the Suhosin Patch". I have tried putting Suhosin into simulation mode by creating a file /etc/php5/apache2/conf.d/suhosin.ini containing:

[suhosin] suhosin.simulation = On

The php info page shows the suhosin.ini file in the list of "Additional .ini files parsed" but the php info page still shows "This server is protected with the Suhosin Patch"

c) Increasing the PHP memory limit In /etc/php5/apache2/ :

; Maximum amount of memory a script may consume (128MB)


memory_limit = 512M

d) Disabling all Wordpress plugins, and going back to the default theme.

5. Specific help needed I would very much like help in debugging what is going on here. I am not sure how to determine what processes are in the Apache error log which are exiting "[notice] child pid 1955 exit signal Floating point exception (8)", or what is causing them to exit. And whether suhosin is part of the problem (and how to disable it if it is).

Thank you in advance for any advice or tips you can offer in helping me debug this.

share|improve this question
I'm suddenly getting this too after upgrading to 2.2.22 provided by Jason's Utter Ramblings Repo. Did you solve this? If so, maybe you can answer your own question... – Nic Cottrell Jan 21 '13 at 14:47
@NicholasTolleyCottrell This is still unresolved. I have not been able to detect the source of the problem yet. I will post here if I find a solution. – Toby Jan 21 '13 at 23:22
I have edited the original post to add that I am running the system under a Hyper-V VM. – Toby Jan 21 '13 at 23:57

Do you have the xdebug php extension enabled? I disabled it in my php configuration files and haven't had a similar crash since.

Update: the error is back so xdebug extension isn't the cause...

share|improve this answer
Thank you for the suggestion. I don't have xdebug installed. – Toby Jan 21 '13 at 23:27

You use php and I would look in that direction first, but it looks like that's what you're doing already. I did a quick search on the "exit signal Floating point exception" thing and apache+php comes up a lot. Maybe one of the php scripts is broken, either by design or a subtly corrupt file.

Keep eliminating php related things until the crashes stop, remove scripts/sites/plugins, re-download and re-install php packages and other related packages (including apache2).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.