DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34664>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34664 ------- Additional Comments From [EMAIL PROTECTED] 2007-03-05 11:15 ------- Hi all, Oh, how I hope someone can give us a clue on what to do with this. Here's what we've been doing to try to isolate the problem. 1) We thought SSL might be the problem, so we took it out of the equation by setting up a new web server to take all the SSL connection, and reconfigured Apache on our production servers to only listen on port 80. No noticeable changes or improvement. 2) We purchased a shiny new web server from Dell. Quad core CPU (2.33 Ghz), 4 GB RAM. Very fast, and should be more than adequate for a simple web server. Same configuration as our other servers. Apache (or PHP, we still don't know which) dies just as happily: Fatal error: Out of memory (allocated 0) (tried to allocate 2 bytes) in Unknown on line 0 [Mon Mar 05 02:44:04 2007] [notice] Parent: child process exited with status 4294967295 -- Restarting. We watched the server closely, and when these errors happen, the CPU is low, the number of active connections is low, and there's over 2 GB of physical memory available. It's running out of *SOMETHING*, we just don't know what. It always, very reliably runs out of this something. The higher the threads, the faster (it seems). But, at least we had 3 servers serving up 128 threads each, which was temporarily acceptable. 3) We are running 7 websites, only one of which uses PHP. So we directed the 6 websites to just one server and we opened up the threads to 512, and that machine has been running without a hitch ever since. So it's just Apache + Tomcat. Hooray! Go Apache! This points to the problem definitely being in PHP, or the integration of PHP + Apache. (Please, don't send us away to go and post it on the PHP bug list just yet... All they are going to do is mark it as bogus.) 4) We updated to Apache 2.2.4. No noticeable difference unfortunately. The problem is, the traffic on the one site that uses PHP is steadily increasing. (It feels weird calling this a problem :-)) We upgraded our staging server to 2 GB of RAM, so it's the same specs as the others, and now 3 production servers are serving up just that one site. In addition we restart Apache daily. It worked fine for a while, but now it's getting worse: even with just serving 128 threads, and restarting the whole service daily (we have the redundancy for it), the above error is starting to present itself more and more frequently... I didn't mention yet that we tried for over a week to reliably reproduce this problem on our staging server, but we simply cannot. Our conclusion was that it's because when we send load to it (much bigger loads than what we normally get on production), it's all coming from the same IP. Whereas normal traffic comes from all over the place, different IPs, different browsers. We've looked at this so much already and running out of ideas and options. Help please? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
