I'm getting a whole load of these errors in my Apache (1.3.37) error log:
child pid 31650 exit signal Segmentation fault (11)
The pid is always different, of course.
I thought it was being caused by php, so I rolled back to 4.4.1 from 4.4.2, but that didn't make a difference.
I've got Zend Optimizer 3.0.1 and eAccelerator 0.9.5-rc1 installed. I originally had eAccelerator 0.9.4 installed and upgraded to 0.9.5-rc1 to see if that would help, but it didn't.
Does anybody have any ideas what could be causing this?
Full Version: "child pid xxxxx exit signal Segmentation fault (11)"
Drop back to Zend 2.6.2 or earlier.
QUOTE (Catalyst)
Drop back to Zend 2.6.2 or earlier.
Is this a known issue with Zend 3.x? I couldn't find anything about it on their website.
I did find this in the Zend Optimizer install doc, though:
QUOTE
Enable Versioning - Check that your PHP was compiled without the Enable Versioning setting. This can be checked by looking at the top part of the phpinfo() function and checking to see if a row called "--enable-versioning" exists in the Configure Command section - if it does exists the PHP should be compiled without this option.
My php is compiled with this switch, could this have something to do with it?
I'm going to try re-compiling php without it first, if that doesn't fix this issue I'll install Zend Optimizer 2.6.2.
Just experience talking ---- it's not something I've ever seen in print. 2.6.2 works, and anything higher has been nothing but a pain. ;-)
Ah, ok.
Well, like I said I'll try to recompile php without that switch first, then try the earlier version of Zend.
In either case I'll report back here when I'm done with that.
Well, like I said I'll try to recompile php without that switch first, then try the earlier version of Zend.
In either case I'll report back here when I'm done with that.
Ok...
First I recompiled php without the --enable-versioning switch. I was still getting the segfaults.
So then I uninstalled Zend Optimizer 3.0.1 and installed 2.6.2. I'm still getting the segfaults!
Any ideas about what else to look at?
I get a whole bunch of messages like this in the Apache error_log:
I also tried removing eAccelerator from php.ini and restarting Apache, but got the same errors.
If I remove Zend Optimizer altogether the errors go away, so it's something to do with that...
*** UPDATE ***
It appears that this error is gone now, about a minute after I restarted Apache there were no more errors. Maybe there were a couple of old Apache processes running that were hanging onto the old config? I dunno, but for the moment all is good. Well, related to this problem anyway. ;-)
First I recompiled php without the --enable-versioning switch. I was still getting the segfaults.
So then I uninstalled Zend Optimizer 3.0.1 and installed 2.6.2. I'm still getting the segfaults!
Any ideas about what else to look at?
QUOTE
PHP 4.4.1 (cli) (built: Aug 8 2006 19:00:47)
Copyright © 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright © 1998-2004 Zend Technologies
with eAccelerator v0.9.5-rc1, Copyright © 2004-2006 eAccelerator, by eAccelerator
with Zend Extension Manager v1.0.9, Copyright © 2003-2006, by Zend Technologies
with Zend Optimizer v2.6.2, Copyright © 1998-2006, by Zend Technologies
Copyright © 1997-2004 The PHP Group
Zend Engine v1.3.0, Copyright © 1998-2004 Zend Technologies
with eAccelerator v0.9.5-rc1, Copyright © 2004-2006 eAccelerator, by eAccelerator
with Zend Extension Manager v1.0.9, Copyright © 2003-2006, by Zend Technologies
with Zend Optimizer v2.6.2, Copyright © 1998-2006, by Zend Technologies
I get a whole bunch of messages like this in the Apache error_log:
QUOTE
[Tue Aug 8 19:15:22 2006] [notice] child pid 23793 exit signal Segmentation fault (11)
[Tue Aug 8 19:15:22 2006] [notice] child pid 23794 exit signal Segmentation fault (11)
[Tue Aug 8 19:15:22 2006] [notice] child pid 23794 exit signal Segmentation fault (11)
I also tried removing eAccelerator from php.ini and restarting Apache, but got the same errors.
If I remove Zend Optimizer altogether the errors go away, so it's something to do with that...
*** UPDATE ***
It appears that this error is gone now, about a minute after I restarted Apache there were no more errors. Maybe there were a couple of old Apache processes running that were hanging onto the old config? I dunno, but for the moment all is good. Well, related to this problem anyway. ;-)
Yeah, it was probably realated to stuck sessions, which got cleaned up after a minute.
Zend's pretty hardcore ... Things drastically change between point releases, and screw anyone who's written an extension --- they have to re-write it, period. It's amazing anything at all runs with the Optimizer these days.
Zend's pretty hardcore ... Things drastically change between point releases, and screw anyone who's written an extension --- they have to re-write it, period. It's amazing anything at all runs with the Optimizer these days.
Nice.
Well, the important thing is I got it working again...
One other thing I noticed. There were hundreds of "wrk" files hanging around the tmp directory from mod_gzip. They weren't getting deleted, I'm assuming because the Apache processes kept crashing. Now that the segfault problem is gone, these wrk files are being cleaned up by Apache (like they should).
Well, the important thing is I got it working again...
One other thing I noticed. There were hundreds of "wrk" files hanging around the tmp directory from mod_gzip. They weren't getting deleted, I'm assuming because the Apache processes kept crashing. Now that the segfault problem is gone, these wrk files are being cleaned up by Apache (like they should).
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.