Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am trying to add a new host to a VMWare Cluster.

I get the error: A general system error occurred: Timed waiting for vpxa to start"

enter image description here

When I look on the host, I get many events of

Refresh service information
192.168.0.51
Completed
vpxuser
11/19/2012 4:49:48 PM
11/19/2012 4:49:48 PM
11/19/2012 4:49:49 PM

enter image description here

But the first error is the problem:

Create user
ha-folder-root
The 
specified key
, name, or 
identifier 
already 
exists.
root
11/19/2012 4:00:20 PM
11/19/2012 4:00:20 PM
11/19/2012 4:00:20 PM

On the vmforums, the suggested solution to this does not work: To resolve this issue:

 1. rename /etc/vmware/hostd/authorization.xml to /etc/vmware/hostd/authorization.xml.old.
 2. Restart the host management services. For more information, see Restarting the Management agents on an ESX or ESXi Server (1003490). 

The version is 5.1, and I have Essentials license.

On the new host there are no clients running

The new host version is 799733, and it has 2 other hosts running on it, which are still 5.0.0 - Should I upgrade them first?

share|improve this question
    
Does this host have any VMs running on it yet? Also, does your cluster already have other running hosts that are working? Are the other hosts also the same version of ESXi 5.1 (same build #)? –  sjw Nov 19 '12 at 13:04
    
added info to the question –  Saariko Nov 19 '12 at 14:56
add comment

2 Answers

up vote 3 down vote accepted

This question is old, however I came across this exact scenario today. Issue was that the vCenter server was running 5.0 and the ESXi host being added was 5.1.

Solution: upgrade vCenter from 5.0 to 5.1 prior to adding the host. As per the VMware Compatibility matrix, 5.1 hosts cannot be added to 5.0 or earlier vCenter servers.

The symptoms I experienced were identical to the ones listed in the original question. REF: http://communities.vmware.com/thread/417834

share|improve this answer
add comment

just a quick idea, try to unregister the troubled ESX host from vCenter Server then register it back again.

Regards,

share|improve this answer
    
Read the question: I can't add it (unless register and add are 2 different things) –  Saariko Nov 19 '12 at 15:09
    
well you right, my bad... –  Vladimir Nov 19 '12 at 15:14
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.