You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Greg Ames <gr...@remulak.net> on 2002/03/04 19:00:02 UTC

Re: Weird network problem with MPM_WORKER

Pier Fumagalli wrote:
> 
> I don't know why, but right now my server started complaining with:
> 
> [warn] (128)Network is unreachable: connect to listener
> 
> I just issued a "restart" and before it was working fine... Now, even if I
> shut it down and start it back again, the error_log is full with those...

When Apache 2.0 is restarted, we send ourselves a bunch of dummy connnections to
insure that every thread/process which is blocked in accept() wakes up if there
is little or no network traffic.  Those dummy connections are failing, so you
might have old generation processes that won't go away if you don't have much
traffic on your site.

There was a Solaris bug that caused a problem similar to this which was reported
a few weeks ago.  I think Jeff saw it, and fixed it by putting on the latest
Solaris fix packages.  I don't think anyone was able to identify one specific
fix.

Greg

Re: Weird network problem with MPM_WORKER

Posted by Jeff Trawick <tr...@attglobal.net>.
Pier Fumagalli <pi...@betaversion.org> writes:

> "Jeff Trawick" <tr...@attglobal.net> wrote:
> 
> > The Solaris fixes were required to fix a hang in getaddrinfo().
> 
> Yeah, looked at the archive and patched the whole baby before posting...
> Didn't change the behavior...
> 
> > When I had the same symptom as Pier mentions above, the fix was to get
> > my IPv6 configuration straightened out.  None of my network interfaces
> > had IPv6 addresses, so attempting to connect to :: (in6addr_any)
> > resulted in ENETUNREACH.
> 
> Haha! :) Gotcha. So it's an IPv6 problem :) I don't have anything configured
> in IPv6 ATM, so that might be as well my problem... I'll try to figure out
> how to configure those, but at the same time, it would be cool to have in
> the autoconf for httpd a placeholder for --disable-ipv6 in autoconf for APR
> (if that solves the problem, will try!)

by placeholder... you mean something like this?

AC_ARG_ENABLE(ipv6,
  [  --disable-ipv6          Disable IPv6 support in APR and Apache] )

-- 
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...

Re: Weird network problem with MPM_WORKER

Posted by Pier Fumagalli <pi...@betaversion.org>.
"Jeff Trawick" <tr...@attglobal.net> wrote:

> The Solaris fixes were required to fix a hang in getaddrinfo().

Yeah, looked at the archive and patched the whole baby before posting...
Didn't change the behavior...

> When I had the same symptom as Pier mentions above, the fix was to get
> my IPv6 configuration straightened out.  None of my network interfaces
> had IPv6 addresses, so attempting to connect to :: (in6addr_any)
> resulted in ENETUNREACH.

Haha! :) Gotcha. So it's an IPv6 problem :) I don't have anything configured
in IPv6 ATM, so that might be as well my problem... I'll try to figure out
how to configure those, but at the same time, it would be cool to have in
the autoconf for httpd a placeholder for --disable-ipv6 in autoconf for APR
(if that solves the problem, will try!)

    Pier


Re: Weird network problem with MPM_WORKER

Posted by Jeff Trawick <tr...@attglobal.net>.
Greg Ames <gr...@remulak.net> writes:

> Pier Fumagalli wrote:
> > 
> > I don't know why, but right now my server started complaining with:
> > 
> > [warn] (128)Network is unreachable: connect to listener
> > 
> > I just issued a "restart" and before it was working fine... Now, even if I
> > shut it down and start it back again, the error_log is full with those...
... 
> There was a Solaris bug that caused a problem similar to this which was reported
> a few weeks ago.  I think Jeff saw it, and fixed it by putting on the latest
> Solaris fix packages.  I don't think anyone was able to identify one specific
> fix.

The Solaris fixes were required to fix a hang in getaddrinfo().

When I had the same symptom as Pier mentions above, the fix was to get
my IPv6 configuration straightened out.  None of my network interfaces
had IPv6 addresses, so attempting to connect to :: (in6addr_any)
resulted in ENETUNREACH.
-- 
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...