I see the same effect, just booted a Lucid EC2 instance and apache does not listen on ::1
In fact, I can't make it listen on ::1 explicitly with
Listen [::1]:80
Even though that exists on the loopback according to ip addr list/ifconfig. I get this error:
... waiting [Fri Sep 10 22:57:04 2010] [crit] (EAI 9)Address family for hostname not supported: alloc_listener: failed to set up sockaddr for ::1
Syntax error on line 9 of /etc/apache2/ports.conf:
But when I've added a routable ipv6 address it works fine!
Marking Confirmed.
Setting Importance to Medium. While ipv6 is not the norm now, We need to make sure we support IPv6 users/developers/etc. now, and this may signal something broken deeper down in the system.
Hi Loic,
I see the same effect, just booted a Lucid EC2 instance and apache does not listen on ::1
In fact, I can't make it listen on ::1 explicitly with
Listen [::1]:80
Even though that exists on the loopback according to ip addr list/ifconfig. I get this error:
... waiting [Fri Sep 10 22:57:04 2010] [crit] (EAI 9)Address family for hostname not supported: alloc_listener: failed to set up sockaddr for ::1 ports.conf:
Syntax error on line 9 of /etc/apache2/
But when I've added a routable ipv6 address it works fine!
Marking Confirmed.
Setting Importance to Medium. While ipv6 is not the norm now, We need to make sure we support IPv6 users/developer s/etc. now, and this may signal something broken deeper down in the system.