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?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. hoping to be helpful -- Massimo On 06/09/2011 02:11 PM, Vincent Lefevre wrote:
Package: apache2.2-common Version: 2.2.19-1 Severity: normal After installing the new kernel 2.6.39-2-amd64 and rebooting, I got in /var/log/boot: Thu Jun 9 13:41:49 2011: Starting web server: apache2apache2: apr_sockaddr_info_get() failed for ypig Thu Jun 9 13:41:51 2011: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName Thu Jun 9 13:41:51 2011: . This error didn't occur with previous kernels, and doesn't occur after a manual restart with: /etc/init.d/apache2 restart My /etc/hosts contains: 127.0.0.1 localhost 127.0.1.1 ypig.lip.ens-lyon.fr ypig # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters and /etc/nsswitch.conf contains the line: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4