Update Manager Could not scan 1 of my 6 Esxi task failed at 55 %

[cosmos77]

Hello,

My environnement contain 6 Esxi 5.1.0 build 799733.

I can't update 1 of my 6 Esxi

I have no problem with 5 of my Esxi but the last give me this error

"Scan entity x.x.x.x Host cannot download files from VMware vSphere Update Manager patch store.  Check the network connectivity and firewall setup, and check esxupdate logs for details. "

I verify this one (the IP address is set)

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200739...

VMware KB: ESX/ESXi hosts fail to scan in vCenter Update Manager 4.1.x and 5.x

Here is one prtscr of my esxupdate.logs

Have anybody an idea to help me to fix this problem

Thanks

[dhanarajramesh]

can you check HTTP (SSL) port 9087 and  TCP port 9084 opened between this issue host to vcenter or not?

[admin]

ESXi firewall sounds like a good start, basically you can also simply test to download the file you see in the logs using wget on the host.

[cosmos77]

hello,

Ports are open on all hosts, I checked. How to list open ports on the appliance vCenter 5.1, I did not find the corresponding command as escli network firewall
for wget, actually it would be a solution, although I prefer to use update manager for all the updates

[admin]

>for wget, actually it would be a solution, although I prefer to use update manager for all the updates

Even if you download the file with wget Update Manager will still fail, as it still will download the file again, wget is just a test to see if VUM actually has a chance of pushing this file or not.

So try on the host that fails the scan and try on one of the hosts that succeed to rule out any port/firewall/connectivity issues towards that single host.

[cosmos77]

Hello Frank,

I tested on the host where scan works, I tested on the host where the scan does not work.

Wget does not work on either of the two hosts, the return is wget: bad address 'i.testdebit.info'

I tested with the command wget-o / dev / null http:// 1.testdebit.info/fichiers/100Mo.dat

[cosmos77]

I thought I had found the source of the problem
My esxupdate.log I saw this:

Options: {'nosigcheck': None, 'retry': 5, 'loglevel': None, 'cleancache': None, 'viburls': None, 'meta': ['http://172.16.1.108:9084/vum/repository/hostupdate/csco/csco-VEM-5.1.0-metadata.zip', 'http://172.16.1.108:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.1.0-metadata.zip'], 'proxyurl': None, 'timeout': 30.0, 'cachesize': None, 'hamode': True, 'maintenancemode': None}
2014-03-10T13:11:58Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg
2014-03-10T13:11:58Z esxupdate: BootBankInstaller.pyc: INFO: Unrecognized value "title=Loading VMware ESXi" in boot.cfg
2014-03-10T13:11:59Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.
2014-03-10T13:11:59Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.
2014-03-10T13:11:59Z esxupdate: downloader: DEBUG: Downloading http://172.16.1.108:9084/vum/repository/hostupdate/csco/csco-VEM-5.1.0-metadata.zip to /tmp/tmp6mJvD9...
2014-03-10T13:14:29Z esxupdate: esxupdate: ERROR: An esxupdate error exception was caught:
2014-03-10T13:14:29Z esxupdate: esxupdate: ERROR: Traceback (most recent call last):
2014-03-10T13:14:29Z esxupdate: esxupdate: ERROR:   File "/usr/sbin/esxupdate", line 216, in main
2014-03-10T13:14:29Z esxupdate: esxupdate: ERROR:     cmd.Run()
2014-03-10T13:14:29Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-799733/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esx5update/Cmdline.py", line 106, in Run
2014-03-10T13:14:29Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-799733/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/Transaction.py", line 71, in DownloadMetadatas
2014-03-10T13:14:29Z esxupdate: esxupdate: ERROR: MetadataDownloadError: ('http://172.16.1.108:9084/vum/repository/hostupdate/csco/csco-VEM-5.1.0-metadata.zip', None, "('http://172.16.1.108:9084/vum/repository/hostupdate/csco/csco-VEM-5.1.0-metadata.zip', '/tmp/tmp6mJvD9', '[Errno 12] Timeout: <urlopen error timed out>')")
2014-03-10T13:14:29Z esxupdate: esxupdate: DEBUG: <<<

as explained here

VMware KB: Remediating an ESXi 5.x host fails with the error: The host returns esxupdate error code:...

so I replaced the file / locker/packages/5.1.0 / by that of a host or it worked
but the problem persists ...

[vSomething]

I see this occasionally and an easy fix is to change your Update Manager patch store from the host name to the IP name.

[kumarde]

Greetings,

I see this was posted some time back I hope this might have  been already resolved but just in case  if we still see the issue please try the following steps:

This issue occurs when the /bootbank/state.XXXXXXXX directory is not empty.

1) Checked the Update Manager logs after a fail scan. Search for entries similar to "Directory not empty: '/altbootbank/state.xxxxxxx".

2) SSH to the host and navigate to the path ie altbootbank/state.xxxxxxx

ie cd "altbootbank/state.xxxxxxx"

3) Type "ls" to list the contents, there should be file called local.tgz

4) Move this file to different directory. The idea is to free up this state.xxxxxxx directory.

5) Once we are able to free up the space ran the scan and remmediate again.

You could also refer the following KB article for reference : <http://kb.vmware.com/kb/2007163>

hope this helps!

[MrLionelB]

Agree, default GW was my problem.

[cosmos77]

I finally discovered that the problem was the firewall blocking the update