VMware Cloud Community
rthorson
Contributor
Contributor
Jump to solution

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

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.

Reply
0 Kudos
1 Solution

Accepted Solutions
tfra
Enthusiast
Enthusiast
Jump to solution

You could manually try to install the agent as follows:

\- Copy the vpx-upgrade-esx-6-linux-32042 from the upgrade folder in the VC folder to /tmp on the ESX server

\- run the command sh vpx-upgrade-esx-6-linux-32042

(By default the script is located in C:\program files\vmware\vmware virtualcenter\upgrade )

Next restart management services:

service mgmt-vmware restart

After completing the above steps, try to reconnect to the esx

View solution in original post

Reply
0 Kudos
50 Replies
tfra
Enthusiast
Enthusiast
Jump to solution

You could manually try to install the agent as follows:

\- Copy the vpx-upgrade-esx-6-linux-32042 from the upgrade folder in the VC folder to /tmp on the ESX server

\- run the command sh vpx-upgrade-esx-6-linux-32042

(By default the script is located in C:\program files\vmware\vmware virtualcenter\upgrade )

Next restart management services:

service mgmt-vmware restart

After completing the above steps, try to reconnect to the esx

Reply
0 Kudos
Allen_Derusha
Contributor
Contributor
Jump to solution

I experienced the exact same issue - 4 ESX servers in one cluster, upgraded to 3.0.1 and everything was OK until I upgraded VC to 2.0.1. At this point, all of the servers were disconnected and wouldn't reconnect. The process outlined by trfa above fixed all 4. Thank you so much!

Reply
0 Kudos
rthorson
Contributor
Contributor
Jump to solution

That worked. I was successfully able to reconnect to the VC. Thank you for your help

Reply
0 Kudos
BKersting
Contributor
Contributor
Jump to solution

Thanks tfra.

I had the same situation and your solution resolved it for me as well.

Reply
0 Kudos
Jae_Ellers
Virtuoso
Virtuoso
Jump to solution

Just an update for folks not using ESX 3 yet.

Look in C:\Program Files\VMware\VMware VirtualCenter 2.0\upgrade\bundleversion.xml to determine which vpx-upgrade-esx script you need. I had this problem and needed #1 for an old 2.1.2 system.

And the path to the script on my VC 2.0.1 load is C:\Program Files\VMware\VMware VirtualCenter 2.0\upgrade\

Message was edited by:

Jae Ellers

-=-=-=-=-=-=-=-=-=-=-=-=-=-=- http://blog.mr-vm.com http://www.vmprofessional.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Reply
0 Kudos
amslife
Enthusiast
Enthusiast
Jump to solution

going from esx3.0 to 3.01 worked for me with upgrade 6.

Reply
0 Kudos
kimono
Expert
Expert
Jump to solution

I am having this problem with 1 out of our 38 ESX 2.5.3 hosts. We upgraded to VC2.0.1 from 1.3.1 last week and this 1 host won't connect with this error. I've tried a manual install using

sh /tmp/vpx-upgrade-esx-3-linux-32042[/b]

But to no avail. Don't really want to reboot the host as it's running VMs. Am going to log support issue and see what they say.

kim

/kimono/
Reply
0 Kudos
rzomerman
Contributor
Contributor
Jump to solution

Did you fix this already? I'm having same problem now .. after upgrading VC to 2.1 and ESX to 3.01

Reply
0 Kudos
kimono
Expert
Expert
Jump to solution

I ended up rebooting the host

/kimono/
Reply
0 Kudos
boydd
Champion
Champion
Jump to solution

Did you try restarting serverd?

DB

DB
Reply
0 Kudos
mrbrown66
Contributor
Contributor
Jump to solution

In my case I had filled up the / disk volume with ISO's !

I had to update the vmimages soft link to point to VMFS and move all the ISO files over to vmfs.

J

Reply
0 Kudos
pjgould
Enthusiast
Enthusiast
Jump to solution

We just applied Patch 1 to VCenter 2.0.1 and experienced a similar issue in that our ESX 3.0.1 hosts configured for HA/DRS wouldn't reconnect to VCenter. Got the same "Failed to install the VirtualCenter Agent service." error as the first post. A standalone 3.0.1 host reconnected just fine as well as all of our 2.5.3 hosts. Fixed it by running

service mgmt-vmware restart

on each host that was having problems and then manually reconnecting via VCenter.

Message was edited by:

pjgould

Reply
0 Kudos
mdina
Contributor
Contributor
Jump to solution

I ran 'service mgmt-vmware restart' and it fixed it for me. Thanks!

Reply
0 Kudos
letoatrads
Expert
Expert
Jump to solution

Encountered this same issue when I installed VC 2.0.1 Patch 1 today. The service mgmt-vmware restart resolved it for some of my hosts, others who would connect but not register with HA required me to destroy the cluster and re-add the hosts.

Reply
0 Kudos
MrPhoenix
Contributor
Contributor
Jump to solution

Hi!

I had the same issue today.

Destroying the cluster and reastablishing a new one solved the problem.

This works, but isn't a real solution. What if there are realy sensitive VMs running on the ESX-Hosts? What if they are "mission critical"?

Disconnected VMs or even ESX-Hosts are real pain in the ass, at least for me

Regards,

Philipp

Reply
0 Kudos
adriano_oliveir
Contributor
Contributor
Jump to solution

It works , thanks for your help Mr. tfra......

Reply
0 Kudos
S_Crockett
Contributor
Contributor
Jump to solution

I had a similar problem when attempting to apply patch 2 to VirtualCenter. All but 1 of the ESX servers updated successfully. I was naive and did not realize that the VirtualCenter patch would also update my ESX servers. I determined that I was out of space on the /opt filesystem. Clearing space and restarting mgmt-vmware and vmware-vpxa did not seem to help. I was able to install vpx-upgrade-esx-6-linux-40644 manually, but was still unable to connect the ESX server in VC. What finally worked for me was to resynchronize the time with ntp, uninstall vpx manually, remove the vpxuser userid, and reattempt to reconnect in VC. BINGO!

Reply
0 Kudos
brokebastard
Contributor
Contributor
Jump to solution

trfa, your solution work for me after upgrading to VC 2.01. Thanks for the post.

Reply
0 Kudos
TFX
Contributor
Contributor
Jump to solution

Hello all,

My problem seems to reach further. I did all of the above. But the installation of "sh ./vpx-upgrade-esx-6-linux-40664" hangs (See log below). There are six VM's running on this ESX 3.0.1 server.

The VIC's error is Failed to install the VirtualCenter Agent service. Some help would be appreciated.

Total of 8 DL380 G5's with ESX 3.0.1 and only (this) one has this problem.

Now there is no vpxa installed anymore vpxa -v: -bash: vpxa: command not found. Uh, yikes!

NOTE: The root password is correct but VIC reports: Login failed due to a bad username or password. And then it starts to install the update and hangs for about two! hours on 19%, Reconnect host.

Log:

\[27747] 2007-03-13 11:20:03 AM: Logging to /var/log/vmware/vpx-ivpx-upgrade-esx-6-linux-40644.log

\[27747] 2007-03-13 11:20:03 AM: exec mkdir -p /tmp/VMware-vpx-esx-6-linux-40644

\[27747] 2007-03-13 11:20:03 AM: status = 0

\[27747] 2007-03-13 11:20:03 AM: exec tar -xvf /tmp/VMware-vpx-esx-6-linux-40644.tar -C /tmp/VMware-vpx-esx-6-linux-40644

\[27747] 2007-03-13 11:20:03 AM: status = 0

\[27747] 2007-03-13 11:20:03 AM: exec cd /tmp/VMware-vpx-esx-6-linux-40644/

\[27747] 2007-03-13 11:20:03 AM: status = 0

\[27747] 2007-03-13 11:20:03 AM: Build: 39823 List: LGTOaama-5.1.2-1.i386.rpm LGTOaamvm-5.1.2-1.i386.rpm VMware-vpxa-2.0.1-40644.i386.rpm

\[27747] 2007-03-13 11:20:03 AM: Rpmlist: VMware-vpxa-2.0.1-40644.i386.rpm LGTOaamvm-5.1.2-1.i386.rpm LGTOaama-5.1.2-1.i386.rpm

\[27747] 2007-03-13 11:20:03 AM: exec rpm -ev --allmatches VMware-vpxa

\[27747] 2007-03-13 11:20:03 AM: status = 0

\[27747] 2007-03-13 11:20:03 AM: exec rpm -ev --allmatches LGTOaamvm

Reply
0 Kudos