[Bug 599342] [NEW] Temporary failure in name resolution

[Robert Sander]

Public bug reported:

libvirt-bin is not started correctly.

It tries to resolve the hostname when starting but at that time ther eis
no network and no DNS available. It fails with error 6 and starts again
immediately. After several attempts init disables the job completely:

Jun 28 14:33:05 natta libvirtd: 14:33:05.885: error : virGetHostname:1838 : internal error getaddrinfo failed for 'natta': Temporary failure in name resolution
Jun 28 14:33:05 natta init: libvirt-bin main process (1332) terminated with status 6
Jun 28 14:33:05 natta init: libvirt-bin main process ended, respawning
Jun 28 14:33:05 natta libvirtd: 14:33:05.892: error : virGetHostname:1838 : internal error getaddrinfo failed for 'natta': Temporary failure in name resolution
Jun 28 14:33:05 natta init: libvirt-bin main process (1338) terminated with status 6
Jun 28 14:33:05 natta init: libvirt-bin respawning too fast, stopped

We have removed the "bogus" hostname entry from /etc/hosts poiting to a
127.0.0.2 address. Our network DNS resolves hostnames to their "real" IP
addresses.

If libvirt-bin needs to resolve a hostname to an IP address it should
wait for the network when starting.

The libvirt-bin upstart script may need a dependency.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libvirt-bin 0.7.5-5ubuntu27
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32.11-epi+drm33.2 x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Jun 28 14:34:41 2010
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LANGUAGE=
SourcePackage: libvirt

** Affects: libvirt (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug lucid

-- 
Temporary failure in name resolution
https://bugs.launchpad.net/bugs/599342
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.