Varunsh
Enthusiast
Enthusiast

repetitive errors in Virtual center

I am getting n numbers fo alerts in my virtual center events tab....I have seen multiple posts taht people are facing such errors and come to know its a known bug on http://malaysiavm.com/blog/false-alarm-host-connection-failure/#more-1923

but unable to find any vmware kb article which states its an issue...could someone help me out in resolving issue...I have checked the connectivity between vc and esx host ..it is absolutely fine...dns resolution is fine....ports are open..ESx build is ESX 4.0.0.208167

( OR OR OR OR )

Alarm Definition:

( OR OR )

0 Kudos
9 Replies
a_p_
Leadership
Leadership

Not sure if this helps solving your issue, but I'd suggest you take a look at the latest release notes. There are several entries concerning alarms. http://www.vmware.com/support/vsphere4/doc/vsp_vc40_u2_rel_notes.html

Maybe the issues have already been resolved in a newer build (than 208167).

André

0 Kudos
Varunsh
Enthusiast
Enthusiast

Hi Andre,

I had checked it earlier..there are no performance issue on server......which could have caused HA agent connectivity issue.

I am awaiting for the official stement to acknowledge the issue.

0 Kudos
Varunsh
Enthusiast
Enthusiast

..???????????....helooooooooo

0 Kudos
a_p_
Leadership
Leadership

..???????????....helooooooooo

Not sure what you mean by this?!

If you need an official statement, the communities are the wrong place. The members here are users like you and me. If you need an official statement you need to open a support call with VMware.

André

0 Kudos
Varunsh
Enthusiast
Enthusiast

i did not m ean lyk that...let me explain...if someone has faced this issue or able to resolve it... if anyone knows any kb article ....coz i am sure someone must have faced this kind of issue and able to resolve

0 Kudos
Varunsh
Enthusiast
Enthusiast

when i checked /var/log/messages i got following entries

Aug 23 10:50:17 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6179 from=127.0.0.1

Aug 23 10:50:17 ictrsesx001 xinetd[2792]: EXIT: vmware-authd status=255 pid=6179 duration=0(sec)

Aug 23 10:50:18 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6180 from=127.0.0.1

Aug 23 10:50:18 ictrsesx001 xinetd[2792]: EXIT: vmware-authd status=255 pid=6180 duration=0(sec)

Aug 23 10:50:21 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6356 from=127.0.0.1

Aug 23 10:50:21 ictrsesx001 xinetd[2792]: EXIT: vmware-authd status=255 pid=6356 duration=0(sec)

Aug 23 10:50:21 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6357 from=127.0.0.1

Aug 23 10:50:21 ictrsesx001 xinetd[2792]: EXIT: vmware-authd status=255 pid=6357 duration=0(sec)

Aug 23 10:50:25 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6420 from=127.0.0.1

Aug 23 10:50:25 ictrsesx001 xinetd[2792]: EXIT: vmware-authd status=255 pid=6420 duration=0(sec)

Aug 23 10:50:25 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6421 from=127.0.0.1

Aug 23 10:50:25 ictrsesx001 xinetd[2792]: EXIT: vmware-authd status=255 pid=6421 duration=0(sec)

Aug 23 10:50:29 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6503 from=127.0.0.1

Aug 23 10:50:29 ictrsesx001 xinetd[2792]: EXIT: vmware-authd status=255 pid=6503 duration=0(sec)

Aug 23 10:50:29 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6504 from=127.0.0.1

Aug 23 10:50:29 ictrsesx001 xinetd[2792]: EXIT: vmware-authd status=255 pid=6504 duration=0(sec)

Aug 23 10:50:32 ictrsesx001 xinetd[2792]: START: vmware-authd pid=6577 from=127.0.0.1

0 Kudos
Varunsh
Enthusiast
Enthusiast

has anyone faced such issues before..........?

0 Kudos
a_p_
Leadership
Leadership

You may want to read http://kb.vmware.com/kb/1012942

It looks like a DNS/name resolution issue.

Please check "/etc/hosts" and "/etc/resolv.conf" for wrong entries.

André

Varunsh
Enthusiast
Enthusiast

thanks Andre....its a nice article ...I have checked host file and resolve.conf and these are configured correctly...name resolution is proper. My server remain in virtual center but alerts are not stopping "Alarm 'Host connection failure' on usmoesx001.alpha.rb.net sent email to

xyz@abc.com;

I am not able to identify the actual issue or I am not be that good in understanding log files......

0 Kudos