Urgent: Pages causing seg fault

Anon

I'm using php3.0.9 loaded as a dynamic module with MySQL enabled. I think those where the only config options made. I'm also using apache 1.3.12 as downloaded as rpm from redhat 6.2. The box is a RH 6.1 i386. Here is the error that I am receiving.

[Mon Aug 14 16:55:11 2000] [notice] child pid 1056 exit signal Segmentation fault (11) [Mon Aug 14 16:55:39 2000] [notice] caught SIGTERM, shutting down [Mon Aug 14 16:55:39 2000] [warn] Loaded DSO modules/libphp3.so uses plain Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI) [Mon Aug 14 16:55:39 2000] [notice] Apache/1.3.12 (Unix) (Red Hat/Linux) PHP/3.0.9 configured -- resuming normal operations

I've tried to use some of the available rpms, and I've tried upgrading to php4.0, the configure script for php 4.0 dies checking for pthreads and none of the rpms out there have helped the situation at all. This server is used for some custom intranet apps. It does not crash on all PHP pages, but the most important ones are causing the crash.

Please get back to me as soon as you can. I need to have this situation resolved quickly or my butt's in a sling.

Thanks and sorry for the length.

Rich

Anon

I came across a problem similar to this and it turned out that improper use of the PHP contactenation operator was causing it. Apache would seg fault whenever it came across something like this:

$var . = "some text";

Note the space in between the period and the equal sign. Do a search to see if this occurs anywhere in your scripts as this is a possible cause. No idea why it seg faults on this but it happened to me. I believe someone on our dev team submitted a bug report to the PHP team some time ago but I don't think he ever heard back from them so I don't have any definitive answers at the moment. Hope it is that simple!

Anon

Nope, that wasn't it. I think I'm starting to see what is going on. I've been playing with the app for a while, trying different things, now I'm getting a FATAL error from emalloc() as follows.

FATAL: emalloc(): Unable to allocate 2159148406 bytes
[Mon Aug 14 20:25:33 2000] [notice] child pid 4757 exit signal Segmentation fault (11)

It appears as though this is the problem although I have no idea why. Anyone have any ideas?

Anon

FATAL: emalloc():
Unable to allocate 2159148406 bytes

It appears as though this is the
problem although I have no idea why.

2,159,148,406 bytes seems like an awful lot of memory for a php script to allocate. What is your script trying to do? It is unlikely you would have enough resources to handle scripts that are that demanding... or am I crazy?

Anon

Thats what I thought too. I don't know what is going on. The section that seems to be causing the problem is just setting a block in a template (the phplib version). There are 85 items and about 9 vars being replaced. Two of them with values accessed from disk. It seems to be choking on the last var, but I don't know why at this point. I know it's not the amount of items 'cause I have other apps that use more than that in a block, although with fewer variables. Right now I'm at a loss as to what to do. The part that is choking the system isn't necessary, but is a nice thing to have. If anyone has any ideas, let me know.

Anon

Richard

Your original post has mention of the php3 module being compiled against the API whereas your apache is EAPI. You need to rebuild your php3 module.

Regards

Anon

I have had this same problem.
In first situation I had run php4 mod to open php3 and php4, but some aplications doesn't want it, so I add php3 3.0.18, and problem with seg fault's starts for me , I tried many thins, it's was only problem with one script (Twig web mail)
I resolve it by direcitive for only this script :
<Directory /usr/local/share/doc/apache/twig>
AddType application/x-httpd-php .php3
</Directory>

Maybe you may change php version on add new.
if you have php3 use php4 only for yours favorite places.

Best Regards
siedar

Richard Wallace wrote:

I've tried to use some of the available rpms, and I've tried upgrading to php4.0, the configure script for php 4.0 di....