I installed Pound-Current on a my system that already had pound
previously installed and was working excellently.  When I launch it now
and try to hit my website, the page just hangs on a blank white screen.
I believe it to be resolving to the website due to a few host header
redirects that show up as working, but alas no content appears on the
page.  I'm sure I've made some kind of mistake in installation.  Any
suggestions on things to look for? 
 
Thanks
Joel Johnston - Network Engineer / Web Developer 
402 W. Broadway, Suite 770 
San Diego, CA 92101 
Phone: 888-868-1391 Ext.8024
E-mail: j.johnston(at)financialaid.com 
CONFIDENTIALITY NOTICE: This communication and any accompanying
document(s) are privileged and confidential and are intended for the
sole use of the addressee(s). If you have received this transmission in
error, you are advised that any disclosure, copying, distribution, or
the taking of any action in reliance upon it is strictly prohibited.
Moreover, any such inadvertent disclosure shall not compromise or waive
the FinancialAid.com-client privilege as to this communication or
otherwise. If you have received this communication in error, please
immediately delete it and contact us at privacy(at)financialaid.com or by
telephone at 619-400-8000. Thank you. FinancialAid.com LLC

Look at the log....

On Tue, 17 Feb 2004, Joel Johnston wrote:
[...]

A large part of the problem is that the addresses that I'm using and are
failing to load the pages are not in the logs.  However, there are tons
of errors there to report.  Have a look see.

Straight from the logs.  Please help me understand what I'm seeing. 

[...]

The bad headers are probably not important.
The error read from .... means, I believe, that the there was a failure 
reading headers.  205.189.12.102 has made a request but is not
responding--at least that's my diagnosis.  Robert?

On Wed, 18 Feb 2004, Joel Johnston wrote:
[...]

On Wed, 2004-02-18 at 21:24, Dennis Allison wrote:[...]

The bad headers are (probably) safe to ignore - it is usually a problem
of some clients sending a header in the wrong character set. The header
is skipped but the request is processed normally.

The 'error reading from' is for clients that either timed-out or aborted
the connection midway through sending the request (such as a user
clicking on a link and closing the browser). This is harmless in itself.
You can try increasing the Client time-out to make sure you do not loose
requests because of a slow network.[...]

Well again the errors appearing in the logs aren't really indicative of
my actual problems.  The actual problem that the end user experiences is
a completely blank page.  If I go to one of our sites that has a
re-direct using host headers, I see the address change.  So, I know that
the initial request is getting through to the webservers, but it would
appear that nothing is coming back.  How do I troubleshoot this when its
not logging the errors?  Here is my config.

ListenHTTP 10.4.0.2,80
ListenHTTPS 10.4.0.2,443 /etc/certificates/cacert.pem
LogLevel 3
NoHTTPS11 1
CheckURL 0
UrlGroup ".*"
BackEnd 10.4.0.50,80,1
BackEnd 10.4.0.60,80,1
EndGroup



-----Original Message-----
From: Robert Segall [mailto:roseg(at)apsis.ch] 
Sent: Thursday, February 19, 2004 5:40 AM
To: pound(at)apsis.ch
Subject: RE: Pound-Current Timing Out?

On Wed, 2004-02-18 at 21:24, Dennis Allison wrote:[...]
failure [...]

The bad headers are (probably) safe to ignore - it is usually a problem
of some clients sending a header in the wrong character set. The header
is skipped but the request is processed normally.

The 'error reading from' is for clients that either timed-out or aborted
the connection midway through sending the request (such as a user
clicking on a link and closing the browser). This is harmless in itself.
You can try increasing the Client time-out to make sure you do not loose
requests because of a slow network.[...]

On Thu, 2004-02-19 at 18:10, Joel Johnston wrote:[...]

I don't know much about your application, but you may be running afoul
of Pound's host rewriting for redirection responses.

If your problem manifests itself on HTTP then please stick an instance
of tcpwatch between the browser and Pound and let us see the problematic
traffic. For HTTPS this won't help, but you could still use the
Mozilla/Firefox LiveHTTPHeaders to let us know what goes on the wire.[...]