Bug#629899: ap_get_local_host is broken (can't always determine the server's FQDN)
Hello Vincent On Wednesday 22 February 2012 03:39:38 Vincent Lefevre wrote: I'll try to do some tests when I have the time. But there's no reason eth0 would be IPv6 only here (unless there's a huge bug in the kernel). I'm prety sure your apache tries to start before dhclient has given the server its IPv4. And you'll have the local link IPv6 address already. The patch of libapr1 will fix your hostname problem: https://issues.apache.org/bugzilla/show_bug.cgi?id=52709 Basically, all loopback IPv4 resolution is broken while dhclient is running the first time, that is when you have IPv6 on eth0 but no IPv4 on it yet. Then libapr1 internal function call_resolver is wrongly using AI_ADDRCONFIG so that loopback IPv4 addresses are ignored. That is why a manual restart (after dhclient completed) works. I did understand your apache starts. Because you probably Listen 80 rather than Listen 127.0.1.1:80. 127.0.1.1 resolution would fail then, just like the resolution of ypig in your case. I tested it yesterday. Believe me, the source of your problems are in libapr1, not in apache2 packages, nor in the kernel. Je te parie une bierre si tu veux! ;) signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#629899: ap_get_local_host is broken (can't always determine the server's FQDN)
Processing commands for cont...@bugs.debian.org: retitle 629899 ap_get_local_host fails when eth0 has IPv6 only (can't determine the FQDN), e.g. with DHCP at boot Bug #629899 [apache2.2-common] ap_get_local_host is broken (can't always determine the server's FQDN) Changed Bug title to 'ap_get_local_host fails when eth0 has IPv6 only (can't determine the FQDN), e.g. with DHCP at boot' from 'ap_get_local_host is broken (can't always determine the server's FQDN)' thanks Stopping processing here. Please contact me if you need assistance. -- 629899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132993026621151.transcr...@bugs.debian.org
Bug#629899: ap_get_local_host is broken (can't always determine the server's FQDN)
One can reproduce that bug by having IPv6 only on eth0 and no other interface with IPv4 but localhost, and /etc/hosts matching `hostname` on any lo address. Call (forward) trace: ap_get_local_host apr_sockaddr_info_get find_addresses call_resolver getaddrinfo ... that fails since it is using AI_ADDRCONFIG flag on loopback interface This bug is actually the same as 500558. signature.asc Description: This is a digitally signed message part.
Bug#629899: ap_get_local_host is broken (can't always determine the server's FQDN)
retitle 629899 ap_get_local_host is broken (can't always determine the server's FQDN) thanks I'll try to do some tests when I have the time. But there's no reason eth0 would be IPv6 only here (unless there's a huge bug in the kernel). -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120222033938.gk7...@xvii.vinc17.org
Processed: Re: Bug#629899: ap_get_local_host is broken (can't always determine the server's FQDN)
Processing commands for cont...@bugs.debian.org: retitle 629899 ap_get_local_host is broken (can't always determine the server's FQDN) Bug #629899 [apache2.2-common] ap_get_local_host fails on loopback interface if eth0 has ipv6 only Changed Bug title to 'ap_get_local_host is broken (can't always determine the server's FQDN)' from 'ap_get_local_host fails on loopback interface if eth0 has ipv6 only' thanks Stopping processing here. Please contact me if you need assistance. -- 629899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132988198015945.transcr...@bugs.debian.org
Bug#629899: ap_get_local_host is broken (can't always determine the server's FQDN)
On 2012-02-22 02:58:04 +, Jean-Michel Vourgère wrote: This bug is actually the same as 500558. Actually the error I get is different from the one in 500558. Note that in my case, apache2 starts, but without being able to get the fqdn. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120222035036.gl7...@xvii.vinc17.org
Bug#629899: ap_get_local_host is broken
Hi, On 2012-02-19 01:12:17 +, Jean-Michel Vourgère wrote: I recently found some strange behavior in dns resolution at boot time, when eth0 has no ipv4 yet. (#500558) Do you use DHCP for your other interface (eth0)? Yes. What is the result of `grep CONCURRENCY /etc/init.d/rc' ? CONCURRENCY=makefile if [ none != $CONCURRENCY ] ; then test -s /etc/init.d/.depend.boot || CONCURRENCY=none test -s /etc/init.d/.depend.start || CONCURRENCY=none test -s /etc/init.d/.depend.stop || CONCURRENCY=none CONCURRENCY=none startpar -v /dev/null 21 || CONCURRENCY=none case $CONCURRENCY in CONCURRENCY=makefile if [ makefile = $CONCURRENCY ] if [ makefile = $CONCURRENCY ] Does the bug is still there if you set up a static ip address in /etc/network/interfaces for your eth0 interface? Like auto eth0 iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 gateway 192.168.0.1 I haven't tried. In any case, there's no reason to use eth0 (some machines do not even have an Ethernet card). -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120219112242.ga7...@xvii.vinc17.org
Bug#629899: ap_get_local_host is broken
tags 629899 + moreinfo thanks On Sunday 19 February 2012 11:22:42 Vincent Lefevre wrote: Does the bug is still there if you set up a static ip address in /etc/network/interfaces for your eth0 interface? I haven't tried. In any case, there's no reason to use eth0 (some machines do not even have an Ethernet card). I know it sounds stupid, but try it, please. The libapr1 resolver is known to fail for 127.0.0.1 if you have only ipv6 on eth0, like when dhclient hasn't finished yet. Race problem on boot. See http://bugs.debian.org/500558 signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#629899: ap_get_local_host is broken
Processing commands for cont...@bugs.debian.org: tags 629899 + moreinfo Bug #629899 [apache2.2-common] ap_get_local_host is broken (can't always determine the server's FQDN) Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 629899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132968917819836.transcr...@bugs.debian.org
Bug#629899: ap_get_local_host is broken
Hello I recently found some strange behavior in dns resolution at boot time, when eth0 has no ipv4 yet. (#500558) Do you use DHCP for your other interface (eth0)? What is the result of `grep CONCURRENCY /etc/init.d/rc' ? Does the bug is still there if you set up a static ip address in /etc/network/interfaces for your eth0 interface? Like auto eth0 iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 gateway 192.168.0.1 signature.asc Description: This is a digitally signed message part.
