Quantcast
Channel: VMware Communities : Discussion List - Update Manager
Viewing all articles
Browse latest Browse all 2118

Update Manager 5.1 Host Cannot Download Files

$
0
0

vsphere 5.1, server 2008 R2, esxi 5.0

This discussion appears to have been done to death but I am receiving the

"

Host cannot download files
from VMware vSphere
Update Manager patch store. 
Check the network
connectivity and firewall
setup, and check

"

esxupdate log is showing:

"

2012-09-25T19:43:44Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2012-09-25T19:43:44Z esxupdate: downloader: DEBUG: Downloading http://192.168.4.100:9084/vci/hostupdates/hostupdate/DELL/metadata_1348601563.zip to /tmp/tmp4vSnZw...

2012-09-25T19:43:44Z esxupdate: esxupdate: ERROR: An esxupdate error exception was caught:

2012-09-25T19:43:44Z esxupdate: esxupdate: ERROR: Traceback (most recent call last):

2012-09-25T19:43:44Z esxupdate: esxupdate: ERROR:   File "/usr/sbin/esxupdate", line 216, in main

2012-09-25T19:43:44Z esxupdate: esxupdate: ERROR:     cmd.Run()

2012-09-25T19:43:44Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-768111/bora/build/esx/release/python-2.6-lib-zip-stage/768111/visor/pylib/python2.6/site-packages/vmware/esx5update/Cmdline.py", line 106, in Run

2012-09-25T19:43:44Z esxupdate: esxupdate: ERROR:   File "/build/mts/release/bora-768111/bora/build/esx/release/python-2.6-lib-zip-stage/768111/visor/pylib/python2.6/site-packages/vmware/esximage/Transaction.py", line 71, in DownloadMetadatas

2012-09-25T19:43:44Z esxupdate: esxupdate: ERROR: MetadataDownloadError: ('http://192.168.4.100:9084/vci/hostupdates/hostupdate/DELL/metadata_1348601563.zip', None, "('http://192.168.4.100:9084/vci/hostupdates/hostupdate/DELL/metadata_1348601563.zip', '/tmp/tmp4vSnZw', '[Errno 14] HTTP Error 404: Not Found')")

"
I have checked all firewall ports and 9084,8084,80,443 are all open on both the vsphere and esxi servers. vci-integrity,xml shows the correct address (as you can see from the esxupdate.log file).  I've swapped between dns and ip address so the issue is not the fqdn.  Any further suggestions. EVERY update of vsphere appears to cause the problem so I have completely rebuilt the server from scratch and I am at my whits end.

Viewing all articles
Browse latest Browse all 2118

Trending Articles