« You Turned the Tables on Me2001 »

Apache error

01/18/03 | by david2 [mail] | Categories: Geek
When you get :

[warn] (128)Network is unreachable: connect to listener

Then...

I was getting these on Solaris 8 also. I found something on the web that
mentioned it was trying to use IPv6. I compiled apache with --disable-ipv6
and it seemed to fix it.
Permalink

4 comments

Comment from: ukon [Visitor]
thanks for the headup
04/07/03 @ 23:36
Comment from: John Harrison [Visitor]
I saw what you wrote here and tried adding this to the bottom of /etc/hosts instead:

# The following lines are desirable for IPv6 capable hosts
# (added automatically by netbase upgrade)

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

That fixed it too, and was a lot quicker and easier than recompiling apache... :o)

If you look at: http://httpd.apache.org/docs-2.0/new_features_2_0.html
it says:
IPv6 Support
On systems where IPv6 is supported by the underlying Apache Portable Runtime library, Apache gets IPv6 listening sockets by default. Additionally, the Listen, NameVirtualHost, and VirtualHost directives support IPv6 numeric address strings (e.g., "Listen [fe80::1]:8080").

So I would say by the looks of it that Apache is trying to bind to localhost via IPv6 - and can't resolve it, once you tell it where to connect to it's happy :o)

Very cool blog BTW :o)
12/09/03 @ 13:32
Comment from: David [Visitor]
well, by damn, that did work -- shows where RTFM will get you
01/08/04 @ 08:52
Comment from: David [Visitor]
One more detail:

In Solaris 8 you might also have to enable ipv6. This is accomplished by:

touch /etc/hostname6.hme0
reboot
03/10/04 @ 00:30
February 2020
Sun Mon Tue Wed Thu Fri Sat
 << <   > >>
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29

Search

The requested Blog doesn't exist any more!

XML Feeds

blog soft