Metadata for Patch Missing

[markvor]

Hi Experts,

It is not possible to Scan for Updates on my esx 3.5 hosts.

I received the many times discussed error Metadata for Patch Missing.

I tested all the solutions discussed in the communities with no luck.

i got the following error in the esxupdate.log file

DEBUG: db: dbfile = , 1 keys

--08Feb13-0030] DEBUG: Depot: Download Rules: {'blacklist': '.rpm', '/headers', 'exclusives': [--}

ERROR: root: IOError: <urlopen error (111, 'Connection refused')>

ERROR: hostagent: BundleID:Unknown

ERROR: hostagent: File:[http://192.168.10.2:80/vci/hostupdates/hostupdate/esx/esx-3.5.0/contents.xml.sig|http://192.168.10.2/vci/hostupdates/hostupdate/esx/esx-3.5.0/contents.xml.sig]

ERROR: hostagent: Extra:()

Ho can i get that thin working that he connection is not refused anymore.

My VC Server works on Port 80 an there is no IIS installed. Only the Tomcat Service for VC Server.

I hope anybody of you could give me the final hint to solve this riddle.

Thanks for your help.

Markus Vorderer

[vlchild]

Have you tried to telnet to port 80 on your VC server?

Sounds silly, but what about the Windows firewall?

[markvor]

Hi,

the firewall is deactivated on the vc server. an also i am abe to telnet the vc server port over port 80.

any other hints?

markus

[vlchild]

Since you said you have tried everything else everyone posted, I am only throwing out silly oversite type stuff. hopefully something hits for you.

Have you checked the NTFS permissions on the datastore?

Lee

[markvor]

Hi Lee,

what did you mean to check the ntfs permissions on the datastore. where do i have to check it, on the host or the vc server and what is command to check this.

thanks

markus

[vlchild]

From this path:

File:http://192.168.10.2:80/vci/hostupdates/hostupdate/esx/esx-3.5.0/contents.xml.sig

I would guess when you set up updater that you choose a different path than the default. But I am not real sure as I haven't dug that deeply into mine yet. There were two paths when you set up updatemanager. The path on the top was where the program resides, the path on the bottom was where the update data went. It looks like oyu changed that from the defaults (and you should, no one wants that much data crammed in the default location)

So, where ever you set that second path. If you cannot remember search on one of the strings above, like 'hostupdates' or 'esx-3.5.0' and it will pop up. On that folder right click and look at the NTFS permissions. Check the services and see how you launch update manager and VC. By default they launch with 'Local System'. Make sure the directory that houses that metadata actually has the proper permissions for VC and Updatemanager to change it.