VMware Cloud Community
matt3
Contributor
Contributor

Failed to install the VirtualCenter Agent service

I installed VC2 and the lic. server. however when I start the VC2 up it prompts me for my user name and password. I finsh the wizard and when it goes to install the agent it give me the following:

\----


Error

\----


Failed to install the VirtualCenter Agent service

\----


OK

\----


Any help with this will be more then helpful.

Reply
0 Kudos
45 Replies
admin
Immortal
Immortal

Did you make sure there is enough disk space on the ESX host. You need at least 200MB. Is there a /var/log/vmware/vpx-iupgrade.log file on the ESX host?

Reply
0 Kudos
whynotq
Commander
Commander

I've got a similar issue, 2 hosts both at esx3 one in VI2 no problem second host "disconnected" when I try to connect it I eventually get "failed to install virtualcentre agent".

Reply
0 Kudos
CHogan
VMware Employee
VMware Employee

Generally, this suggests some sort of networking configuration issue between the ESX and the VC Server.

You could manually try to install the agent as follows:

\- Copy the vpx-upgrade-esx-5-linux-27704[/b] from the upgrade folder in the VC folder to /tmp on the ESX server

\- run the command sh vpx-upgrade-esx-5-linux-27704[/b]

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

After running the script, see if you can connect...

http://cormachogan.com
Reply
0 Kudos
Named_Jason
Contributor
Contributor

I'm having this issue as well. This environment may have an additional challenge, as the VC server is actually a VM running on the ESX server that I am trying to add.

I used the suggested manual install method above and the install seemed to go smoothly. However, I was still unable to connect to the server in the VC inventory. The error that it gives me on subsequent connection attempts is connection related, but since the COS and the VM are on the same VSwitch, I don't see how it could be a network related issue. Do you have any other advice? Thanks in advance.

Reply
0 Kudos
DarrenBolton
Contributor
Contributor

Im having the same problom after upgrading Virtual Center 1.2 to 2.0

Out of my 5 ESX 2.5.1 servers only two of them have reconnected, with the other three I get the "Failed to install the VirtualCenter Agent Service" I've tried to manual install mentioned in this thread to no avail.

It even shows back the host summary with the VM's that are configured on that host so it is deffinatly seeing it.

How would i stop and restart the VC Agent service on the ESX Server?

It gets to about 88% when adding the host into VC then bombs out, I dont think its connection related in my case as all the servers can see either and i can get putty sessions.

I've raised a support call with VMware.

Reply
0 Kudos
DarrenBolton
Contributor
Contributor

I've managed to fix this issue on my setup.

After upgrading VC to version 2 my 2.5.1 esx hosts would no longer connect.

To fix this I had to run the vpx-upgrade-esx-3-linux-27704 manually on the server from the Console.

These are located in the VirtualCenter install folder.

\VMware\VMware VirtualCenter 2.0\upgrade

If you look in bundleversion.xml you will be able to see which script it is that you need to run depending on what version your esx hosts are running.

Reply
0 Kudos
Iton
Contributor
Contributor

Look in the bundleversion.xml file for the correct filename for your ESX version upgrade.

I have VC 2.01 then the 3.0 agent is: vpx-upgrade-esx-6-linux-32042

Reply
0 Kudos
dphelps1
Contributor
Contributor

I'd like to thank you for providing this solution. It really worked for me.

Reply
0 Kudos
admin
Immortal
Immortal

Did you figure out why the automatic installation failed?

Reply
0 Kudos
RJ_Bruce
Contributor
Contributor

Manually copying over vpx-upgrade-esx-6-linux-32042 and executing it from the esx server console worked for me on two ESX hosts.

This was with a fresh 2.0.1 VI Server install and fresh 3.0.1 ESX servers. Any update as to the source of this issue and why the two .0.1 released products can't seem to handle the automated task?

Reply
0 Kudos
Vorraber
Contributor
Contributor

I had the same error after I had to reinstall the Virtual-Center Server.

In my case, copying the vpx-upgrade-esx-6-linux-33643 to the ESX-Host an installing it with sh command worked fine.

Reply
0 Kudos
system_ict
Contributor
Contributor

The manual install worked for me. Had the problem after upgrading my virtual center to build 33643, 2 ESX 3.0.1 servers would not update their virtualcenter agent.

Regards,

Raymond

Reply
0 Kudos
vmit
Contributor
Contributor

I had the same issue with 3 out of 10 ESX hosts after upgrading to VC2.0.1. I was able to get two working by removing them from VC and then rebooting them.

Reply
0 Kudos
FJAvm
Contributor
Contributor

I upgraded today from VC 2.01 to VC 2.01 Patch1. After the update i got excatly the same problem. Every Host of our DRS Cluster was disconnected with the message that the vc agent installation failed. When i recovered from the panic attack i got, i solved it that way:

On the Console of every ESX Host:

service mgmt-vmware restart

service vmware-vmkauthd restart

After that i reconnected the Hosts through the VC Client. I got prompted for the root credentials and after that, the updated VC agent got successfully installed.

Now i had my DRS cluster back, but with a big red question mark on it saying that the HA agent failed. The solution to this was to disable HA in the properties of the Cluster and after applying the changes to reenable it. Then the HA agent got reconfigured and restarted.

@VMWare

The whole installation was a pain in the a......... . I never got such problems when i moved from VC 2.0 to VC 2.01 . 2 hours blood sweat and tears, thanks for that.

The only problem left is that unlike stated in the release notes, the counter "CPU Wait" is not renamed in "CPU idle" . Somebody here made the same experience ??

Regards

Wolfgang

Reply
0 Kudos
admin
Immortal
Immortal

Can you look in the VC server logs to figure out why the agent install failed? Just search for the string "AgentInstallFailed". Thanks!

Reply
0 Kudos
FJAvm
Contributor
Contributor

Hi,

these are the corresponding entries:

\[2007-01-15 13:24:55.599 'App' 2488 warning] \[VpxdInvtHost] Bad vpxa build on host m-s-esx01.global.fjh.com (bundle version 6). Got <32042> Expecting <33643>
\[2007-01-15 13:24:55.630 'App' 2488 info] \[VpxdHostUpgrader] Scheduling auto-upgrade for host m-s-esx01.global.fjh.com
\[2007-01-15 13:24:55.677 'App' 964 info] \[VpxLRO] -- BEGIN task-1991 -- host-10 -- Upgrade.UpgradeAgent
\[2007-01-15 13:24:56.380 'StackTracer' 964 info] \[964] Enter DAS_PROFILE UpdateDasStatus
\[2007-01-15 13:24:56.396 'StackTracer' 964 info] \[964] Exit DAS_PROFILE UpdateDasStatus (15 ms)
\[2007-01-15 13:24:56.584 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

\* A certificate in the host's chain is based on an untrusted root.

\[2007-01-15 13:24:56.584 'BaseLibs' 964 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0

\[2007-01-15 13:24:56.584 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

\[2007-01-15 13:24:56.599 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

\* A certificate in the host's chain is based on an untrusted root.

\[2007-01-15 13:24:56.599 'BaseLibs' 964 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0

\[2007-01-15 13:24:56.599 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

\[2007-01-15 13:24:56.693 'App' 3340 info] \[VpxLRO] -- FINISH task-internal-14 -- host-39 -- VpxdInvtHostSyncHostLRO.Synchronize
\[2007-01-15 13:24:56.724 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

\* A certificate in the host's chain is based on an untrusted root.

\[2007-01-15 13:24:56.724 'BaseLibs' 964 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0

\[2007-01-15 13:24:56.724 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

\[2007-01-15 13:24:56.724 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

\* A certificate in the host's chain is based on an untrusted root.

\[2007-01-15 13:24:56.724 'BaseLibs' 964 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0

\[2007-01-15 13:24:56.724 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

\[2007-01-15 13:24:57.084 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

\* A certificate in the host's chain is based on an untrusted root.

\[2007-01-15 13:24:57.084 'BaseLibs' 964 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0

\[2007-01-15 13:24:57.084 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

\[2007-01-15 13:24:57.084 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

\* A certificate in the host's chain is based on an untrusted root.

\[2007-01-15 13:24:57.084 'BaseLibs' 964 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0

\[2007-01-15 13:24:57.084 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

\[2007-01-15 13:24:57.115 'App' 2488 warning] \[VpxdInvtHost] Bad vpxa build on host m-s-esx03.global.fjh.com (bundle version 6). Got <32042> Expecting <33643>
\[2007-01-15 13:24:57.130 'App' 2488 warning] \[VpxdInvtHost] Bad vpxa build on host m-s-esx02.global.fjh.com (bundle version 6). Got <32042> Expecting <33643>

\[2007-01-15 13:24:57.193 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

\* A certificate in the host's chain is based on an untrusted root.

\[2007-01-15 13:24:57.193 'BaseLibs' 964 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0

\[2007-01-15 13:24:57.193 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

\[2007-01-15 13:24:57.193 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

\* A certificate in the host's chain is based on an untrusted root.

\[2007-01-15 13:24:57.193 'BaseLibs' 964 warning] SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0

\[2007-01-15 13:24:57.193 'BaseLibs' 964 warning] SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error

\[2007-01-15 13:24:58.709 'App' 964 warning] ============BEGIN FAILED METHOD CALL DUMP============

\[2007-01-15 13:24:58.709 'App' 964 warning] Invoking \[prepareToUpgrade] on \[vim.AgentManager:ha-agentmgr]

\[2007-01-15 13:24:58.709 'App' 964 warning] Fault Msg: "A general system error occured: Create upgrade tmp directory failed"

\[2007-01-15 13:24:58.709 'App' 964 warning] ============END FAILED METHOD CALL DUMP============

\[2007-01-15 13:24:58.709 'App' 964 error] \[VpxdHostAccess] PrepareToUpgrade on hostd failed: vmodl.fault.SystemError

\[2007-01-15 13:24:58.709 'App' 964 error] \[VpxdHostUpgrader] Failed to get directory in which to upload script

\[2007-01-15 13:24:58.787 'App' 964 error] \[VpxdHostUpgraderLRO] Failed to upgrade host m-s-esx01.global.fjh.com: vim.fault.AgentInstallFailed

\[2007-01-15 13:24:58.927 'App' 964 info] \[VpxLRO] -- FINISH task-1991 -- host-10 -- Upgrade.UpgradeAgent

Reply
0 Kudos
admin
Immortal
Immortal

Thanks very much. This is a bug we're seen before but it doesn't occur consistently so has been hard to diagnose. Can you post the hostd logs from the same time period (/var/log/vmware/hostd.log on the ESX host)?

Reply
0 Kudos
AlexPT
Contributor
Contributor

Hi, I had the same issue. To fix try this:

Stop the Managerment Agent - /etc/inid.d/mgmt-vmware Stop

Stop the Authorisation daemon - /etc/inid.d/vmware-authd Stop

Stop the ESX Server Agent - /etc/inid.d/vmware-vpxa Stop

Make sure the host is removed from VIC2 (if using it)

Then start in the same order. Give it an hour or two before trying to connect the host again (if in VIC) or try connecting to the host directly via VIC or HTTPS://hostname.

It worked for me. After approx 1 1/2 hours I was able to add back my host to VIC.

Let us know how it worked - if it did.

Alex

Reply
0 Kudos
AlexPT
Contributor
Contributor

..And as eziskind says make sure there's enough room for install (/ root):

vdf -h

Reply
0 Kudos