I have a ESXi v6.5 running on IBM M2. The ESXi is managed by vCenter V6.7. I tried to patch the ESXi with Update Manager. Update manager always fails with error, The host returns esxupdate error codes: -1. Check the Update Manager log files and esxupdate log files for more details.
The update manager and vCenter are installed on Windows 2012 Server. Please advise how I can proceed to troubleshoot and fix the issue.
Hi Guy,
My platform below:
vCenter 6.7
3 x ESXi Host server v6.7 Update 01 (Cluster enabled)
I migrate out all running vm to other host, then I using Update Manager to update the ESXi host server form ESXi v6.7 Update 01 to 03, it is no prompt for ESXi host restart, and the build already updated show in vCenter.
So, may I ask using Update Manager to patch ESXi host server, does it need restart the ESXi server?
Regards
Thanks...KEN
So I need to go to a specific version of ESXi in my lab environment in order to carry out a test to try and diagnose a fault in our production environment, we have the latest build of 6.7 installed in our lab as we used it as the test bed before we rolled the upgrade out to our production servers.
We had an issue with one cluster which vmware cant seem to find the root cause of without further information, they want me to test the precise steps we took in upgrading the environment in a test lab so I need to install the same version that is in the production problem cluster.
The target version is an older build of 6.7, now if I add the ISO to update manager, build a baseline and apply it to the hosts will it install the older version or will I have to wipe and install and reconfigure everything?
Just updated our vSphere appliance to 6.5.0 Build 15259038.
One of the reasons for this upgrade was to bring Update Manager into the HTML5 view rather than the Flash view. The upgrade went fine, I can see the update manager plug-in is enabled in the flash client as you cant see plugins in the html client.
But on the html client still not seeing update manager. I created a new local admin user to test and does not shop up for them so assuming its not a permissions issue, I have restarted the services and the VSCA server to no avail.
Does anyone know how to resolve this?
Hello,
is update manager is available in all editions
I have created a new host upgrade baseline using Lenovo ESXi 6.7U3 custom image and now when I try to update the host I get error message - "Cannot copy files to host data.host. Check the management service status, network connectivity with vCenter and disk space on the host.".
I checked the vpxa logs on the host and update manager logs in vCenter and I see the following warning
2020-03-27T08:02:05.112Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcNewAuthdConnectionEx: Setting TCP timeouts: keepIdle 60 keepIntvl 6 keepCnt 8
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFileLocalizePath: Translated ./ssl/rui.crt -> ./ssl/rui.crt
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Open: Local filename = './ssl/rui.crt'
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFileGetOpsReal: using raw fns
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFileRawOpen: Opening file './ssl/rui.crt' access 1 action 0
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: start
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcReserveStreamMem: Allocated stream memory of size 262144
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFileRawRead: Got EOF, while 1428 left to read
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 1428 bytes from file
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFileRawRead: Got EOF, while 0 left to read
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 0 bytes from file
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: got eof
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: apparently file was succesfully sent
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcUnreserveStreamMem: Freed stream memory of size 262144
2020-03-27T08:02:05.231Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcSendFileInt: Waiting for file put to complete on peer
2020-03-27T08:02:05.234Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_DestroyHandle: returns
2020-03-27T08:02:05.234Z warning vmware-vum-server[100798] [Originator@6876 sub=Libs] [NFC ERROR] NfcSendFile: Failed to get sidecar paths: NFC_SUCCESS (The operation completed successfully)
2020-03-27T08:02:05.262Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] Using proxy/session authentication, sessionId=52 84 63 da c2 d2 a3 45-7d b4 40 1f 27 e6 39 cf, useSSL=1
2020-03-27T08:02:05.901Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcNewAuthdConnectionEx: Setting TCP timeouts: keepIdle 60 keepIntvl 6 keepCnt 8
2020-03-27T08:02:06.027Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFileLocalizePath: Translated ./docroot/vci/vua/eesx6/vua.sh -> ./docroot/vci/vua/eesx6/vua.sh
2020-03-27T08:02:06.027Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Open: Local filename = './docroot/vci/vua/eesx6/vua.sh'
2020-03-27T08:02:06.027Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFileGetOpsReal: using raw fns
2020-03-27T08:02:06.027Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFileRawOpen: Opening file './docroot/vci/vua/eesx6/vua.sh' access 1 action 0
2020-03-27T08:02:06.027Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: start
2020-03-27T08:02:06.027Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcReserveStreamMem: Allocated stream memory of size 262144
2020-03-27T08:02:06.027Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 262144 bytes from file
2020-03-27T08:02:06.049Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 262144 bytes from file
2020-03-27T08:02:06.064Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 262144 bytes from file
2020-03-27T08:02:06.073Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 262144 bytes from file
2020-03-27T08:02:06.080Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 262144 bytes from file
2020-03-27T08:02:06.085Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 262144 bytes from file
2020-03-27T08:02:06.093Z info vmware-vum-server[100798] [Originator@6876 sub=Default] [,0] [NFC DEBUG] NfcFile_Send: about to send 262144 bytes from file
The update process goes till 92% and then it fails with error - "Cannot copy files to host data.host. Check the management service status, network connectivity with vCenter and disk space on the host."
How to fix it?
We recently upgraded from vcenter 6.5 to 6.7. We also updated all the hosts to 6.7 as well but when I go into VUM, I do not see 6.7 patches. Additionally, when I create a new baseline, I do not have the option for 6.7 under the product field.
Attempting to upload image into vCenter Update Manager. Uploading file progress bar moves pretty quickly most of the way to 100%, then restarts a few times, then quits here. No error beyond the red banner.
I've updated vCenter and still have this. No idea what to look at next as there is no error. G Search indicates one cannot upload an older image but this one is not older.
Thanks
I updated a VM's Hardware to match host first. After that completed, I went to update the VMware Tools to match host but now I get a red bar with a message stating
An unexpected error has occurred.
Every time I go to the Updates tab for this VM, I get this message. I also get this message when I go to the Host and click the Updates tab > VMware tools. IF I move the VM off this host and then go back to the Updates tab of the host, it works fine and tells me an overview of what VMs need updates for VMware Tools.
I was able to update the VMware tools of this VM by clicking an update now link in the summary tab of the VM. I confirmed the newer version on the VM via server itself. This errror though still remains for this VM. I have restarted the upgrade manager service in the VMware Appliance but sadly no luck.
I have attached some screenshots of this error. Any ideas on a solution?
Hi,
I'm facing this error everytime on my vCenter 6.7:
I tried restarting the service, but everytime I logon again on vCenter it continues to show up.
Any advice?
A driver or provider component kit can be installed on esxi host using esxcli commands. However a user needs to login to the esxi host using a SSH client and then issue esxcli software install commands. Can this same operation be done via vSphere web client ? A file i.e. the kits can be copied to the local data-store of the esxi host using vSphere. After this is there a way to issue esxcli software install commands on the esxi hosts connected to vSphere?
I'm trying to update the VM Hardware in vCenter, but I keep receiving an error message that states "Errors during the scan operation for virtual hardware upgrade". Why am I receiving this error message?
I upgraded to vSphere 7 in my lab environment and noticed a strange issue that causes Lifecycle Manager not to load and work within vCenter v7.
I was coming from a VCSA 6.7 install which had an externally signed SSL cert added to replace the Machine Cert in vCenter that way when I load vCenter in web browser, it doesn't complain about a self-signed certificate. Everything worked great.
When I updated to VCSA 7, the update wizard told me I must reset the certificates back to VCMA certs since something about trust blah blah blah. I followed the KB article it provided which brough my 6.7 back to using vCenter generated self-signed cert. I retried the update to v7 and it worked fine. After upgrade I replaced the Machine SSL certs with my externally signed certs (from Namecheap, domain specific, not wildcard) and vCenter v7 said it was changed successfully and it rebooted the appliance. I can now login to Web UI without annoying warnings, great.
However, if I click "Lifecycle Manager" in vCenter v7, I get a red bar that pops up over that section that loads that says Status 404 - Error and list a URL that has to do with Lifecycle Manager I guess. And below, nothing loads in Lifecycle Manager, clicking any of the buttons doesn't do anything, or just produces more errors like "An unexpected error has occurred". Similar result if I click "Updates" tab on a host of cluster. Nothing to do with LM loads or works. everything else in VC seems to work fine, including proper serving of the signed SSL cert in my web browser.
If I go back to Certificate Management and change the Machine SSL cert back to one generated by vCenter as self-signed, after reboot, Lifecycle Manager works again.
Any ideas? Obviously LM doesn't like something about the externally signed cert even though it works everywhere else.
Hey guys,
I have a 6.7u2 vSphere environment(vCSA and hosts) and I have a HPE Synergy frame/SPP combination that only supports 6.7u2. It does not support 6.7u3 until we upgrade(VCSA 1st, HPE Synergy Frame Composer 2nd, HPE Synergy Frame Hardware 3rd, and Synergy Server SPPs 4th) later this year. I want to apply vSphere security patches through VUM, but noticed the default critical baseline automatically include 6.7 complete update 3, which both my vCenter server and hardware are not ready for yet. Is there a simple way to exclude the 6.7 complete update 3, and also any of its included componenets that might cause issues from a VUM baseline?
I have always had concerns about remaining in a supported configuration and following the correct upgrade path. Because of that, typically it has been easier to wait until we run all HPE updates first, confirm what version of VMWare they support, and then apply all VMWare updates after. I know I can try to piece together a baseline without 6.7 complete update 3, but figuring out what should and should not go in there can be tough. If anyone has a good process for updating a VMWare environment, or how to comfortably apply needed updates without u3 and the modules that go in it, etc. it would really be appreciated
Hey all,
In my lab environment I've started kicking the tires of vSphere Lifecycle Manager and I'm running into this weird issue that's rendering it nonfunctional.
I can create a cluster image without an issue, but after I upload the PowerPathVE add-on component, vLCM comes up with the below error. I even went through the process of reimaging and redeploying vCenter just to sanity check and unfortunately I've ended up with the same result. Interestingly, I can still manage the cluster image and remediate hosts from the hosts and clusters view but if I try to go to vLCM everything is blank and I get the error.
Anyone else hitting this? Any ideas?
Hi everyone,
I'd like to know how can I install ESXi updates on ESXi 6.7. I have the following scenario (as shown in the picture below):
It seems there are some updates to apply, but I don't know which ones I have to apply. What's the next step? When I click on the "check compliance" link, nothing happens.
Thank you.
Author : Martina Laleva
Topic Name : Import Patches Manually
Publication Name : vSphere Update Manager Installation and Administration Guide
Product/Version : VMware vSphere/6.7
Question :
hello! it is great to have the opportunity to manually import patches, but please add to the documentation how to remove them as well. thanks in advance!
Update Manager is missing from vCenter7.0 after upgrading from 6.7. i also reboot vCenter and also follow VMware Knowledge Base .
but it did not fixed the issue.
I recently upgraded to VCSA 6.5. I've never used VUM, but I want to use it. VUM is unable to connect with VMware.com.
I'm using VMware VCSA 6.5.0-7312210
I've set the proxy server on the VCSA. When I test the connection, using the GUI, I get a message that says that Internet connection test can access http://www.microsoft.com, but not http://www.vmware.com.
When I look in the log file on the vcsa, I see messages like:
2018-01-12T04:47:03.038Z warning vmware-vum-server[7F12BD106700] [Originator@6876 sub=Default] File download error: downloading file: https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main/csco-depot-index.xml failed, 0 bytes downloaded.. Retrying^M
But when I run "wget https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main/csco-depot-index.xml" in /tmp, I get an xml file that is the same as running the wget on a Linux system in the same subnet:
<?xml version="1.0" encoding="UTF-8"?>
<vmwdpm:vendorList xmlns:vmwdpm="http://www.vmware.com/depotmanagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.vmware.com/depotmanagement ../../depot-index-xml.xsd">
<vendor>
<name>Cisco Systems, Inc.</name>
<code>csco</code>
<indexfile>csco-index.xml</indexfile>
<relativePath>esx/csco</relativePath>
</vendor>
<vendor>
<name>Cisco Systems, Inc.</name>
<code>csco</code>
<indexfile>csco-esx-index.xml</indexfile>
<relativePath>esx/csco</relativePath>
<content>
<name>VMware ESX</name>
<type>http://www.vmware.com/depotmanagement/esx</type>
</content>
</vendor>
</vmwdpm:vendorList>
Why is VUM running on the VCSA having trouble connecting to
http://vapp-updates.vmware.com
?
Need a setup file for VCenter 6.7 for Windows OS. Can someone please help me on this?