Re: [libvirt] Re: Libvirt PHP binding

On Tue, Apr 14, 2009 at 03:56:28PM +0200, Radek Hladik wrote: > > When running from command line everything seems to work fine. This is of > course singlethreaded and potential resource leaks need not to cause a > problem. However when running from webserver, the result is much more > interesting. When connecting to qemu:///system (via local socket) using > <? > libvirt_connect($uri,true); > ?> > I can crash the libvirt daemon after cca 10 page reloads - sometimes > with message > Apr 13 15:32:44 kvmtest kernel: libvirtd[8263]: segfault at 4 ip > 00000039d7223fc0 sp 00007fa6fbc29a88 error 6 in > libdbus-1.so.3.4.0[39d7200000+3c000] > in system log, sometimes without any message. Crashing the libvirtd daemon is not your fault ! It is supposed to be completely robust against whatever bad stuff the client may throw at it. So even if the client has a bug, then it shouldn't crash the daemon. If possible it'd be helpful if you can get a stack trace from the daemon. You can do this by stopping the demon '/etc/init.d/libvirtd stop' and then running it under GDB directly 'gdb /usr/sbin/libvirtd' make sure you have libvirt-debuginfo RPM installed if using Fedora, or have built with '-g' debug option if built manually.

> httpd-2.2.11-6.x86_64 > php-5.2.9-1.fc11.x86_64 > php-devel-5.2.9-1.fc11.x86_64 > libvirt-0.6.0-2.fc11.x86_64 > qemu-0.9.1-12.fc11.x86_64 > libvirt-devel-0.6.0-2.fc11.x86_64 I'd recommend updating to the latest libvirt 0.6.2 release that should be available in rawhide now. It fixed quite a few crashes & leaks, which you may be unlucky enough to be hitting