one of my server hosted on vmware 5.5 getting crashed twice.

Its a centos 5.8 version when I tried logging case with vmware they deny and asked to raise this with OS vendor.

let me know if any one has any idea why this server crashed and I got kernel panic error.

I have enclosed the image.

Attached Thumbnails

 

And that image and the tiny bit of information you've provided tell us NOTHING. You don't tell us if this server HAD been working ok, or if it was a new installation, or what changes (if any) took place. Things don't 'just crash'...there is a cause. What happened recently on that server? Check the system logs for any causes or clues, but what you've posted here is of no help at all in diagnosing this.

Also, if you're paying for VMware, they won't 'deny' a service request...ARE you paying for VMware, as you should be? Also, CentOS 5.8 is VERY old, and totally unsupported...the latest is 7.x.

TBone

If I have any logs when the server was crashed definitely, I would paste.

Its a production server, so we wont play anything with particular VM.

I understand 5.x is old but as I told its a prod VM and So we are not upgrading to 7.x or 6.x

VMware says its a OS related issue so, they wont help & I need to check with OS vendor.

I have given screenshot while server was down, That's all I can say.

From Tb0ne:

Additionally:

What do the logs on the system tell you? (Log in with a bootable disk, mount the drive, get the logs etc)

Please answer these questions if you can, and gather the logs as indicated. Share anything you find interesting in the logs to help diagnose.

..and WITHOUT any information from the logs, there is NOTHING we can tell you.
No idea what you mean by this.
If it's a PRODUCTION server, then you should ABSOLUTELY upgrade it. 5.8 is TOTALLY UNPATCHED and unsupported...it is not only insecure, but will probably have issues (such as this), on current hardware/VMware.
...which again, tells you that you NEED to upgrade your OS.
Then you'll have to figure it out yourself. A few lines from a kernel panic screen tells us absolutely nothing. Unless you have actual information and details, there is NOTHING we can help you with.

And AGAIN, you were asked questions before, which you still haven't answered; both myself and szboardstretcher asked you questions, and you have not even acknowledged you read them, much less have answered them. If you're not going to answer questions when asked and provide no details, there is no point in posting. Additionally, the VMware support team told you POINT BLANK that this is an OS issue, and you ignored THEM too.

When server was crashed i got the error which i had posted earlier. I reset the machine and then after server comes up and this happened twice.

Then I have upgrade the centos from 5.8 to 5.11. Its a application server (lamp) and there is no changes took place.

There is no logs present during the time frame. I have only seen below logs from server which I am sharing.

========================================logs=========================================

Nov 7 15:43:33 *****-228 snmpd[4108]: Connection from UDP: [172.16.110.35]:58678
Nov 7 15:43:33 *****-228 snmpd[4108]: Received SNMP packet(s) from UDP: [172.16.110.35]:58678
Nov 7 15:43:43 *****-228 snmpd[4108]: Connection from UDP: [172.16.10.35]:36537
Nov 7 15:43:43 *****-228 snmpd[4108]: Received SNMP packet(s) from UDP: [172.16.110.35]:36537
Nov 7 15:43:53 *****-228 snmpd[4108]: Connection from UDP: [172.16.10.35]:42382
Nov 7 15:43:53 *****-228 snmpd[4108]: Received SNMP packet(s) from UDP: [172.16.110.35]:42382
Nov 7 15:54:45 *****-228 syslogd 1.4.1: restart.
Nov 7 15:54:45 *****-228 kernel: klogd 1.4.1, log source = /proc/kmsg started.
Nov 7 15:54:45 *****-228 kernel: Linux version 2.6.18-308.1.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Wed Mar 7 04:16:51 EST 2012
Nov 7 15:54:45 *****-228 kernel: Command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
Nov 7 15:54:45 *****-228 kernel: BIOS-provided physical RAM map:
Nov 7 15:54:45 *****-228 kernel: BIOS-e820: 0000000000010000 - 000000000009f800 (usable)
Nov 7 15:54:45 *****-228 kernel: BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Nov 7 15:54:45 *****-228 kernel: BIOS-e820: 00000000000ca000 - 00000000000cc000 (reserved)
Nov 7 15:54:45 *****-228 kernel: BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
Nov 7 15:54:45 *****-228 kernel: BIOS-e820: 0000000000100000 - 00000000bfee0000 (usable)
==================================================================================================== =================================


Update from VMware Team
=======================

The vmmemctl driver is not included with VMware tools, we use that driver when needed but the driver crashing is handled but the OS vendor not by us..
vmmemctl driver is upstreamed to the vendor.

You may not agree but this is now handled but the software Vendor not us.

Please provide your software vendor with the crush dumps, this case will now be archived as a 3rd party issue.


Its OS issue and please click below link for further help.

https://access.redhat.com/solutions/722633

==================================================================================================== ===================

I don't have subscription with Redhat and if you click the link you will see same error.

If you still need any more info. Please let me know.

So, no changes...other than the fact you TOTALLY UPGRADED the server??????
Right...so AGAIN, you need to update the is to something current that is supported by vmware. This is very clear from the support message. Either do it or it won't work. The module mentioned is causing the crash...that module is NOT provided by VMware, and they tell you so. That module is provided by the OS you're using, and you are refusing to update it.

So what, exactly, would you like us to do? You know what the problem is, and how to fix it. Whether you choose to fix the problem or not is up to you.