CentOS Bug Tracker
CentOS Website
Main | My View | View Issues | Roadmap | Docs
  

Viewing Issue Simple Details [ Jump to Notes ] [ View Advanced ] [ Issue History ] [ Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0003884 [CentOS-5] glibc crash always 2009-10-03 17:56 2009-11-18 08:42
Reporter jhughes@hughesjr.com View Status public  
Assigned To
Priority normal Resolution open  
Status new   Product Version
Summary 0003884: CentOS 5.4 glibc causes crash of VMWare vmware-hostd process in VMWare 2.0.0 and 2.0.1
Description CentOS 5.4 glibc causes crash of VMWare vmware-hostd process in VMWare 2.0.0 and 2.0.1. This is documented on these 2 VM threads:

http://communities.vmware.com/message/1364852 [^]

and

http://communities.vmware.com/thread/230842 [^]

Two ways to fix this are called out in the above threads. The easiest one is to just exclude glibc from CentOS-5.4 in the yum.conf file if you are upgrading a 5.3 machine, using this line:

exclude=*2.5-42*

Then do this to verify you will not get the new files in the upgrade:

yum list glibc*

The output should not show new glibc files.

===================
If you have already installed (or updated) to the new glibc files, you can manually download and install the older version of glibc* and/or ncsd from the 5.3 tree.

For a short time after 5.4 is released, this tree will be on the main centos mirrors:

http://mirror.centos.org/centos/5.3/ [^]

Later, you will still be able to get them from the CentOS Vault:

http://vault.centos.org/ [^]
Additional Information
Tags No tags attached.
Attached Files

- Relationships
has duplicate 0003987new Vmware Guests crash since upgrades that included glib 2.5-42 & Kernel 2.6.18-164.2.1 

-  Notes
(0010045)
Charlie Brady (reporter)
2009-10-08 19:46

 Or do this before upgrading (adapted from http://communities.vmware.com/message/1364852): [^]

    * Create the directory /usr/lib/vmware/lib/libc.so.6
    * Grab /lib64/libc-2.5.so (or
      /lib/libc-2.5.so in case you're running an 32 Bit host) and copy it to
      into /usr/lib/vmware/lib/libc.so.6
    * Rename the file libc-2.5.so within /usr/lib/vmware/lib/libc.so.6 to libc.so.6
    * Open /usr/sbin/vmware-hostd and add /usr/lib/vmware/lib/libc.so.6 to the LD_LIBRARY_PATH. I just added an "export LD_LIBRARY_PATH=/usr/lib/vmware/lib/libc.so.6:$LD_LIBRARY_PATH" before the last line.
    * Restart your vmware services (our just the host)
(0010046)
Charlie Brady (reporter)
2009-10-08 19:47

 You should also complain to VMWare. Considering that RHEL5 is their recommended platform, they support it poorly, e.g. they expect selinux to be disabled.
(0010159)
RevRagnarok (reporter)
2009-10-25 02:59
edited on: 2009-10-26 20:17

 If you've already updated glibc like I have, a hybrid version of note 1 above is to do this:

mkdir /usr/lib/vmware/lib/libc.so.6
cd /tmp
mkdir tmp
cd tmp
wget http://mirror.centos.org/centos/5.3/os/x86_64/CentOS/glibc-2.5-34.x86_64.rpm [^]
rpm2cpio glibc-2.5-34.x86_64.rpm | cpio -ivd
mv lib64/libc-2.5.so /usr/lib/vmware/lib/libc.so.6/libc.so.6

Edit /usr/sbin/vmware-hostd as above.

Wish me luck... I'm about to reboot.
(0010160)
RevRagnarok (reporter)
2009-10-25 03:00
edited on: 2009-10-26 20:19

 OK, I accidentally linked to another bug report. Also, the rpm2cpio shouldn't have the ../ leading the RPM file.

[EDIT] It was not your error. Mantis did that. I removed the "#" to prevent it. Also removed the ../ for people who get there through searches or from outside links. -toracat
(0010195)
LinuxETC (reporter)
2009-10-28 15:37

 VMware just release v2.0.2 as of 26 Oct 2009. Does this resolve the original bug report with glibc v2.5-42 by chance?
(0010203)
prgarcia (reporter)
2009-10-29 16:57

 I am still having the same issue with VMware-server-2.0.2-203138.x86_64.
(0010213)
nogin (reporter)
2009-10-30 21:52

 While I do not see much vmware-hostd crashes, after the 5.3->5.4 upgrade, I keep having the vmware-vmx (the virtual machine itself) crash, which is much more unpleasant that "just" a hostd crash. Not sure if this is a related problem, but it also did not go away after the 2.0.1->2.0.2 upgrade of VMWare and installing the latest kernel update.
(0010214)
RevRagnarok (reporter)
2009-10-30 22:23

 nogin, I have had 100% uptime since the 5.4 upgrade with three VMs running on consumer grade hardware. First thing I would do is run memtest86+ or some other program that will beat on your system. If that's not the problem, you should open a new bug because this one is tracking the specific issue of glibc not working with vmware-hostd...
(0010358)
jhaig (reporter)
2009-11-12 20:46

 I don't know if I am having the same problem. I upgraded to 5.4 (x86_64) some time ago and have been running a couple of CentOS vms since, one 5.4 and the other 4.8 (both i386). I had no problems until yesterday, when I installed and set up munin on them. Since doing this, the 5.4 guest has crashed for no apparent reason twice in a day.

The only major change I had to make was installing the rpmforge repositories on the host, to get the munin packages. Is there some easy way I can see if this bug is the problem I am seeing?

Thanks.
(0010376)
drennalls (reporter)
2009-11-18 08:07

 @jhaig
You might try adding "ulimit -c unlimited" just before the last line of /usr/sbin/vmware-hostd to enable core file generation. When/if a crash happens again you can examine the core file by doing...

gdb /usr/lib/vmware/bin/vmware-hostd /path/to/core_file

..once in gdb do "thread apply all bt" to generate backtraces for all the threads. I've found the signature of the crash is "Program terminated with signal 6, Aborted." where one of the backtraces shows an abort() from freeing memory, e.g.
Thread 1 (process 12674):
#0 0xb7fd3402 in __kernel_vsyscall ()
0000001 0x00909df0 in raise () from /lib/libc.so.6
0000002 0x0090b701 in abort () from /lib/libc.so.6
#3 0x0094ddc7 in free_check () from /lib/libc.so.6
#4 0x0094aa5b in free () from /lib/libc.so.6
#5 0xb76db211 in operator delete () from /usr/lib/vmware/lib/libstdc++.so.6/libstdc++.so.6
#6 0xb7db9cb1 in Vmomi::PropertyCollectorImpl::FilterImpl::AfterComputeUpdate () from /usr/lib/vmware/vmacore/libvmomi.so.1.0
..snip..

HTH
(0010377)
jhaig (reporter)
2009-11-18 08:42

 @drennalls
Thanks. I have already followed the steps given by RevRagnarok to fix the problem and I haven't had any more crashes (yet).

- Issue History
Date Modified Username Field Change
2009-10-03 17:56 jhughes@hughesjr.com New Issue
2009-10-03 17:56 jhughes@hughesjr.com Assigned To => kbsingh@karan.org
2009-10-08 19:46 Charlie Brady Note Added: 0010045
2009-10-08 19:47 Charlie Brady Note Added: 0010046
2009-10-22 06:31 NETim Issue Monitored: NETim
2009-10-22 14:29 villainy Issue Monitored: villainy
2009-10-25 02:59 RevRagnarok Note Added: 0010159
2009-10-25 03:00 RevRagnarok Note Added: 0010160
2009-10-26 20:17 toracat Note Edited: 0010159
2009-10-26 20:19 toracat Note Edited: 0010160
2009-10-28 15:37 LinuxETC Note Added: 0010195
2009-10-28 20:24 tljohnsn Issue Monitored: tljohnsn
2009-10-29 16:57 prgarcia Note Added: 0010203
2009-10-30 21:49 nogin Issue Monitored: nogin
2009-10-30 21:52 nogin Note Added: 0010213
2009-10-30 22:23 RevRagnarok Note Added: 0010214
2009-11-12 02:58 kwanlowe Issue Monitored: kwanlowe
2009-11-12 20:46 jhaig Note Added: 0010358
2009-11-13 15:25 toracat Relationship added has duplicate 0003987
2009-11-15 09:44 jhaig Issue Monitored: jhaig
2009-11-16 12:56 mfalb Issue Monitored: mfalb
2009-11-18 08:07 drennalls Note Added: 0010376
2009-11-18 08:42 jhaig Note Added: 0010377
2009-11-20 11:43 wste Issue Monitored: wste

Copyright © 2000 - 2009 Mantis Group
Powered by Mantis Bugtracker