Hi , I have a VCSA 6.7 with Build number 11726888 , A few days ago, VUM service began to fail and shows the following error, the service is stopped and when I try to start it, the following error is observed

could someone please give me some idea what is causing the failure???, thanks

ERROR TEXT

root@vcenter [ ~ ]# service-control --start vmware-updatemgr

Operation not cancellable. Please wait for it to finish...

Performing start operation on service updatemgr...

Error executing start on service updatemgr. Details {

    "detail": [

        {

            "localized": "An error occurred while starting service 'updatemgr'",

            "translatable": "An error occurred while starting service '%(0)s'",

            "id": "install.ciscommon.service.failstart",

            "args": [

                "updatemgr"

            ]

        }

    ],

    "componentKey": null,

    "problemId": null,

    "resolution": null

}

Service-control failed. Error: {

    "detail": [

        {

            "localized": "An error occurred while starting service 'updatemgr'",

            "translatable": "An error occurred while starting service '%(0)s'",

            "id": "install.ciscommon.service.failstart",

            "args": [

                "updatemgr"

            ]

        }

    ],

    "componentKey": null,

    "problemId": null,

    "resolution": null

}

I have ESXi 6.7 update 2 installed and want to apply all the latest security patches to this. In vcenter I am only seeing patches from August 2019. Is this because August 2019 is when Update 3 came out so to apply the latest security patches to my hosts I need to upgrade to Update 3 first?

Fresh install on an HPE DL380 gen10 using HPE 6.7 U3 Custom ISO with VCSA 6.7 U3a.

In the Critical Host Patches predefined baseline, VCSA shows three missing items:

• Updates elx-esx-libelxima.so VIB
• VMware ESXi 6.7 Complete Update 2
• VMware ESXi 6.7 Complete Update 3

The Non-Critical Host Patches predefined baseline also shows a number of patches missing which are included in 6.7 U2 and U3.  When viewing the Updates tab for the host, the "Installed on Host" section shows 6.7.0 build 14320388 which corresponds with 6.7 U3.

Is there some way to correct VUM so it properly see the host is running 6.7 U3 and stops reporting that it needs patches which are already installed?

ESXi 6.7.0 Build 13981272

On the web client, when I click the Updates tab on one of the hosts, or the cluster, the expected behavior is present.  However, when I highlight a VM and click the Updates tab, I get "An unexpected error has occurred".  This happens on every VM when it is selected.  I can scan/remediate from the host or the cluster level, I just cannot do so from the VM level.  Any ideas?

I've attached a screenshot of the updates tab from both the host, and the VM to illustrate the issue I am having. 

Just installed VCSA67u3a.

Update Manager has a bunch of stuff for 6.0.0. How do I purge these? It says there are 406 updates.

I ONLY want updates for the version I am running. Not anything OLDER.

is there a doc somewhere?

Hi all,

I wonder if there is such an instrument in VMware structure which can manage several vCenter Update Managers, on any level (vCloud Director, any of vRealize, etc)?

Have anyone ever met something with this functionality?

All of the guides list vmware-umds -E as one of the final steps.  Is it necessary?  Can I just place the IIS virtual directory on C:\ProgramData\VMware\VMware Update Manager\Data and call it a day?  It seems to be working but I haven't actually patched anything with it yet.

The export step seems superfluous as it just makes a copy of everything UMDS has downloaded.  Or does it?  Does it compile metadata into an XML or something?

I have a couple of Dell ESX hosts, running 5.5 and am in the process of updating them to 6.7.

So far I've updated the vCentre host to 6.5 and it works fine. (This is the Linux appliance which replaces our older Windows vCentre) and used the custom Dell image for 6.5U3 to upgrade one of the two hosts with no issues. This now runs fine.

However, attempting to use the u/grade manager to achieve the same ting on the second Dell host results in a 'cannot execute script' error.

I've reboot the host and retried but get the same result.

Checking the vua.log does not show any bootbank/state or altbootbank messages, so I don't think it's any junk in a state.xxxx dir.

Below is the esxupdate log.

2018-10-06T15:31:22Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-01-13T16:20:13Z esxupdate: root: INFO: Command = profile.setacceptance

2019-01-13T16:20:13Z esxupdate: root: INFO: Options = {}

2019-01-13T16:20:13Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-01-13T16:20:13Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-01-13T16:20:13Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-01-13T16:20:13Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-01-13T16:20:13Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-01-13T16:20:13Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-01-13T16:20:13Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-01-13T16:20:13Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-01-13T17:02:52Z esxupdate: root: INFO: Command = profile.setacceptance

2019-01-13T17:02:52Z esxupdate: root: INFO: Options = {}

2019-01-13T17:02:52Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-01-13T17:02:52Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-01-13T17:02:52Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-01-13T17:02:52Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-01-13T17:02:52Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-01-13T17:02:52Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-01-13T17:02:52Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-01-13T17:02:52Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-08-20T16:38:43Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetTimeout']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-08-20T16:38:43Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRetries']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-08-20T16:38:43Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRateLimit']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-08-20T16:38:43Z esxupdate: esxupdate: INFO: ---

Command: scan

Args: ['scan']

Options: {'nosigcheck': None, 'retry': 5, 'loglevel': None, 'cleancache': None, 'viburls': None, 'meta': ['http://192.168.16.17:9084/vum/repository/hostupdate/csco/csco-VEM-5.5.0-metadata.zip', 'http://192.168.16.17:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.5.0-metadata.zip'], 'proxyurl': None, 'timeout': 30.0, 'cachesize': None, 'hamode': True, 'maintenancemode': None}

2019-08-20T16:38:43Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-08-20T16:38:43Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-08-20T16:38:43Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-08-20T16:38:43Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-08-20T16:38:44Z esxupdate: downloader: DEBUG: Downloading http://192.168.16.17:9084/vum/repository/hostupdate/csco/csco-VEM-5.5.0-metadata.zip to /tmp/tmpmqRxn3...

2019-08-20T16:38:44Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2019-08-20T16:38:44Z esxupdate: downloader: DEBUG: Downloading http://192.168.16.17:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.5.0-metadata.zip to /tmp/tmpLAN4NO...

2019-08-20T16:38:44Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2019-08-20T16:38:45Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-08-20T16:38:45Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-08-20T16:38:45Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/usr/sbin/vsish', '-e', '-p', 'cat', '/hardware/bios/dmiInfo']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-08-20T16:38:45Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/smbiosDump']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-08-20T16:38:45Z esxupdate: esxupdate: INFO: All done!

2019-08-20T16:38:45Z esxupdate: esxupdate: DEBUG: <<<

2019-11-14T10:52:38Z esxupdate: root: INFO: Command = profile.setacceptance

2019-11-14T10:52:38Z esxupdate: root: INFO: Options = {}

2019-11-14T10:52:38Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-14T10:52:38Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-14T10:52:38Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-14T10:52:38Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-14T10:52:38Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-11-14T10:52:38Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-14T10:52:38Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-11-14T10:52:38Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-11-14T11:11:08Z esxupdate: root: INFO: Command = profile.setacceptance

2019-11-14T11:11:08Z esxupdate: root: INFO: Options = {}

2019-11-14T11:11:08Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-14T11:11:08Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-14T11:11:08Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-14T11:11:08Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-14T11:11:08Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-11-14T11:11:08Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-14T11:11:08Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-11-14T11:11:08Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-11-20T11:06:26Z esxupdate: root: INFO: Command = profile.setacceptance

2019-11-20T11:06:26Z esxupdate: root: INFO: Options = {}

2019-11-20T11:06:26Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T11:06:26Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T11:06:26Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:06:26Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:06:26Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-11-20T11:06:26Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:06:26Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-11-20T11:06:26Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-11-20T11:40:34Z esxupdate: root: INFO: Command = profile.setacceptance

2019-11-20T11:40:34Z esxupdate: root: INFO: Options = {}

2019-11-20T11:40:34Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T11:40:34Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T11:40:34Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:40:34Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:40:34Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-11-20T11:40:34Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:40:34Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-11-20T11:40:34Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-11-20T11:49:59Z esxupdate: root: INFO: Command = profile.setacceptance

2019-11-20T11:49:59Z esxupdate: root: INFO: Options = {}

2019-11-20T11:49:59Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T11:49:59Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T11:49:59Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:49:59Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:49:59Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-11-20T11:49:59Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T11:49:59Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-11-20T11:49:59Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-11-20T19:00:19Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetTimeout']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:19Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRetries']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:19Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRateLimit']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:20Z esxupdate: esxupdate: INFO: ---

Command: scan

Args: ['scan']

Options: {'nosigcheck': None, 'retry': 5, 'loglevel': None, 'cleancache': None, 'viburls': None, 'meta': ['http://192.168.16.17:9084/vum/repository/hostupdate/csco/csco-VEM-5.5.0-metadata.zip', 'http://192.168.16.17:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.5.0-metadata.zip'], 'proxyurl': None, 'timeout': 30.0, 'cachesize': None, 'hamode': True, 'maintenancemode': None}

2019-11-20T19:00:20Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T19:00:20Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T19:00:20Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:20Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:20Z esxupdate: downloader: DEBUG: Downloading http://192.168.16.17:9084/vum/repository/hostupdate/csco/csco-VEM-5.5.0-metadata.zip to /tmp/tmpQxPQHN...

2019-11-20T19:00:20Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2019-11-20T19:00:20Z esxupdate: downloader: DEBUG: Downloading http://192.168.16.17:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.5.0-metadata.zip to /tmp/tmpPDT3Yf...

2019-11-20T19:00:21Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2019-11-20T19:00:21Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T19:00:21Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T19:00:22Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/usr/sbin/vsish', '-e', '-p', 'cat', '/hardware/bios/dmiInfo']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:22Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/smbiosDump']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:22Z esxupdate: esxupdate: INFO: All done!

2019-11-20T19:00:22Z esxupdate: esxupdate: DEBUG: <<<

2019-11-20T19:00:55Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetTimeout']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:55Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRetries']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:55Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRateLimit']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:55Z esxupdate: esxupdate: INFO: ---

Command: scan

Args: ['scan']

Options: {'nosigcheck': None, 'retry': 5, 'loglevel': None, 'cleancache': None, 'viburls': None, 'meta': ['http://192.168.16.17:9084/vum/repository/hostupdate/csco/csco-VEM-5.5.0-metadata.zip', 'http://192.168.16.17:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.5.0-metadata.zip'], 'proxyurl': None, 'timeout': 30.0, 'cachesize': None, 'hamode': True, 'maintenancemode': None}

2019-11-20T19:00:55Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T19:00:55Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T19:00:55Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:55Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:56Z esxupdate: downloader: DEBUG: Downloading http://192.168.16.17:9084/vum/repository/hostupdate/csco/csco-VEM-5.5.0-metadata.zip to /tmp/tmpTylmS6...

2019-11-20T19:00:56Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2019-11-20T19:00:56Z esxupdate: downloader: DEBUG: Downloading http://192.168.16.17:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.5.0-metadata.zip to /tmp/tmpWwZE0t...

2019-11-20T19:00:56Z esxupdate: Metadata.pyc: INFO: Unrecognized file vendor-index.xml in Metadata file

2019-11-20T19:00:56Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T19:00:56Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-11-20T19:00:57Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/usr/sbin/vsish', '-e', '-p', 'cat', '/hardware/bios/dmiInfo']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:57Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/smbiosDump']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-11-20T19:00:57Z esxupdate: esxupdate: INFO: All done!

2019-11-20T19:00:57Z esxupdate: esxupdate: DEBUG: <<<

2019-12-26T18:18:45Z esxupdate: root: INFO: Command = profile.setacceptance

2019-12-26T18:18:45Z esxupdate: root: INFO: Options = {}

2019-12-26T18:18:45Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-12-26T18:18:45Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-12-26T18:18:45Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-12-26T18:18:45Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-12-26T18:18:45Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-12-26T18:18:45Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-12-26T18:18:45Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-12-26T18:18:45Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-12-26T18:35:50Z esxupdate: root: INFO: Command = profile.setacceptance

2019-12-26T18:35:50Z esxupdate: root: INFO: Options = {}

2019-12-26T18:35:50Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-12-26T18:35:50Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg

2019-12-26T18:35:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-12-26T18:35:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-12-26T18:35:50Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.5.0-3.78.3248547 to ImageProfile Dell-ESXi-5.5U3-3568722-A06

2019-12-26T18:35:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-12-26T18:35:50Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-12-26T18:35:50Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

and attached is the vua.log - can anyone please suggest where I might look to work around this?

I did wonder about both 'acceptance level' and free space.. see these lines from vua.log.. but there is no actual log 'failure' entry I can see.

--> DEBUG:root:Running /sbin/localcli --formatter=json storage filesystem list

--> DEBUG:root:Running vib conflicts check.

--> INFO:root:Image size: 160 MB, Maximum size: 239 MB

--> INFO:root:Locker currently have 211055068 bytes in package folder, and 88145920 bytes free. Incoming image has 161582107 bytes of locker payloads, estimate to take 200582356 bytes of space.

--> INFO:root:Running command /sbin/esxcfg-advcfg -U host-acceptance-level -G

--> INFO:root:Host acceptance level is partner, target acceptance level is partner

--> INFO:root:Running /sbin/localcli system visorfs ramdisk remove -t /upgrade_scratch

Many thanks

David

Good Afternoon:

We're seeing this message when attempting to launch the update manager on one of our Vcenter environments.   If we look at the updatemgr-utility.log file in /var/log/vmware/vmware-updatemgr we're seeing the following:

Was wondering if anyone could help point us in the right direction as to how to get our update manager functioning again.  Please let me know if I can provide any additional information that may help pinpoint the issue.

Thanks!

After migrating from Windows 5.5 vCenter to VCSA 6.5 Update1 (intermediate step to 6.7) everything was working well. After the migration the vcenter machine cert was soon to be expired so I replaced it, though I did notice https://vc.domain.com:7444 was still using the old cert. I didn't worry about this as the old cert was not expired. A month or so passes by with vcenter being very stable. Completed host upgrades to 6.5U1 using VUM over the weekend - In the mean time the cert bound to 7444 expired, which caused problems with the Migration wizard to 6.7. Also, VUM service had stopped and wouldn't start (perhaps it was ok until I rebooted the VCSA and now VUM wont start)

With the help of VMWare support we fixed this by replacing the cert in the STS_INTERNAL_SSL_CERT. This fixed the expired cert for 7444 but did not help with the VUM issues. I'm pretty well stuck, I am just waiting on VMWare support to help. In the mean time I thought I'd post here in case someone could possible help.

Regards

I get the following errors in the SSH session when executing service-control --start vmware-updatemgr:

Error executing start on service updatemgr. Details {

    "resolution": null,

    "detail": [

        {

            "args": [

                "updatemgr"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'updatemgr'",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

Service-control failed. Error {

    "resolution": null,

    "detail": [

        {

            "args": [

                "updatemgr"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'updatemgr'",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

tail -f updatemgr-utility.log give this:

[2018-10-10 23:29:10,255 INFO] Install Key store for Jetty

[2018-10-10 23:29:11,579 INFO] Keystore installed successfully.

[2018-10-10 23:29:11,953 INFO] Updating VUM extension with VC

[2018-10-10 23:29:12,236 INFO] Updating CM service info

[2018-10-10 23:29:12,402 ERROR] CM ReRegisterService failure. Exception is (cis.cm.fault.ComponentManagerFault) {

   dynamicType = <unset>,

   dynamicProperty = (vmodl.DynamicProperty) [],

   msg = '',

   faultCause = <unset>,

   faultMessage = (vmodl.LocalizableMessage) [],

   errorCode = 0,

   errorMessage = 'UNKNOWN'

}

[2018-10-10 23:29:12,402 ERROR] Unable to update CM service info

Tail on cm.log give me this while starting service:

2018-10-10T23:24:35.847Z [pool-2-thread-1 [] WARN  com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore (f15657f3-ac72-40f0-8c90-3e948201000c)] Call to lookup service failed; uri:https://VCENTER.DoMain.int/lookupservice/sdk [(vmodl.fault.InvalidArgument) {

   faultCause = null,

   faultMessage = null,

   invalidProperty = Invalid certificate

}]

2018-10-10T23:24:35.847Z [pool-2-thread-1 [] ERROR com.vmware.cis.services.cm.service.ServiceManagerImplTemplate (f15657f3-ac72-40f0-8c90-3e948201000c)] reRegisterService v1: Failed to re-register c39131ca-cda5-446d-a6ac-44b51348c107 (vpxd-extension-a6f84462-5ea2-11e6-ada6-0050569777b5@vsphere.local, com.vmware.vcIntegrity/vcIntegrity 6.5.0)

com.vmware.vim.binding.vmodl.fault.InvalidArgument: null

        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_141]

        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_141]

        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_141]

        at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_141]

        at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_141]

        at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:150) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:101) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:88) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:83) ~[vlsi-core.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:40) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:274) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:230) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:613) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:594) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:345) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:305) ~[vlsi-client.jar:?]

        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:179) ~[vlsi-client.jar:?]

        at com.sun.proxy.$Proxy101.set(Unknown Source) ~[?:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper$3.execute(LsVmomiSiteStore.java:229) ~[service-cm.jar:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper$3.execute(LsVmomiSiteStore.java:226) ~[service-cm.jar:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper.callLs(LsVmomiSiteStore.java:302) ~[service-cm.jar:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore$LsVmomiWrapper.set(LsVmomiSiteStore.java:224) ~[service-cm.jar:?]

        at com.vmware.cis.services.cm.service.impl.LsVmomiSiteStore.updateService(LsVmomiSiteStore.java:622) ~[service-cm.jar:?]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_141]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_141]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_141]

        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_141]

        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at com.vmware.cis.services.common.perfmon.PerfmonInterceptor.invoke(PerfmonInterceptor.java:31) ~[service-common.jar:?]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) ~[spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at com.sun.proxy.$Proxy67.updateService(Unknown Source) ~[?:?]

        at com.vmware.cis.services.cm.service.ServiceManagerImplTemplate.reRegisterService(ServiceManagerImplTemplate.java:306) [service-cm.jar:?]

        at com.vmware.cis.services.cm.service.ServiceManagerImpl.reRegisterService(ServiceManagerImpl.java:291) [service-cm.jar:?]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_141]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_141]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_141]

        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_141]

        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at com.vmware.cis.services.common.perfmon.PerfmonInterceptor.invoke(PerfmonInterceptor.java:31) [service-common.jar:?]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) [spring-aop-4.3.9.RELEASE.jar:4.3.9.RELEASE]

        at com.sun.proxy.$Proxy68.reRegisterService(Unknown Source) [?:?]

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_141]

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_141]

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_141]

        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_141]

        at com.vmware.vim.vmomi.server.impl.InvocationTask.run(InvocationTask.java:65) [vlsi-server.jar:?]

        at com.vmware.vim.vmomi.server.common.impl.RunnableWrapper$1.run(RunnableWrapper.java:47) [vlsi-server.jar:?]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_141]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_141]

        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141]

tcpdump on lo gives:

Request

POST /lookupservice/sdk HTTP/1.1

Content-Type: text/xml; charset=utf-8

SOAPAction: urn:lookup/2.0

Content-Length: 21474

Host: https://VCENTER.DoMain.int/lookupservice/sdk

Connection: Keep-Alive

User-Agent: VMware vim-java 1.0

Cookie: vmware_soap_session=a7600162-79b1-4797-9e7f-4b885dde550b

Accept-Encoding: gzip,deflate

X-Forwarded-For: 127.0.0.1

X-Forwarded-Proto: https

....CERT HASH in XML stream.........

Request

HTTP/1.1 500

Set-Cookie: vmware_soap_session=a7600162-79b1-4797-9e7f-4b885dde550b; HttpOnly

Content-Type: text/xml;charset=utf-8

Content-Length: 558

Date: Wed, 10 Oct 2018 01:45:27 GMT

Connection: close

<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Fault><faultcode>ServerFaultCode</faultcode><faultstring/><detail><RuntimeFaultFault xsi:type="InvalidArgument" xmlns="urn:lookup"><invalidProperty>Invalid certificate</invalidProperty></RuntimeFaultFault></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

I started writing this up as a question about putting ESXi at 6.5 u3 while vCenter Server remains at 6.5 u2, however it gave me a realization that has led to a follow-up question.

I then answered that question as I was writing it up, and I have another. *sigh*.

How do I (easily) have Patch Manager download the updates for an ESXi baseline to only include 6.5 u2 patches, and not u3 patches. When on 6.0, I recall applying some patches one day and was surprised to see I had gone from u1 to u2 by virtue of the patches I applied. The numbering/labeling schema of the ESXi updates don't easily/obviously (AFAI can tell) reference whether the patch is for a u2 or u3 release of 6.5.

Any recommendations on 'bypassing' the u3 updates for ESXi would be wonderful - my NSX is still on 6.3.x which isn't supported with 6.5 u3 vCenter/ESXi.

Hello,

Another noob question that I don't understand what I have done wrong.

I have 2 VMs running on ESXi, the one named vCenterServer has vCenter Server and Update Manager both installed on that VM. I used the embedded database.

After installing, I cannot find the Update Manager in either the web or vsphere console. What am I doing wrong?

Hi all,

I upgraded recently to VCSA 6.7 U3 and have an issue with the Update Manager.

I download the patches from an Update Manager Download Service repository.

When I download patches the system returns a successful status for the download but the patch list remains empty.

I ran DB reset on the VCSA as per VMware KB 2147284 to no effect.

Importing offline update packages works.

I haven't found any online notes regarding this issue.

I'm hoping someone has come across it.

Thanks

Gadi

  Good Morning,

We have recently upgraded on vCenters to version 6.7U3. 

Now we are trying to upgrade our hosts to the same version.  Using Update Manager to upgrade.

Seems like we are having an issue with trying to do multiple hosts with the same baseline or even a different baseline.

If you only do one host, no issues. Example I had one host that was doing a remediation, and it got 72%.  Started another remediation, with a completely different baseline and it never got past 0% and the other one stopped at 72% and has yet to complete.

This only seems to be an issue with our Cisco UCS blades.  We have HP blades also and you can remediate them 2 at a time with no issues.

Just curious if anyone else has seen this behavior or is there something within vCenter Update manager that I need to check.

Thank You

Brian Dougherty

Hello

I dont have the settings tab

Also I cannot create baseline for the patch

I tried to restart the service on the appliance but still no choice for settings

I'm using vCenter 6.7 appliance and download updates straight from the internet. I've noticed that although downloads succeed the latest patch I can see is from 19 December 2019. It's now 03 Feb 2020 and I'm sure there have been critial or non critical patches released. I have 3 X different vCenters and they are all the same.

After taking the suggestion to upgrade to 6.7 from 6.5, I know find that 6.7 Update Manager appears as incompatible and plug-in will not load or work.  Moving to Appliance is not an option at the moment.  Any suggestions.

Currently we are running latest Vmware Update Manager 6.5 patches. When we install Vcenter we didn't install update manager. So now when I try to install update manager I am getting this error during the ODBC DSN configuration.

"The DSN is pointing to an unsupported ODBC driver. Please re-configure you DSN to use one of the supported drivers."

But I checked the DSN and it is using the correct name and version.

Basically update manager can't find the existing vcenter database.

I upgraded a few of my ESXi's from v6.5 to v6.7u3.  I discovered when I select the VMware Tools I get a message that reads, "an unexpected error has occurred" followed by a green check mark stating "undefined of undefined VMs are up to date."  See attached.

Has anyone seen this before and, if so, what did you do to resolve the issue?

Thanks!

David

Hi,

I wanted to install the update manager download service on my laptop which is a Debian 10. So I unpacked the tarball from the ISO installer (/mnt/cdrom/umds/VMware-UMDS-6.7.0-15124069.tar.gz) and ran the vmware-install.pl script. I installed to /usr/local/ and put the patch repository in my home directory. I ran the installer as root. Now I get "Segmentation Fault" every time I try to run vmware-umds. Is Debian 10 not supported. I checked this page. It says you need a Linux host and Administrative privileges but it does not mention anything about compatibility of the different distributions.  https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.update_manager.doc/GUID-292B9BE6-7B48-4EE2-B6A1-48468BB9648B.html

Does someone know it does or does not run on Debian? If not, will CentOS (7/8) probably work?