gary lim wrote:I knew you would say that, but that doesn't change what I suggested. It's like the situation where someone has suspected flaky hardware (e.g. bad RAM), but they can't reboot the server to run memtest86 because it's production. It won't get you any closer to a solution when you can't test all possible avenues, especially when it's very difficult to even replicate the issue consistently.
Hu justin,
1. Because its a production site, we are unable to disable the PHP modules/script......From the log output below, we are having difficulty to pinpoint the source of error. I just spent the last couple of hours to run through the pages and see if the log shows up any systematic error...unfortunately, wasn't able to replicate the source of problem causing the glibc issue. Not sure if this only happen during high loading....
--
Justin Pasher
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|