VMware Cloud Community
jones_rc
Contributor
Contributor

ESX 4 PSOD Issues - Heartbeat: 471: PCPU 1 didn't have a heartbeat in xx seconds. *may* be locked up

Screnshot attached, we have 5 Virtual Hosts, 3 of these run version 3.5 (no issues at all) and the other 2 have recently been upgraded (clean installs) to Vsphere Version 4 build 164009. They run on Dell PowerEdge 2970 servers with 2x Quad Core Opteron 2350 processors and 32GB RAM. They had a connection to SAN Storage and were previously clustered but I have now removed this due to this issue.

This issue has occurred several times now on both servers and Internet searches state that it is related to Hardware but I don't buy this, the servers are less than 6 months old and have worked fine on version 3.5. Can anyone offer any advice on how best to troubleshoot the issue? I am considering reverting back to 3.5 as my experience with VSphere has not been great so far.

Reply
0 Kudos
6 Replies
admin
Immortal
Immortal

Hi,

Please install the hot-off-the-press ESX 4.0 patch 02.

One of the fixes in the patch addresses this specific crash, and should

do the trick.

Regards,

-Ari

Reply
0 Kudos
jones_rc
Contributor
Contributor

Hi,

Thanks for your response, I have had a look on the website and can't find an update patch for VMware Vsphere. Do you have a link?

Reply
0 Kudos
ITOSITU
Contributor
Contributor

jones_rc
Contributor
Contributor

The patch page was unavailable but I have managed to download the patches now, I will test this and let you know how I get on.

Many Thanks.

Reply
0 Kudos
coco26
Contributor
Contributor

ANy updat e on whether your issue was resolved? I dont see anything in the patch list thats specifically related to this error - can you be a bit more specific. I have the same error on 3.5 server

Reply
0 Kudos
jones_rc
Contributor
Contributor

I wasn't sure what patch the previous post was talking about but there was one that was posted within the last month. The details did not seem to be related to the problem I was experiencing but I applied all of the patches that were outstanding and I have not experienced the problem since. It is still early days so I am going to continue testing for another month before I migrate any of my working 3.5 machines to vsphere.

Reply
0 Kudos