VMware Cloud Community
ajohn24
Contributor
Contributor

Heartbeat error

ESX3.5U4. Upgraded the VC from 2.5 to 4.0. We are getting heartbeat error now on one of the host. The VMs are all working fine too.

Error detected on host : Agent can't send heartbeats.msg size: 912, sendto() returned: Operation not

permitted. Any clues ?

0 Kudos
10 Replies
AndreTheGiant
Immortal
Immortal

Do you have HA? Have you tried to reinstall the HA agent?

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
ajohn24
Contributor
Contributor

No HA in our environment..the alarm usually is generated after a scan for update is done..though the host is running fine and so are all the VMs onto it

0 Kudos
AndreTheGiant
Immortal
Immortal

No idea, sorry.

Strance behaviour for a simple scan for update.

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
rogerfinch
Contributor
Contributor

yup we are getting this too:-

Agent can't send heartbeats.msg size: 66

the esx hosts and vcenter server are on the same lan, not nat or firewall involved. only happening since we upgraded to 3.5 U4 to 4.0 with lastest patches.

anyone have an idea whats going on?

HA and DRS enabled. all vms running fine, all hosts happy too. Dell 2950s x 5. EMC Clarion backend, RAID10 luns x 5 x 1Tb on 4Gb FC

0 Kudos
albd
Contributor
Contributor

Hi Rogerfinch.

You say you have upgraded your esx hosts and vcenter, but you don't say you upgraded virtual tools from vm's.

Sometimes you can find issues you can solve upgrading vmtools.

You can try.

Alberto.

0 Kudos
rogerfinch
Contributor
Contributor

hi

yes, did the vmtools upgrade too. this only killed sql on one box and pcanywhere on another Smiley Happy

the errors relate to heartbeats to the host, not the vms..

0 Kudos
SimonLong
VMware Employee
VMware Employee

I've just come across this, has anyone worked out whats causing it?

Regards Simon

-


Visit My Blog, The SLOG at:

Follow me on Twitter:

Visit My Blog, The SLOG at: http://www.simonlong.co.uk
0 Kudos
ePaulSG
Contributor
Contributor

Ran into the "agent can't send heartbeats.msg size 66" error today. All of the hosts in vCenter showed as disconnected. I was able to see the ESX hosts initiate the heartbeats to the vCenter server but vCenter couldn't see them. Checked the IT firewall and the proper rules were inplace. Turns out the Windows firewall was turned on and was blocking UDP 902 outbound.

Once the rule was added to the Windows firewall, all of the hosts were able to reconnect.

0 Kudos
AdamFleischmann
Contributor
Contributor

Hello,

we have this strange feature too...

we have 3 clusters in our environment, and only one cluster with 2 esx show this message:

Agent can't send heartbeats.msg size: 66, sendto() returned: Operation not permitted

firewall on vc and between this 2 esx seem ok (still not blocking port 902...)

our esx servers:

esx4 with latest patches...

has anyone found an solution?

0 Kudos
AdamFleischmann
Contributor
Contributor

i found this in kb:

KB Article: 1019548

seems to be a bug... Smiley Sad

0 Kudos