Issue:
Using vCenter 5.5 Web Client (the Linux VM Appliance), added Host. The Host does NOT add successfully. However, if you launch the 5.0 MS Windows client, the new host is in the inventory. If you try to add the host again, you get an error that the object name already exists.
Removing the host in the MS Windows client seems to be successful. When added back by the MS Windows client, it is successful, but still not visible. When removed in the MS Windows client again, it still cannot be added back using the Web Client - same error message.
Solution:
Remove the Inventory Service database and re-add it. Even after removing the database, it was still visible/usable in the MS Windows client. So nothing is really lost by doing this.
Using either a local login or a root SSH shell, enter the following:
1. Stop the corrupt Inventory Service service.
# service vmware-inventoryservice stop
2. Remove the database and it's folders.
# rm -rf /storage/db/inventoryservice/data
3. Recreate the database and give it the default username and password.
# /usr/lib/vmware-vpx/inventoryservice/scripts/ds-invoke.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice com.vmware.vim.dataservices.CreateDb /storage/db/inventoryservice/data changeme default changeme
4. Restart the Inventory Service service.
# service vmware-inventoryservice start
6a. Set the hostname variable for the re-register command.
# vcenterhost=vcenter.mindwatering.net
6b. Re-register the Inventory Service to the vCenter appliance.
# /usr/lib/vmware-vpx/inventoryservice-registration/vcregtool.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice-registration com.vmware.vim.dataservices.vcregtool.RegisterVC -action register -lookupserviceurl https://$vcenterhost:7444/lookupservice/sdk -isurl https://$vcenterhost:10443 -vcurl https://$vcenterhost/sdk/vimService -vccert /etc/vmware-vpx/ssl/rui.crt -vcprivkey /etc/vmware-vpx/ssl/rui.key -vcinstancecfg /etc/vmware-vpx/instance.cfg -vcendpointsdir /usr/lib/vmware-vpx/endpoints -vcextensionsdir /usr/lib/vmware-vpx/extensions
7. Restart the VPXD service.
# service vmware-vpxd restart
previous page
|