Status: New
Owner: ----
New issue 1289 by a...@laumi.org: When using localhost and ipv4+ipv6
stacks, ipv4 should get precedence on name-resolving
http://code.google.com/p/cherokee/issues/detail?id=1289
Ok, the scenario is:
1. ArchLinux, only stable repositories
2. Cherokee 1.2.100-1 and 1.2.101-1
3. cherokee-admin and all f/w/scgi sites that run on localhost connections
stop working.
Up until cherokee version 1.2.99-3 it all worked fine, and, if I downgrade
cherokee, it still works fine.
After reporting it to the ArchLinux mantainer of the package, he couldn't
reproduce the issue.
After searching here on code.google, I found a similar issue, that put me
on the right path:
http://code.google.com/p/cherokee/issues/detail?id=1145
It seems that having both ipv6 and ipv4 addresses to localhost causes the
issue.
My /etc/hosts files has the following lines:
127.0.0.1 localhost.localdomain localhost
::1 localhost.localdomain localhost
With thouse two lines, using cherokee 1.2.101, running:
cherokee-admin -b -u
And trying to connect to localhost:9090 times out (after a looong time)
with the 503 error.
If I comment out the line that has the ipv6 localhost address,
cherokee-admin starts to work as expected, and so do all the other f/w/scgi
sites using localhost connections.
Running the following commands on python:
import sys, socket
result = socket.getaddrinfo("localhost", None)
print result
yields the following results:
1- with ipv6 ::1 localhost still on /etc/hosts:
[.(10, 1, 6, '', ('::1', 0, 0, 0)), (10, 2, 17, '', ('::1', 0, 0, 0)), (10,
3, 0, '', ('::1', 0, 0, 0)), (2, 1, 6, '', ('127.0.0.1', 0)), (2, 2,
17, '', ('127.0.0.1', 0)), (2, 3, 0, '', ('127.0.0.1', 0))]
2- with ipv6 commented on /etc/hosts:
[.(2, 1, 6, '', ('127.0.0.1', 0)), (2, 2, 17, '', ('127.0.0.1', 0)), (2, 3,
0, '', ('127.0.0.1', 0))]
Since ipv6 isn't critical to me, I had no other issues comming from
commenting ipv6 localhost resolving, but others may have a problem with
that.
I'm not sure whether it is a cherokee issue or some os-dependent library's,
so, any help will be much appreciated.
Thanks!
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev
Owner: ----
New issue 1289 by a...@laumi.org: When using localhost and ipv4+ipv6
stacks, ipv4 should get precedence on name-resolving
http://code.google.com/p/cherokee/issues/detail?id=1289
Ok, the scenario is:
1. ArchLinux, only stable repositories
2. Cherokee 1.2.100-1 and 1.2.101-1
3. cherokee-admin and all f/w/scgi sites that run on localhost connections
stop working.
Up until cherokee version 1.2.99-3 it all worked fine, and, if I downgrade
cherokee, it still works fine.
After reporting it to the ArchLinux mantainer of the package, he couldn't
reproduce the issue.
After searching here on code.google, I found a similar issue, that put me
on the right path:
http://code.google.com/p/cherokee/issues/detail?id=1145
It seems that having both ipv6 and ipv4 addresses to localhost causes the
issue.
My /etc/hosts files has the following lines:
127.0.0.1 localhost.localdomain localhost
::1 localhost.localdomain localhost
With thouse two lines, using cherokee 1.2.101, running:
cherokee-admin -b -u
And trying to connect to localhost:9090 times out (after a looong time)
with the 503 error.
If I comment out the line that has the ipv6 localhost address,
cherokee-admin starts to work as expected, and so do all the other f/w/scgi
sites using localhost connections.
Running the following commands on python:
import sys, socket
result = socket.getaddrinfo("localhost", None)
print result
yields the following results:
1- with ipv6 ::1 localhost still on /etc/hosts:
[.(10, 1, 6, '', ('::1', 0, 0, 0)), (10, 2, 17, '', ('::1', 0, 0, 0)), (10,
3, 0, '', ('::1', 0, 0, 0)), (2, 1, 6, '', ('127.0.0.1', 0)), (2, 2,
17, '', ('127.0.0.1', 0)), (2, 3, 0, '', ('127.0.0.1', 0))]
2- with ipv6 commented on /etc/hosts:
[.(2, 1, 6, '', ('127.0.0.1', 0)), (2, 2, 17, '', ('127.0.0.1', 0)), (2, 3,
0, '', ('127.0.0.1', 0))]
Since ipv6 isn't critical to me, I had no other issues comming from
commenting ipv6 localhost resolving, but others may have a problem with
that.
I'm not sure whether it is a cherokee issue or some os-dependent library's,
so, any help will be much appreciated.
Thanks!
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev