I've been researching this problem for a couple of months now and each time I think I've figured it out the occurs again. So its about time I asked for some help/suggestions.
I maintain an enterprise-sized site on Ubuntu 9.04 kernel version 2.6.28-17-server running Apache 2.2.11 and our site runs under Drupal 5.18 (yes - its time to upgrade and we're in the process). The hardware is 16 core Intel with 48GB real RAM so it runs pretty well.
My problem is that we have ONE page that more often than not when requested the browser just sits there "waiting for . . ." and never completes.
I can find NOTHING that might be causing this. I have no corresponding errors in the apache2 error log, the virtual server site error log, the php error log and the access logs are constantly being scoured for issues. Other than several bots accessing (googlebot, Yahoo Slurp, Bingbot, and others) nothing looks out of the ordinary.
I'm thinking that there is an internal error that's causing Apache to give up and quit on that request and return nothing to the client.
Any thoughts from any web gurus out there to point me to other areas I can look or things that I can do to hopefully detect any anomalies? This is one elusive issue. Fortunately its not totally failing, just annoying the heck out of our users.
Andy ideas/suggestions GREATLY appreciated.![[nosmiley]](/data/assets/smilies/nosmiley.gif "[nosmiley] [nosmiley]")
I maintain an enterprise-sized site on Ubuntu 9.04 kernel version 2.6.28-17-server running Apache 2.2.11 and our site runs under Drupal 5.18 (yes - its time to upgrade and we're in the process). The hardware is 16 core Intel with 48GB real RAM so it runs pretty well.
My problem is that we have ONE page that more often than not when requested the browser just sits there "waiting for . . ." and never completes.
I can find NOTHING that might be causing this. I have no corresponding errors in the apache2 error log, the virtual server site error log, the php error log and the access logs are constantly being scoured for issues. Other than several bots accessing (googlebot, Yahoo Slurp, Bingbot, and others) nothing looks out of the ordinary.
I'm thinking that there is an internal error that's causing Apache to give up and quit on that request and return nothing to the client.
Any thoughts from any web gurus out there to point me to other areas I can look or things that I can do to hopefully detect any anomalies? This is one elusive issue. Fortunately its not totally failing, just annoying the heck out of our users.
Andy ideas/suggestions GREATLY appreciated.
