*** glibc detected *** double free or corruption

[WindyT]

Occasionally, I'll get a steep spike in load due to apache process, and had one this morning.
Restarting Apache often gets rid of the problem.

Pulling up the apache error_log for the time period, there's only one item that stands out:

[Mon Jul 24 07:50:10 2006] [error] [client 207.46.98.48] File does not exist: /home/myclient/public_html/404.shtml
*** glibc detected *** double free or corruption (!prev): 0x0a3b4950 ***

exim: SIGTERM received - message abandoned
[Mon Jul 24 07:51:22 2006] [warn] pid file /usr/local/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Jul 24 07:51:22 2006] [notice] Apache/1.3.36 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 PHP/4.4.2 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.27 OpenSSL/0.9.7a configured -- resuming normal operations
[Mon Jul 24 07:51:22 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Mon Jul 24 07:51:22 2006] [notice] Accept mutex: sysvsem (Default: sysvsem)

I did restart apache either during the time of this error log or shortly thereafter.

In previous threads, users were requested to post the results of
php -v
and mine is:

PHP 4.4.2 (cli) (built: May 25 2006 03:08:50)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies

The "myclient" website the initial error was tacked onto: After looking at the access logs, the only thing to note is that msnbot was cruising that site at the time. That website/user is particularly unremarkable and the webmaster is one of my partners.

Separately, I did have a PHP based mailer program working on another website at the time (PHPList)

Any ideas on this? Is this a Zend thing, or httpd.conf thing?

[sumith]

The issue is something related with buggy php modules. Do a php recompilation without "versioning" and check the results.

[DigitalN]

Yep,

I'm having the same issue on centos 4.3

This is with compiling php5 - I even tried compiling manually, with no options other than apxs and --prefix=
No Zend, no additional modules. Apache will not even start, just get the glibc error in the logs.

So if its a php module that is causing it, then its in the core of php, at least with 5.1.4

I have been able to compile php with no issues on other centos 4.3 boxes, but did get a problem with zend 3.0, which got resolved with 3.0.1 - but the latest problem has got me stumped.

[WindyT]

Yep,

I'm having the same issue on centos 4.3

This is with compiling php5 - I even tried compiling manually, with no options other than apxs and --prefix=
No Zend, no additional modules. Apache will not even start, just get the glibc error in the logs.

So if its a php module that is causing it, then its in the core of php, at least with 5.1.4

I have been able to compile php with no issues on other centos 4.3 boxes, but did get a problem with zend 3.0, which got resolved with 3.0.1 - but the latest problem has got me stumped.

Just now getting back after a vacation.

Thanks. Forgot to mention I'm running CentOS 4.3 but you guessed it.

I wish I knew more on this. Thanks all!

[HostMerit]

We had the same issue where nothing would load.

This seemed to be caused by Zend Optimizer 3.0, we fixed the problem by installing Zend Optmizer 2.6.2 as opposed to 3.0

root@energy [~]# php -v
PHP 4.4.2 (cli) (built: Jul 28 2006 22:16:52)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
with Zend Extension Manager v1.0.9, Copyright (c) 2003-2006, by Zend Technologies
with Zend Optimizer v2.6.2, Copyright (c) 1998-2006, by Zend Technologies

[kris1351]

Recompiling Apache using php 4.4.2 and upgrading Zend to 3.0.1 fixed the problem for me.

[PbG]

I agree. I just recompiled PhP 4.4.2 with Zend 3.01 to correct the following error. Php versions 5.1.6, and 4.4.4 would not work with versioning. I did not test 4.4.3 with or without versioning.

(*** glibc detected *** free(): invalid pointer error.


Thanks for sharing.

We had the same issue where nothing would load.

This seemed to be caused by Zend Optimizer 3.0, we fixed the problem by installing Zend Optmizer 2.6.2 as opposed to 3.0

root@energy [~]# php -v
PHP 4.4.2 (cli) (built: Jul 28 2006 22:16:52)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
with Zend Extension Manager v1.0.9, Copyright (c) 2003-2006, by Zend Technologies
with Zend Optimizer v2.6.2, Copyright (c) 1998-2006, by Zend Technologies