Re: Not firewall, but what?

[Benjamin Franz <jfranz@xxxxxxxxxxx>]

On 05/06/2010 11:42 AM, Ryan Manikowski wrote:

Notice the op posted they get timeouts even when going directly to a numerical address (if the apache server is configured to respond to *:80 it should at least display something)

Try using telnet from a client machine that can not connect.

e.g. telnet host.name.here 80

or

telnet xx.xxx.xxx.xxx 80

Try a few times and see if you're getting a timeout or if it connects every time. Run tcpdump on the apache server while sending the connection requests and see if the connection attempts show up at all. If they do not, then it's a network problem.

Try running 'ab' (the apache bench tool - see 'man ab' for how to use it) against your server and see if you can provoke the timeouts. If you can, then you are probably not configured to handle many quick connections and should check (1) httpd.conf to make sure you don't have an excessively low setting for 'MaxClients' or (2) a too low setting for max open filehandles. Look in /etc/security/limits.conf - you should have a line reading something similar to:


*                -       nofile          64000


somewhere in it to raise the max number of open files. Busy web servers need lots of filehandles.

--
Benjamin Franz

-- 
Benjamin Franz

_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos