[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] libvirt socket closed unexpectedly (code=39) & libvirt: Broken pipe (code=38)



On Sat, Aug 15, 2009 at 10:02:21AM -0700, dave c wrote:
> Hello everyone,
> 
> I'm trying to get eucalyptus v1.5.2 working on debian lenny 64bit, the
> relevant info I can give you is as follows:
> 
> --- libvirtd conf file ----
> 
> 01:/etc/libvirt# cat libvirtd.conf|grep -v '#'
> 
> unix_sock_group = "libvirt"
> unix_sock_rw_perms = "0770"
> auth_unix_ro = "none"
> auth_unix_rw = "none"
> 
> ---------------------
> 
> version of libvir installed on my server (cloud controller/cluster
> controller):
> 
> 01:/etc/libvirt# dpkg -l|grep libvirt
> ii  libvirt-bin                         0.4.6-10                   the
> programs for the libvirt library
> ii  libvirt-dev                         0.4.6-10
> development files for the libvirt library
> ii  libvirt-doc                         0.4.6-10
> documentation for the libvirt library
> ii  libvirt0                            0.4.6-10                   library
> for interfacing with different virtualization systems
> 
> version installed on my node:
> 
> 02:~# dpkg -l |grep libvirt
> ii  libvirt-bin                         0.4.6-10                   the
> programs for the libvirt library
> ii  libvirt0                            0.4.6-10                   library
> for interfacing with different virtualization systems
> 
> ================
> 
> error in my nc..log (eucalyptus node log):
> 
> [Sat Aug 15 02:24:58 2009][005115][EUCADEBUG ] system_output():
> [//usr/lib/eucalyptus/euca_rootwrap
> //usr/share/eucalyptus/gen_kvm_libvirt_xml --ramdisk --ephemeral]
> [Sat Aug 15 02:24:58 2009][005115][EUCAERROR ] libvirt: socket closed
> unexpectedly (code=39)
> [Sat Aug 15 02:24:58 2009][005115][EUCAERROR ] libvirt: Broken pipe
> (code=38)

There are two possible reasons for this error message

 - The daemon closed the client connection because it mis-behaved
 - The daemon crashed

Of these, the 2nd is the most likely. To check this, start the libvirtd
daemon manually, under GDB or valgrind, and then do whatever you do in
eucalyptus to make it break. Hopefully you'll then get a stack trace
from GDB, or a list of errors from valgrind. 0.4.6 is quite old now, so
you should report the bug to Debian's bug tracker with gdb/valgrind 
info so they can evaluate  whether its possible to fix/backport a patch

Alternatively you can upgrade to a newer version of libvirt, I'd recommend
0.6.4 which has proved quite stable, or even 0.7.0 though that's not has
as much exposure yet.

Regards,
Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]