Need help with ESX 4 Service Console (/tmp folder)

[mitulgk]

Hello Experts,

We have an ESX 4 server (in fact there are 4 - three on ESX 4.1 and one of ESX 4.0) which have Production VM's on them.  When we upgraded our vCenter to 5.1, we tried to push the vCenter upgrade agents and it failed on these 4 servers (went fine on a lot other servers which were ESX 4.x and ESX 5.x).  On further investigation it seems that somehow the /tmp directory is the issue....whenever we try 'ls -l /tmp' the SSH session just freezes.

So looking for suggestions to resolve the same, without affecting the Production VM's running from the same (if possible as we do not have any downtime).

Thanks in advance.

Thanks and Regards,

Mitul

[zXi_Gamer]

Possible cases /tmp might be filled up which would have caused the pushing of the vcenter agents to be halted or in worst case corrupted. In case, you have access to shell, look out for the /var/log/vmware/vpxa.log or hostd.log to have a better explanation on why the agent did not get pushed. Also, since accessing /tmp is held up, if possible, try to do a du -sh /tmp.

Major case would be compatibility. Attached a matrix which would help you in either patching your ESX or using a higher version of vSphere Center