httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 46682] New: mod_proxy EAI_AGAIN DNS failure
Date Mon, 09 Feb 2009 17:26:42 GMT

           Summary: mod_proxy EAI_AGAIN DNS failure
           Product: Apache httpd-2
           Version: 2.2.11
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_proxy

I have an installation HTTPD running on a Mac OS X 10.5 system that uses
mod_proxy to front a Tomcat 6 installation.

Here's my httpd.conf excerpt for the virtual host:
    ProxyPass /hudson/ ajp://
    ProxyPassReverse /hudson/ ajp://

The proxy works fine, but after some amount of time (days), I start getting a
"502 GET /app/ error reporting a DNS failure for". Once it gets
in this state, I must stop and then restart Apache (a restart won't fix it).
While in this state, Tomcat is running fine as I can get directly to it with a
port 8080 reference.

I inserted log messages directly into the code and have determined that APR is
getting an EAI_AGAIN return value from getaddrinfo() after running for a while.
I inserted the messages into these files:
- modules/proxy/proxy_util.c
- srclib/apr/network_io/unix/sockaddr.c

I've verified that DNS calls are actually still working in other processes via
"host", etc. There are no other problems seen on this server
when it gets into this state.

Note that I've compiled and run Apache on Mac OS X 10.5.6 (latest). I've been
running Apache for many years on this server with no issues until I started
using mod_proxy with Tomcat.

My Apache ./configure is as follows. I built and run Apache on the same Mac
./configure \
--prefix=/usr/local/apache2 \
--enable-mods-shared=all \
--enable-proxy-balancer \
--enable-proxy-ajp \
--enable-proxy-http \
--enable-proxy-ftp \
--enable-proxy-connect \
--enable-proxy \
--enable-ssl \
--with-included-apr \
--enable-dav \
--with-berkeley-db=/usr/local/bdb \
--with-dbm=db4 \

It appears to me that Apache/mod_proxy is leaking memory somehow. I have not
been able to track down the leak, or identify a test case that will reliably
reproduce the problem.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message