ID: 32002 Comment by: niteman dot es at gmail dot com Reported By: tlamay at cte1 dot com Status: No Feedback Bug Type: Unknown/Other Function Operating System: Windows 2003 PHP Version: 4CVS-2005-02-17 New Comment:
I had a Windows 2003 with apache 2.0.59 and php 5.0.5 (the machine was an Athlon 2800+ with 1GB of RAM) working fine. Since I needed more power for my web, I migrated the whole thing with the same configuration to a Dual Core AMD Opteron 1212 HE with 2GB of RAM and this issue started to happen. I think this could be related with the multiprocesor implementation over windows 2003, but it has a quite inconsistent behaviour (I couldn't reproduce the bug at my will). Right now I have switched from loading php as a module of apache to the traditional cgi aproach. I'll follow up the issue and post a comment both if the issue is fixed with the change or if it is not. No doubt to contact me if you need further testing on this. Sorry for my bad english. Kind Regards Previous Comments: ------------------------------------------------------------------------ [2007-02-02 01:42:52] bob at cave dot net This is not just an apache problem. I am using WebSite Pro under win2000 with php 4.x and get the same error. The website service dies, and the watchdog needs to restart it. ------------------------------------------------------------------------ [2006-12-23 02:49:40] vst at gamervision dot net OS: Windows XP Pro and Server 2003 PHP: 4.4.4 Apache: 2.23 CPU: AMD X2 4400+ RAM: 2GB DDR I have the same issue and consider it as CRITICAL. I tried it on many Windows systems and the same results. If I add 'Win32DisableAcceptEx' then I'm getting this issue. But I must use 'Win32DisableAcceptEx' because without it I'm getting some Winsock issues. I can't upgrade to PHP 5 because some of the parts in my side having MySQL connection issues with PHP 5. PLEASE!! PLEASE FIX IT ALREADY!! ------------------------------------------------------------------------ [2006-12-21 21:00:11] csaba at ai-media dot com Our configuration: Windows2003 Web Edition PHP 5.2, ZendOptimizer 3 Apache 2.2.3 Tomcat 5.5.17 To reproduce: this happens consistently on the Windows platform as long as Win32DisableAcceptEx is enabled in the Apache httpd.conf. Tested with Apache2.0.59, PHP 5.1.6 and PHP 5.2. We get "FATAL: erealloc(): Unable to allocate XXX bytes" in the Apache2 error log with 5.1.6 and no feedback to the user (could not connect to server), with 5.2 the user sees the same error message in the browser. There's an open issue in the Apache2 bug list here: http://issues.apache.org/bugzilla/show_bug.cgi?id=34664#c8 Comment 8 is particularly interesting: one of the Apache developers say they do not call erealloc. At this point (to me) it's not clear whether this is a PHP or an Apache bug, but it's definitely related to both. ------------------------------------------------------------------------ [2006-12-12 23:04:20] alex_25052 at hotmail dot com Same thing here. Tons of FATAL: erealloc(): Unable to allocate xxxx bytes I config is PHP 4.4.4 Apache 2.2.3 on Windows 2003 Xeon Dual web machine, 2Gb ram. Sometimes apache restarts by itself, sometimes it doesn't and i have to do it manualy Drives me nuts... :) ------------------------------------------------------------------------ [2006-12-03 12:53:49] levi_tedder at hotmail dot com I have installed PHP 5.2 on the server where I had this issue, and it seems to have fixed it. No fatal for 24 hours, but I will let you know if it reappears when traffic peeks (although traffic was not an issue when this happened). ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/32002 -- Edit this bug report at http://bugs.php.net/?id=32002&edit=1
