Forum OpenACS Development: 20 seconds delay after ad_returnredirect on AOLServer 4.5 / OpenACS 5.4?

1: 20 seconds delay after ad_returnredirect on AOLServer 4.5 / OpenACS 5.4?

Posted by Frank Bergmann on 03/26/09 05:00 PM

Hi,

I'm getting a delay of about 20 second after ad_returnredirect, before my browser redirects to the right page. It only happens during the first redirect.

I'm sure I've already fixed this issue some years ago, but I'm searching through forums since two hours now and haven't found anything...

I've connected to the server via telnet and got the same output as with aolserver3.3/OpenACS 5.1...

Connected to www.project-open.net.
Escape character is '^]'.
GET /
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML>
<HEAD>
<TITLE>Redirection</TITLE>
</HEAD>
<BODY>
<H2>Redirection</H2>
<A HREF="http://www.project-open.net/intranet/index">The requested URL has moved here.</A>
<P ALIGN=RIGHT><SMALL><I>AOLserver/4.5.0 on http://koeln.project-open.net:8000</I></SMALL></P>

</BODY></HTML>
Connection closed by foreign host.

Thanks a lot!
Frank

2: Re: 20 seconds delay after ad_returnredirect on AOLServer 4.5 / OpenACS 5.4? (response to 1)

Posted by Brian Fenton on 03/27/09 12:34 AM

Hi Frank,

I wonder if it happens if you try ns_returnredirect? That way you will be able to determine if it's an AOLserver or OpenACS issue.

cheers
Brian

3: Re: 20 seconds delay after ad_returnredirect on AOLServer 4.5 / OpenACS 5.4? (response to 1)

Posted by Gustaf Neumann on 03/27/09 08:26 AM

Upgrade to 4.5.1; if this does not help, one has to go through your configuration parameters.

4: Re: 20 seconds delay after ad_returnredirect on AOLServer 4.5 / OpenACS 5.4? (response to 1)

Posted by Frank Bergmann on 03/27/09 04:18 PM

Hi,

I knew I knew this problem. A 20/30 second delay is _always_ the DNS.

This time it was a bit more tricky: Using wget with the -S option, I was able to track down the delay to Pound on the server side. And running Pound with the -v option I could see a "gethostbyname(projop.dnsalias.com): Host name lookup failure".

And the reason for this failure is that I run Pound in a root jail, so that Pound can't access the normal /etc/resolv.conf. So I had to fix /var/pound/etc/resolv.conf, and that's it.

Thanks for your replies!
Frank