Bug#629899: apache2: apr_sockaddr_info_get() failed / Could not reliably determine the server's FQDN
On Thu, 9 Jun 2011 19:27:23 +0200, Vincent Lefevre wrote:
On 2011-06-09 16:09:29 +0100, Massimo Manghi wrote:
On Thu, 9 Jun 2011 16:40:07 +0200, Vincent Lefevre wrote:
>On 2011-06-09 15:20:00 +0100, Massimo Manghi wrote:
>>It's probably so, because I don't see why apache2 is getting it
right
>>after the boot is over and you have gained access to the shell.
>>That's why I thought you were using dhcp at first.
>
>Yes, I confirm a possible problem with a recent libc or kernel at
>boot time, but this isn't related to DHCP.
I have no doubt: this has nothing to do with DHCP per se. DHCP was
useful to understand that gethostname (or uname) is not working
properly.
Actually I don't think this is the same bug. I cannot reproduce
this bug 629899 concerning apache2, while the bug with wwwoffle
has occurred every time since I upgraded to libc6 2.13.
OK. Wasn't this bug filed against apache2.2-common? Anyway I expect
every application based on apr calling apr_sockaddr_info_get to fail
with a similar reason.
>and with the kernel 2.6.39-1:
>
>Sun Jun 5 22:50:14 2011: Starting HTTP cache proxy server:
wwwoffled
>wwwoffled[5199] Warning: Failed to get name/IP address for host
'xvii'
>[No address associated with hostname].
>Sun Jun 5 22:50:14 2011: (offline mode) done.
After I looked in the logs, I got this actually for the first time
after I upgraded to libc6 2.13.
I've reported the wwwoffle problem against wwwoffle because apache2
on the same machine doesn't have any problem:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629923
wwwoffle may do something special, and the maintainer could reassign
the bug to libc6 (with a testcase) if it appears that the problem
comes from libc6.
I suggest that you report a bug for the problem you get. If you can
reproduce it, you'll have at least more information than me...
I would file it against libc6 because my conjecture is that different
components layered on libc6 are failing when they probably call
something
like uname or gethostname.
I cannot image what apr_* and tcsh have in common except for libc6
when
they are unable to determine the correct hostname.
Anyway, the bug seems not to be reproducible, not in a deterministic
way at least: tonight I booted my home machine and the hostname was
displayed
correctly. I'll keep an eye on it to see if it shows up again.
-- Massimo
Reply to: