Bug#629899: apache2: apr_sockaddr_info_get() failed / Could not reliably determine the server's FQDN

[Massimo Manghi <massimo.manghi@unipr.it>]

On Thu, 9 Jun 2011 16:40:07 +0200, Vincent Lefevre wrote:
> On 2011-06-09 15:20:00 +0100, Massimo Manghi wrote:
> > On Thu, 9 Jun 2011 16:08:49 +0200, Vincent Lefevre wrote:
> > >Definitely not the kernel or libc, unless something wrong occurs
> > >at boot time.
> >
> > 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.

I looked up a possible bug already in the database against libc6 or the
kernel-image, but I haven't found any. I think the bug should have
'critical' as severity, since it can break applications started at
boot time that relay on the FQDN to work properly.

> On my laptop, on which I do not use DHCP when I'm at home, with the
> kernel 2.6.38-2:
>
> Thu Mar 31 21:53:49 2011: Starting HTTP cache proxy server: wwwoffled
> (offline mode) done.
>
> 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.
>
> and no problems with a manual restart.

If this is the case the kernel-image package must clearly be the targed
of the bug report.

Do you want to file it yourself? This bug (#629899) could be merged
later with it as soon as it's been registered in the database.

 -- Massimo