Failed to install the virtualcenter Agent service after upgrading toVC2.0.1

[rthorson]

After upgrading to VC 2.0.1 one of my ESX servers disconnected and after trying to reconnect I get the following errors:

Failed to install the VirtualCenter Agent service.

Login failed due to a bad username or password.

Also, I logged in to the ESX server directly and I see the following errors:

A general system error occured: Create upgrade tmp directory failed.

The specified key, name, or identifier already exists.

[stbrinen]

I did the upgrade from VC 2.0.1 to VC 2.0.2 and had 2 of my eight Host servers not reconnect properly and give this error. I did the service mgmt-vmware restart and it resolved the issues. I also had to reconfigure HA on all of the servers before they would clear up completely. Thanks for the thread

[Petter_Lindgren]

One of my four servers did not reconnect after the 2.0.2 Update 1 for VC.

I issued 'service mgmt-vmware restart' on the host and could then reconnect to it.

[daikyu]

restarting the service did the trick.

thanks

[monikeo]

Yeah, the 'service mgmt-vmware restart' worked for me too. Thanks. When it doubt, reboot, I guess.

[halr9000]

FYI, the path has changed in VC 2.5. The agent upgrade bits are now located in c:\Program Files\VMware\Infrastructure\VirtualCenter Server\upgrade. Also new I see a file called 'vpx-upgrade-esx-7-linux-64192'. Not sure what ESX version that applies to, maybe 3i or 3.5?

[willdarton]

Ran into the same problems with the 2.5 upgrade this morning. About half of mine wouldn't reconnect...

In the end. I realized my times were off slightly. Got NTP up and running and everything started reconnecting correctly.

[sthoppay_wipro]

I tried most of the suggestions in this thread. Still no luck. When I ran the script, I noticed, it created the folder vpx-upgrade-installer.

In that folder, found the rpm VMware-vpxa-2.5.0-64192.i386.rpm

tried to install that rpm & bingo got the reason for failure. There is no space left on /var/log.

[azn2kew]

I got same problems while back doing 30 esx hosts upgrade for a client and 2 of them didn't work so I've checked the vpxa package version which doesn't match with other esx hosts. I've removed it and copied the new vpx package from VC server and reinstalled it and restart mgmt-vmware services and repeat same process.

Regards,

Stefan Nguyen

"The Power of Knowledge"

[Murr38]

Hey guys.

Thank you for the "service mgmt-vmware restart" tip. I was upgrading from 2.0 to 2.5 update1 and 1 ESX host would NOT re-connect. That fixed it!!

Thanks again.

[daikyu]

Vielen Dank für Ihre Nachricht!

Ich bin jedoch erst am 09.05 wieder im Büro und momentan auf Dienstreise. Die emails werden nicht weitergeleitet. Nach meiner Rückkehr werde ich ihr Email beantworten.

In dringenden allgemienen Angelegenheiten kontaktieren Sie bitte die hotline

(hotline@mannundmouse.coml 07242 224344)

In dringenden VMware Angelegenheiten kontaktieren Sie bitte

Hrn. Hochmuth Horst ( 07242 224344602)

*********************************************

Thank’s for your email

I’m out of office until 09 th of mai. after my return home I will answer your message. the messages are not forwarded automatically.

In urgent matters please do not hesitate to contact the hotline.

(hotline@mannundmouse.com 07242224344)

for VMware, please contact Mr. Horst Hochmuth ( 07242 224344602)

Mit freundlichen Grüssen / Best regards

Peter Erleshofer

IT Services VMware VCP

mann&mouse IT Services GmbH

Collmannstrasse 2

A-4600 WELS

phone +43.(0)664.8187666

fax +43.(0)7242.224344.7593

email erp@mannundmouse.com

www www.mannundmouse.com

[bargamj]

I had the same issue of trying to add the Host back into Virtual Center.

What I found is we had some residual NFS mounts back to a Windows machine.

We had removed this and started using iSCSI some time ago.

However, it did not look like everything was removed from this Host.

the /etc/mtab still had the mount points entered. /etc/fstab was clear.

After removing the entries from the mtab and umounting the mount points I was able to successfully connect the host into Virtual Center.