ESX hosts not responding in VC

[aravinds3107]

For the past few days one of our ESX host is going to not responding state in VC every night. When checking service console found the hostd agent was in stopped state, so I have restarted hostd and vpxa agent services and everything comes back to normal.

Can someone suggest on how to start the troubleshooting on this?

[Rubeck]

I would start by chekking free space in service console (df -lh)...

/Rubeck

[jkumhar75]

could you check the hostd log file on that ESX server, if possible could you upload that log file here?

Jay

VCP 310,VCP 410,MCSE

Consider awarding points for "helpful" and/or "correct" answers.

[aravinds3107]

i have checked disk space and have almost 50% free space.

Attached is the hostd log

[philvirt]

Have you rebooted the ESX host lately?

Thanks,

Phil Couto

[Rubeck]

Do the host dump any files into your /var/core when the hostd terminates and is the watchdog proc for hostd up and running?

/Rubeck

[Troy_Clavell]

also, if not already done, you may consider upping your service console memory to 800MB to help with the hostd crashes.

[Rubeck]

Indeed, Troy..

Whaz up with this not being default these days anyway?

/Rubeck

[aravinds3107]

Our Service console is still with 272 MB, so before we increase the service console to 800 MB should we also increase the Swap partition to 1.6 GB

[jo_strasser]

Hi!

We have the same issue...

Every night up to 12 hosts are not responding to vcenter...

I got an alarm from vcenter, but the hosts are working proberly...

So, the timeout will be only in ms or seconds area.

ESX 4.0 U1 and vCenter 4 U1 running.

SC of hosts got 800MB RAM, enough free disk space on the vCenter system.

Have anyone a solution or an idea?

best regards,

Strasser Johannes, VCP, VXP