Update Manager - Hosts fails to open contents.xml.sig (Connection Refused)

[Conflict2011101]

Hello Everyone:

     This subject looks to be touched on quite a bit, but I am still unable to resolve an issue I am having with one of my hosts.

     When I attempt to remediate on one of my hosts it fails with "VMWare Update Manager had a failure"

     I have a 4 host environment, at least one of the hosts is able to remediate. The host I am working cannot. I am using ESX 3.5.

     I checked the esxupdate.log and see the following problem:

[13Jun11-1048]   DEBUG:   summary: /usr/sbin/esxupdate --HA --flushcache -d http://XXX.XXX.XXX.XXX:8080/vci/hostupdates/hostupdate/esx/esx-3.5.0 scan

[13Jun11-1048]   DEBUG:      root: Enabling hostagent interface

[13Jun11-1048]   DEBUG:        db: dbfile = [/etc/vmware/patchdb/patch.db], 5 keys

[13Jun11-1048]   DEBUG:     Depot: Download Rules: {'blacklist': ['*.rpm'], 'exclusives': []}

[13Jun11-1048]   ERROR:      root: [Errno 4] IOError: <urlopen error (111, 'Connection refused')>: http://XXX.XXX.XXX.XXX:8080/vci/hostupdates/hostupdate/esx/esx-3.5.0/contents.xml.sig

     The IP address has been replaced with X's obviously.

     I've checked the following article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100491...

     I am able to ping the IP, a temp directory is in place, and I opened the firewall for that port. I even went as far as opening the firewall completely for incoming and outgoing.

     I am able to hit http://XXX.XXX.XXX.XXX:8080/vci/hostupdates/hostupdate/esx/esx-3.5.0/contents.xml.sig from other machines so I know it's visible.

     I am not using a proxy.

     I cannot determine why the connection is being refused. I've checked the vci-integrity.xml file and it looks ok.

     Is this possibly a PGP problem or somesort of identity issue? :smileyconfused:

     If there are additional logs I should check or anyone has any suggestions that would be greatly appreciated.

[admin]

Please refer kb 2000356

[raog]

That KB doesn't seem to exist.

Regards

Girish

[Conflict2011101]

Thank you for the reply. I don't see any KB article with that number. Can you double check and possibly post a direct link?

Thank you for your time.

[admin]

This issue may occur if the Jetty configuration is incorrect in the in the vci-integrity.xml file. To resolve this issue, use this default configuration for jetty in vci-integrity.xml file:     -Djavax.net.ssl.trustStore=ssl/vmware-vum.keystore -jar jetty/start.jar jetty/etc/jetty.xml jetty/etc/jetty-logging.xml jetty-vum.xml jetty-vum-ssl.xml       jre\bin\java.exe   Restart the VMware Update Manager for changes to take affect.