Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Categories

PHP crashing/restarting Apache - PLEASE HELP ME!!

faulkjfaulkj Member Posts: 2
So I upgraded the hard drive on my server installing Windows XP and the newest versions of Apache (2.0.51) and PHP (5.0.1) on the new drive. Everything was working out fine until I realized that several of my PHP scripts were not working with the new setup.

Unfortunately, I accidentally formatted the old hard drive, so now I can't go back and see what was different that worked on the old setup.

I know this: every PHP script that does serious file processing (either parsing a long file or cycling through something like 400 files) will cause Apache to crash and then restart. Sometimes repeatedly so that the browser loads halfway through the page over and over. Sometimes with smaller scripts, after several of these reloads the PHP will work and the page will load all the way. When I look at the Apache error log, I see this for each crash/restart (the child process # is different each time):


[Thu Sep 23 04:49:56 2004] [notice] Parent: child process exited with status 4294967295 -- Restarting.
[Thu Sep 23 04:49:59 2004] [notice] Parent: Created child process 3764
[Thu Sep 23 04:50:00 2004] [notice] Child 3764: Child process is running
[Thu Sep 23 04:50:00 2004] [notice] Child 3764: Acquired the start mutex.
[Thu Sep 23 04:50:00 2004] [notice] Child 3764: Starting 250 worker threads.

I've tried every combination of Apache 2.0.48 through 2.0.51 with PHP 4.3.3 through 5.0.1. I've tried changing all the timeout settings I could find in php.ini and httpd.conf. I've changed around all the fopen settings in php.ini. I'm 98% sure I hadn't changed around anything in php.ini with my old setup. I did have a lot of custom settings in httpd.conf, but would anything in there cause this??

I don't know what else to do. I'm desperate! Does anyone out there have any idea how to get my stuff working again??

Thanks,
Joshua

Comments

  • JonathanJonathan Member Posts: 2,914
    : So I upgraded the hard drive on my server installing Windows XP and the newest versions of Apache (2.0.51) and PHP (5.0.1) on the new drive. Everything was working out fine until I realized that several of my PHP scripts were not working with the new setup.
    :
    : Unfortunately, I accidentally formatted the old hard drive, so now I can't go back and see what was different that worked on the old setup.
    :
    : I know this: every PHP script that does serious file processing (either parsing a long file or cycling through something like 400 files) will cause Apache to crash and then restart. Sometimes repeatedly so that the browser loads halfway through the page over and over. Sometimes with smaller scripts, after several of these reloads the PHP will work and the page will load all the way. When I look at the Apache error log, I see this for each crash/restart (the child process # is different each time):
    :
    :
    : [Thu Sep 23 04:49:56 2004] [notice] Parent: child process exited with status 4294967295 -- Restarting.
    : [Thu Sep 23 04:49:59 2004] [notice] Parent: Created child process 3764
    : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Child process is running
    : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Acquired the start mutex.
    : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Starting 250 worker threads.
    :
    : I've tried every combination of Apache 2.0.48 through 2.0.51 with PHP 4.3.3 through 5.0.1. I've tried changing all the timeout settings I could find in php.ini and httpd.conf. I've changed around all the fopen settings in php.ini. I'm 98% sure I hadn't changed around anything in php.ini with my old setup. I did have a lot of custom settings in httpd.conf, but would anything in there cause this??
    :
    : I don't know what else to do. I'm desperate! Does anyone out there have any idea how to get my stuff working again??
    :
    PHP 5 is somewhat new, so do keep an eye out for newer releases to see if this gets fixed. Also look out for newer releases of Apache 2, though it has been around for somewhat longer and it sounds like a PHP issue. The hosting world is mostly still on Apache 1.3.x and PHP 4.x for a reason - they are stable. You may want to drop back to these, or certainly do so for PHP.

    If your script is doing some heavy processing, it's not blowing any kind of memory limit you put in place, perhaps? But causing Apache to restart is ugly, I'd expect the script just to fail...but it could be worth checking.

    Jonathan

    ###
    for(74,117,115,116){$::a.=chr};(($_.='qwertyui')&&
    (tr/yuiqwert/her anot/))for($::b);for($::c){$_.=$^X;
    /(p.{2}l)/;$_=$1}$::b=~/(..)$/;print("$::a$::b $::c hack$1.");

  • faulkjfaulkj Member Posts: 2
    : : So I upgraded the hard drive on my server installing Windows XP and the newest versions of Apache (2.0.51) and PHP (5.0.1) on the new drive. Everything was working out fine until I realized that several of my PHP scripts were not working with the new setup.
    : :
    : : Unfortunately, I accidentally formatted the old hard drive, so now I can't go back and see what was different that worked on the old setup.
    : :
    : : I know this: every PHP script that does serious file processing (either parsing a long file or cycling through something like 400 files) will cause Apache to crash and then restart. Sometimes repeatedly so that the browser loads halfway through the page over and over. Sometimes with smaller scripts, after several of these reloads the PHP will work and the page will load all the way. When I look at the Apache error log, I see this for each crash/restart (the child process # is different each time):
    : :
    : :
    : : [Thu Sep 23 04:49:56 2004] [notice] Parent: child process exited with status 4294967295 -- Restarting.
    : : [Thu Sep 23 04:49:59 2004] [notice] Parent: Created child process 3764
    : : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Child process is running
    : : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Acquired the start mutex.
    : : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Starting 250 worker threads.
    : :
    : : I've tried every combination of Apache 2.0.48 through 2.0.51 with PHP 4.3.3 through 5.0.1. I've tried changing all the timeout settings I could find in php.ini and httpd.conf. I've changed around all the fopen settings in php.ini. I'm 98% sure I hadn't changed around anything in php.ini with my old setup. I did have a lot of custom settings in httpd.conf, but would anything in there cause this??
    : :
    : : I don't know what else to do. I'm desperate! Does anyone out there have any idea how to get my stuff working again??
    : :
    : PHP 5 is somewhat new, so do keep an eye out for newer releases to see if this gets fixed. Also look out for newer releases of Apache 2, though it has been around for somewhat longer and it sounds like a PHP issue. The hosting world is mostly still on Apache 1.3.x and PHP 4.x for a reason - they are stable. You may want to drop back to these, or certainly do so for PHP.
    :
    : If your script is doing some heavy processing, it's not blowing any kind of memory limit you put in place, perhaps? But causing Apache to restart is ugly, I'd expect the script just to fail...but it could be worth checking.
    :
    : Jonathan
    :
    : ###
    : for(74,117,115,116){$::a.=chr};(($_.='qwertyui')&&
    : (tr/yuiqwert/her anot/))for($::b);for($::c){$_.=$^X;
    : /(p.{2}l)/;$_=$1}$::b=~/(..)$/;print("$::a$::b $::c hack$1.");
    :
    :


    it originally worked on Apache 2.0.4(?) and PHP 4.3.(?) where (?) means I don't know. that's why I tried so many different versions--to see if I could get the same combination as before. unfortunately, that didn't work...

    Joshua
  • JonathanJonathan Member Posts: 2,914
    : : : So I upgraded the hard drive on my server installing Windows XP and the newest versions of Apache (2.0.51) and PHP (5.0.1) on the new drive. Everything was working out fine until I realized that several of my PHP scripts were not working with the new setup.
    : : :
    : : : Unfortunately, I accidentally formatted the old hard drive, so now I can't go back and see what was different that worked on the old setup.
    : : :
    : : : I know this: every PHP script that does serious file processing (either parsing a long file or cycling through something like 400 files) will cause Apache to crash and then restart. Sometimes repeatedly so that the browser loads halfway through the page over and over. Sometimes with smaller scripts, after several of these reloads the PHP will work and the page will load all the way. When I look at the Apache error log, I see this for each crash/restart (the child process # is different each time):
    : : :
    : : :
    : : : [Thu Sep 23 04:49:56 2004] [notice] Parent: child process exited with status 4294967295 -- Restarting.
    : : : [Thu Sep 23 04:49:59 2004] [notice] Parent: Created child process 3764
    : : : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Child process is running
    : : : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Acquired the start mutex.
    : : : [Thu Sep 23 04:50:00 2004] [notice] Child 3764: Starting 250 worker threads.
    : : :
    : : : I've tried every combination of Apache 2.0.48 through 2.0.51 with PHP 4.3.3 through 5.0.1. I've tried changing all the timeout settings I could find in php.ini and httpd.conf. I've changed around all the fopen settings in php.ini. I'm 98% sure I hadn't changed around anything in php.ini with my old setup. I did have a lot of custom settings in httpd.conf, but would anything in there cause this??
    : : :
    : : : I don't know what else to do. I'm desperate! Does anyone out there have any idea how to get my stuff working again??
    : : :
    : : PHP 5 is somewhat new, so do keep an eye out for newer releases to see if this gets fixed. Also look out for newer releases of Apache 2, though it has been around for somewhat longer and it sounds like a PHP issue. The hosting world is mostly still on Apache 1.3.x and PHP 4.x for a reason - they are stable. You may want to drop back to these, or certainly do so for PHP.
    : :
    : : If your script is doing some heavy processing, it's not blowing any kind of memory limit you put in place, perhaps? But causing Apache to restart is ugly, I'd expect the script just to fail...but it could be worth checking.
    : :
    : : Jonathan
    : :
    : : ###
    : : for(74,117,115,116){$::a.=chr};(($_.='qwertyui')&&
    : : (tr/yuiqwert/her anot/))for($::b);for($::c){$_.=$^X;
    : : /(p.{2}l)/;$_=$1}$::b=~/(..)$/;print("$::a$::b $::c hack$1.");
    : :
    : :
    :
    :
    : it originally worked on Apache 2.0.4(?) and PHP 4.3.(?) where (?) means I don't know. that's why I tried so many different versions--to see if I could get the same combination as before. unfortunately, that didn't work...
    :
    Have you tried running the script from the command line using the PHP executable? Does it work there, or does it fail too? (If your script grabs stuff from the form data etc, you may need to make a special script to test it from the command line.) Is the crash dependent on the amount of data being processed? And did you have chance to check if there are any memory limiting settings?

    Just a few questions that hopefully might help narrow the problem down.

    Jonathan

    ###
    for(74,117,115,116){$::a.=chr};(($_.='qwertyui')&&
    (tr/yuiqwert/her anot/))for($::b);for($::c){$_.=$^X;
    /(p.{2}l)/;$_=$1}$::b=~/(..)$/;print("$::a$::b $::c hack$1.");

Sign In or Register to comment.