2 people found this helpful
Chek the log at: /var/log/vmware/applmgmt/applmgmt.log
Look for wget
I can see this kind of lines
DEBUG:vmware.appliance.update.update_functions:Running /usr/bin/wget --no-check-certificate --connect-timeout 10 -P /storage/core/software-update/tmp/latest https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/18.104.22.168000.latest/manifest/manifest-latest.xml -e use_proxy=yes -e http_proxy=https://http://<foobar>:8080
Which is wrong. So......
I have found a solution:
1: At VCSA level either VAMI or CLI (/etc/sysconfig/proxy) you should turn off proxy config.
2: Configure the following file: /etc/wgetrc
http_proxy = http://proxy.yoyodyne.com:18023/
https_proxy = http://proxy.yoyodyne.com:18023/
Then It should work like a charm.
1 person found this helpful
Editing the /etc/wgetrc solved my issue with getting the VCSA patch downloaded (thanks). Any suggestions for getting VUM working with a proxy? Nothing I've tried has worked properly for VUM to connect.
I had a ticket opened with VMware to get this resolved. Rather simple really. Not sure why it's not in a document somewhere on the interwebs.
In the settings page for Update Manager just put the proxy information in. I didn't put in any http://proxy.address, I just put in proxy.address and then specified the port number. If you have credentials then use them. However do not click on Test Connection. That button doesn't seem to work right. It might take a moment for the updated settings to show in vCenter. You should then be able to click on Download Now in the upper right and it should get the latest patch definitions, which as of today was May 13th. If you run into issues you can either restart the update manager service from the GUI or if you like command line stuff you can putty into the appliance and use:
service-control --stop vmware-updatemgr
service-control --start vmware-updatemgr
Hope this helps.
The workaround (editing etc/wgetrc) does work with the latest 6.7 u2a patch. None of the 6.x seemed to have a working proxy configuration out of the box, this is frustrating.
I yearn the day when VMware will finally fix this in the various appliances (with VRLM having the most ridiculous workaround), it seems like the company is not aware at all that clients use proxies in their environments.
Agreed. We have a history of challenges surrounding the proxy configuration of our vCenters.