ESX client not working

Usage and Config Platform
1

(imported topic written by FITZPAW91)

Hello,

I am trying to get my ESX 3.0.2 Server patched with the new December patches, and they are showing up as irrelevant. I ran “ESX - Gather ESX Patch Information - ESX Server 3” to populate my list of existing patches which uses the following action script

// Create a folder if it does not exists

if {NOT exists folder “__EsxPatchInfo” of (parent folder of (client folder of current site))}

wait mkdir “{pathname of (parent folder of (client folder of current site)) & “/__EsxPatchInfo”}”

endif

delete execute.sh

delete __appendfile

appendfile {"esxupdate query | awk '/3.0.|ESX-/ %7Bsub(/^

\t

+/, %22%22);gsub(/

\t

+/, %22 %22); print %7D’ > " & pathname of (parent folder of (client folder of current site)) & “/__EsxPatchInfo/EsxPatch.Info”}

move __appendfile execute.sh

wait sh execute.sh

It didn’t work. Then I ran the QNA on the server against the relevance of one of the fixlets, and the last line

exists folder “__EsxPatchInfo” whose (exists file “EsxPatch.Info” whose (NOT exists lines whose (it starts with “ESX-1006985”) of it) of it) of parent folder of client folder of current site

Gave me this error Singular Expression refers to non-existant object.

I even tried running

exists folder “__EsxPatchInfo” whose (exists file “EsxPatch.Info” whose (NOT exists lines whose (it starts with “ESX-1006985”) of it) of it) of parent folder of client folder of current site))

and I get an error - Singular Expression refers to non-existant object. But the file does exist.

The file exists in /var/opt/BESClient/__BESData/__EsxPatchInfo/ExsPatch.Info

Help Please

2

(imported comment written by juancb91)

Fitzpaw,

The relevance used by those Fixlets relies on client context, and as such it cannot be evaluated via QNA. To get the fixlet relevance to evaluate you will have to modify it by replacing “parent folder of client folder of current site” with “folder /var/opt/BESClient/__BESData”.

e.g.

exists folder 
"__EsxPatchInfo" whose (exists file 
"EsxPatch.Info" whose (NOT exists lines whose (it starts with 
"ESX-1006985") of it) of it) of folder 
"/var/opt/BESClient/__BESData"

I don’t think we can determine the cause behind those Fixlets not showing up as Relevant without additional information. Could you try running the modified relevance statement and posting the result of the statement’s evaluation, the contents of your EsxPatch.Info file, and a tar ball of the client’s log directory (/var/opt/BESClient/__BESData/__Global/Logs/)?