Bug#629899: apache2: apr_sockaddr_info_get() failed / Could not reliably determine the server's FQDN
On 2011-06-09 14:41:45 +0200, Massimo Manghi wrote:
> I've run into the same problem recently upgrading to Linux 2.6.38 on my
> home's computer. Symptoms are the shell prompt doesn't show the hostname
> I had assigned at install time, being the hostname displayed instead
> then one passed through dhcp by the router. A similar problem doesn't
> occur at work where we run our own dhcp server and names passed by dhcp
> match consistently the ones in /etc/hosts
>
> Could a possible explanation for the workaround you found a latency in
> the dhcp negotiation at boot time?
Here DHCP *must not* be used to determine the FQDN. It is specified
locally in the /etc/hosts file. This is important, in particular
because one may want to run local services depending on it even when
the external network is not available (the administrator may choose
to use DHCP for the FQDN, but should not be forced to).
> I mean that by the time apache2 is started the interface could be not yet
> configured and the name 'ypig' not yet assigned to it. By the time you
> manually restart apache2 the interface is most likely configured and the
> problem goes away.
>
> If my hypothesis is correct the bug should be filed against the kernel
> e/o the libc packages.
I tried to do an strace to see what was used by apache, but it didn't
succeed.
I have a laptop with the 2.6.39-1-amd64 kernel where DHCP is not used
and /etc/hosts is sufficient to determine the FQDN.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
Reply to: