The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
ESX Server 3.0.x Hosts Shown as Disconnected after Upgrading VirtualCenter Server 2.x (4478241)
You may experience issues connecting to the ESX Server 3.0.x hosts after upgrading VirtualCenter Server 2.x to a later release.
The following error messages may appear:
Failed to install the VirtualCenter Agent service.
A general system error occurred: Create upgrade tmp directory failed.
This issue appears if the directory /tmp/vmware-root is missing on an ESX 3.0.2 host. Virtual Infrastructure Client reports the host as disconnected and you cannot connect the host because the VirtualCenter Agent (vpxa ) fails to upgrade on the host with the missing directory.
ESX Server patches have been released to address this issue and are the preferred resolution.
The alternative solutions described here can be used either proactively as a pre-upgrade procedure or as a means to correct an environment that has already been upgraded and is now experiencing the issue. In case of the latter, each ESX Server must be manually reconnected after addressing the missing directory issue. The VirtualCenter Agent updates properly and the ESX Server host shows up normally in the VirtualCenter inventory.
Note: Before you begin please refer to KB1003490 for important information on restarting the mgmt-vmware service.
This issue has been addressed in 3.0.2 patches.
Note: Hosts that have the appropriate patch installed before VirtualCenter Server is upgraded are not affected.
The patch for ESX Server 3.0.2 is available at: http://kb.vmware.com/kb/1002088
VMware recommends applying the applicable patches. If you are unable to apply the applicable patches, the following alternative is available as a temporary solution:
Apply one of the following workarounds:
Option 1: Restart Host Agent (hostd) on each ESX Server 3.0.x host.
[root@esxhost]# service mgmt-vmware restart
This creates the missing /tmp/vmware-root directory.
Caution: Issuing service mgmt-vmware restart also restarts any virtual machine configured to auto-start or auto-shutdown. This issue only affects ESX Server 3.0.1 without patch ESX-7557441 .
Option 2: Manually create the missing directory on each ESX Server 3.0.x host.
[root@esxhost]# mkdir -p /tmp/vmware-root
Option 3: Consider using a script to log into each ESX Server 3.0.x host to create the missing directory.
The script attached to this KB article can be downloaded and executed directly on the VirtualCenter Server machine. Run the script before attempting to perform a VirtualCenter Server upgrade.
To utilize this script, there must be an account on each ESX Server 3.0.x host that has permission to log in via SSH. This does not need to be the root account, any user that can log into the host is sufficient.
The script also requires access to the plink.exe utility, which is available as part of the PuTTY suite. You can download this utility from: http://www.chiark.greenend.org.uk/~sgtatham/putty/ .
To execute the script, open a command prompt and type:
Note: The script is provided as-is, and is not supported by VMware Technical Support. The script has undergone minimal QA testing and might not work in all environments. Please use one of the other two options above, if necessary.
Option 4: Remove the installed VirtualCenter Agent (vpxa).
Log in to the service console as root and run:
rpm -qa | grep vpxa
The result appears similar to:
Note: If there is no output, there is either: A) n o agent installed, or B) a problem with the agent installation that is beyond the scope of this documentation. File a support request with VMware Support and note this KB Article ID in the problem description. For more information, see How to Submit a Support Request .
Remove the vpxa package. run this command:
rpm -e VMware-vpxa
If the VirtualCenter Server upgrade has already been performed, use the Virtual Infrastructure Client connected to VirtualCenter and reconnect the ESX Server hosts. You are prompted for the root credentials and the updated VirtualCenter Agent is successfully installed. If this workaround has been applied as a pre-upgrade step, normally it is not necessary to perform this additional reconnection step.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.