Hello, When in doubt, you should always use "tail -f" on the log files:
1. "tail -f /var/log/messages" and watch the pound traffic 2. "tail -f /var/log/httpd/blah.log" and watch your back end traffic If pound is the culprit, then you will see a quick connection in #1 and a slow connection in #2. Of course, you should run these on separate machines, right? #1 is for the pound machine, and #2 is for one of your back end servers. If you see a slow connection in #2, then pound is having a hard time figuring out where to send packets. Maybe you have a bad ARP on your route for the second server? Are these two BEs on a DMZ, or are they solely behind a firewall? Where is pound? Also behind the firewall, or on the DMZ? If you see #1 fast and #2 fast, then you have a definite routing problem where the firewall is killing packets because it thinks they belong on the inside instead of the outside. There are a bunch of reasons that could be why this routing problem is occurring. PCRE will not help you with this problem. In some cases, I've heard of PCRE making pound slower. So, use that with a grain of salt. Another fun tool to use is "traceroute". Try that on your pound machine against one of your BE IP addresses. If you are running all of your servers on the DMZ, then you are likely encountering routing problems caused by the firewall. You are essentially using a drop-in firewall in your network and that is no good. The firewall would filter packets as they occur on the wire for every response, and in some cases, it will reflect the packets back because they can't be routed. I've seen this before in one of my configurations where we dropped in a firewall parallel to the pound server and it started to do the same thing that you describe. -- Jake > -----Original Message----- > From: Dave Steinberg [mailto:[email protected]] > Sent: Thursday, April 30, 2009 8:45 AM > To: [email protected] > Subject: Re: Pound is Slowing Down My Site [Pound Mailing List] > > Tim Dunphy wrote: > > Emilio, > > > > Thank you. This is the result of telnet: > > > > telnet> open 192.168.1.6 > > Trying 192.168.1.6... > > telnet: Unable to connect to remote host: Connection refused > > telnet> open web2 > > telnet: could not resolve web2/telnet: Name or service not known > > Telnet to port 80, not the default port. We're not actually interested > in whether or not you have telnet working! :-P > > > It should be noted that internal DNS is _mostly_ configured properly. > > Just make sure that the machine running pound can properly resolve > whatever is in your pound.cfg file. If you have IPs in your pound.cfg, > then its not a DNS issue. > > What happens if you type the pound machine's IP into your browser? > > Regards, > -- > Dave Steinberg > http://www.geekisp.com/ > http://www.steinbergcomputing.com/ > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
