[libvirt-users] Libvirtd dead, pid still exists. ( Problem might be with TLS interface of libvirtd )

[SHREE DUTH AWASTHI]

Dear All,

A Gentle Reminder !!!

Any suggestions please on how to debug further

Gist : libvirt crash when trying to inquiry libvirt version using curl with
TLS ( virsh -c qemu+tls://localhost/system version )

Your inputs would be of great help !

Thanks and Regards,
Shree Duth Awasthi.
On Fri, Apr 5, 2013 at 2:41 PM, SHREE DUTH AWASTHI <
shreeduth.awasthi at gmail.com> wrote:

> Hi Michal,
>
> Thanks for your time.
>
> Yes it seems so. Adding one more info :
>
> The issue is not reproducable on our board with
> libvirt-0.9.4-rc0_WR4.3.x86_64, gnutls-utils-1.4.1-2_WR4.3.x86_64,
> libgcrypt-1.4.0-3_WR4.3.x86_64.
>
> We are unable to debug more as GDB symbols are not completely resolved.
>
> So, can you please give us some pointers to debug the issue further.
>
> Thanks and Regards,
> Shree Duth Awasthi.
>  On Fri, Apr 5, 2013 at 9:34 AM, Michal Privoznik <mprivozn at redhat.com>wrote:
>
>>  On 05.04.2013 09:04, SHREE DUTH AWASTHI wrote:
>>
>> > GDB:
>> >
>> > Program received signal SIGABRT, Aborted.
>> > 0x00007f8591246005 in raise () from /lib64/libc.so.6
>> > (gdb) bt
>> > #0  0x00007f8591246005 in raise () from /lib64/libc.so.6
>> > #1  0x00007f8591248e40 in abort () from /lib64/libc.so.6
>> > #2  0x00007f8592a2fdc5 in ?? () from /lib64/libgcrypt.so.11
>> > #3  0x00007f8592a303d5 in ?? () from /lib64/libgcrypt.so.11
>> > #4  0x00007f8592a35697 in ?? () from /lib64/libgcrypt.so.11
>> > #5  0x00007f8592a3579c in ?? () from /lib64/libgcrypt.so.11
>> > #6  0x00007f8592a30a65 in ?? () from /lib64/libgcrypt.so.11
>> > #7  0x00007f8592a30aa9 in ?? () from /lib64/libgcrypt.so.11
>> > #8  0x00007f8592a30b19 in ?? () from /lib64/libgcrypt.so.11
>> > #9  0x00007f8592a735df in ?? () from /lib64/libgcrypt.so.11
>> > #10 0x00007f8592a7365f in ?? () from /lib64/libgcrypt.so.11
>> > #11 0x00007f8592a6025a in ?? () from /lib64/libgcrypt.so.11
>> > #12 0x00007f8592a6045a in ?? () from /lib64/libgcrypt.so.11
>> > #13 0x00007f8592a3c1ef in ?? () from /lib64/libgcrypt.so.11
>> > #14 0x00007f8592cd9d8c in ?? () from /usr/lib64/libgnutls.so.26
>> > #15 0x00007f8592cc5e7a in ?? () from /usr/lib64/libgnutls.so.26
>> > #16 0x00007f8592ccddd6 in ?? () from /usr/lib64/libgnutls.so.26
>> > #17 0x00007f8592cce67f in ?? () from /usr/lib64/libgnutls.so.26
>> > #18 0x00007f8592ccedaf in ?? () from /usr/lib64/libgnutls.so.26
>> > #19 0x00007f8592cbaf85 in ?? () from /usr/lib64/libgnutls.so.26
>> > #20 0x00007f8592cb6c55 in ?? () from /usr/lib64/libgnutls.so.26
>> > #21 0x00007f8592cb7437 in gnutls_handshake () from
>> > /usr/lib64/libgnutls.so.26
>> > #22 0x00007f8593a5961b in virNetTLSSessionHandshake () from
>> > /usr/lib64/libvirt.so.0
>> >
>>
>> The backstrace shows problem lies in libgcrypt library. So unless
>> libvirt is overwriting some random memory areas, it's a libgcrypt's bug.
>>
>> Michal
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20130409/59313819/attachment.htm>