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

Re: [Xen-API] Segmentation Fault with xe --nossl

On 18/07/13 16:26, Carsten Beyer wrote:
Hi Dave,

the xapi-xe-0.2-5669.i686 RPM came from the XenServer 6.2 Install
ISO-Image and I'm currently wondering where I could get the xe
debug-info RPM. Previous used xapi-xe-RPM's came from the XCP ISO Image.

Without debug-info, it looks like this in gdb (not useful):

I see what you mean!

Although I'm still curious to understand this failure, you might have better luck with a version of xe which I've compiled specifically for CentOS 6.4 x86_64:


Let me know if that one works better for you.


[root@lizard2 bin]# gdb xe core.31717
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
Reading symbols from /usr/bin/xe...(no debugging symbols found)...done.
[New Thread 31717]
Core was generated by `xe vm-list -s xenbase01 -pwf
/root/bin/pwfile.xenbase01 --nossl'.
Program terminated with signal 11, Segmentation fault.
#0  0x0810bb19 in ?? ()
Missing separate debuginfos, use: debuginfo-install xapi-xe-0.2-5669.i686
(gdb) bt
#0  0x0810bb19 in ?? ()
#1  0x080e587c in ?? ()
#2  0x080e47e3 in ?? ()
#3  0x080e6da6 in ?? ()
#4  0x080e36ca in ?? ()
#5  0x080e6f2e in ?? ()
#6  0x080d4b9a in ?? ()
#7  0x080d4c10 in ?? ()
#8  0x080d59ac in ?? ()
#9  0x080d70ca in ?? ()
#10 0x0808cd95 in ?? ()
#11 0x0804bd1e in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)


On 07/18/2013 02:26 PM, David Scott wrote:
On 18/07/13 12:12, Mike McClurg wrote:
On 17/07/13 16:46, Carsten Beyer wrote:

I get a Segmentation fault with the 'xe' command (RPM
xapi-xe-0.2-5669.i686 and earlier versions) if I use the '--nossl'
parameter on a CentOS 6.4 (64bit) server. Without the '--nossl'
parameter 'xe' works fine. We are using LDAP with 'sssd' for
authentication and if we fall back to 'nscd' the Segmentation fault
doesn't occur. That would be our workaround for now.

FYI, I couldn't reproduce this on Ubuntu with a 64-bit build of xe (from
the xcp-xe package). I'll see about reproing this on CentOS 6.4.

[root@lizard2 bin]# xe vm-list -s xenbase01 -pwf pwfile.xenbase01
Segmentation fault

Can you find and install the xe debug-info RPM? If so then you could
enable core dumping

  ulimit -c unlimited

then perform another repro, which will make a core dump file
("core.PID"). If you install gdb

  yum install gdb

you can then get a backtrace from it using

  gdb xe corefilename

and typing in "bt" (for "backtrace"). That would be very interesting!


[root@lizard2 bin]# xe vm-list -s xenbase01 -pwf pwfile.xenbase01
uuid ( RO)           : 1764cfe1-27f4-42e3-bc74-c47db9c533ac
      name-label ( RW): Control domain on host: xenbase01
     power-state ( RO): running

We want to replace our current administration server (RHEL
5.9/LDAP/nscd) with a newer one (CentOS 6.4/LDAP/sssd). Our XEN pools
are running with XenServer 6.2 (just updated).

Had anybody else a similar problem with 'xe' ?

Best Regards,
Carsten Beyer

Xen-api mailing list

Xen-api mailing list

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.