My thoughts...
On 9/23/2009 10:09 PM, William Attwood wrote:
> [Wed Sep 23 21:42:25 2009] [error] [client xx.xx.xx.xx] proxy: DNS lookup
> failure for: web1. domain.com returned by /file.php
>
Is the web1.domain.com actually having to be resolved by a DNS server?
Maybe the DNS server is being overloaded. Try putting the
web1.domain.com in the /etc/hosts file.
> [Wed Sep 23 21:42:47 2009] [error] (70007)The timeout specified has expired:
> proxy: HTTP: attempt to connect to 10.3.1.30:80 (web1. domain.com) failed
> [Wed Sep 23 21:42:47 2009] [error] ap_proxy_connect_backend disabling worker
> for (web1. domain.com)
This would seem to imply that your web1 server did not respond to the
proxy in a timley manner. Is your web1 server overloaded? Do you have
a buggy, or overloaded, application that is having difficulties in
responding within 300 seconds? What is the your ProxyTimeout directive
set to? If ProxyTimeout is not set, what is your Apache TimeOut value
set to?
The other possibility, if you are getting a lot of traffic, is you have
hit some of the default connection limits.
Which version of apache are you running?
Which distribution are you using and which kernel version?
What are your max file descriptors set to: (includes sockets)
/sbin/sysctl fs.file-max
What are your current file descriptor limit set to: (includes sockets)
ulimit -n
Kenneth
/*
PLUG: http://plug.org, #utah on irc.freenode.net
Unsubscribe: http://plug.org/mailman/options/plug
Don't fear the penguin.
*/
