Troubleshooting "not reported" in simple Analysis

Content Authoring
1

Apologies for the beginners question (again :slight_smile: ).

How I can troubleshoot “not reported” items in the Analysis?

I have a simple analysis - looking for 2 items, both items work fine from qna but show “not reported” on the Results tab of the Analysis. I can see “Successful Synchronization” with my site (site141) in the log.

My only thought - time spend on executing the request in qna looks high for a simple query. Is it indeed high?

Thank you,
Aleksandr

Simple analysis is asking for:
A) number of line containing “CUSTOM” of file "/var/log/messages"
B) version of package “tda-check-bigfix-agent” of rpm as string

Both seem to be simple and work in qna as expetced:

[root@h0002039 ~]# /opt/BESClient/bin/qna
Default masthead location, using /etc/opt/BESClient/actionsite.afxm
Q: number of line containing “CUSTOM” of file "/var/log/messages"
A: 0
T: 5101062

Q: version of package “tda-check-bigfix-agent” of rpm as string
A: 0.4-1
T: 11136151

Q: ^C
[root@h0002039 ~]#
[root@h0002039 ~]# grep -B2 -A1 site141 /var/opt/BESClient/__BESData/__Global/Logs/20190416.log | tail -14

Successful Synchronization with site ‘CustomSite_UNIX-2fLinux_Production_Support’ (version 2169726,43) - 'http://bigfix.associatesys.local:52311/cgi-bin/bfgather.exe/CustomSite_UNIX-2fLinux_Production_Support’
At 07:47:20 -0500 -
Successful Synchronization with site ‘opsite141’ (version 2174238,43) - 'http://bigfix.associatesys.local:52311/cgi-bin/bfgather.exe/opsite141’
At 07:51:20 -0500 -

Successful Synchronization with site ‘opsite13’ (version 1738238,43) - 'http://bigfix.associatesys.local:52311/cgi-bin/bfgather.exe/opsite13’
Successful Synchronization with site ‘opsite138’ (version 1738238,43) - 'http://bigfix.associatesys.local:52311/cgi-bin/bfgather.exe/opsite138’
At 08:12:50 -0500 - opsite141 (http://bigfix.associatesys.local:52311/cgi-bin/bfgather.exe/opsite141)
Downloaded ‘http://PRDTXWPRISAS01.prod-am.ameritrade.com:52311/bfmirror/bfsites/manydirlists_101/__diffsite_4a27b918b953904bf4d7ba2d558a7e22c8fdd6a1_to_e72444f9e741178f10190c4fe5c88766407f3bd7’ as '__TempUpdateFilename’
Gather::SyncSiteByFile merging files - count: 2
At 08:12:50 -0500 -
Successful Synchronization with site ‘opsite141’ (version 2174886,43) - 'http://bigfix.associatesys.local:52311/cgi-bin/bfgather.exe/opsite141’
At 08:12:51 -0500 -
[root@h0002039 ~]#

2

2 possible cause that spring to mind are

  1. The computers aren’t relevant for the analysis. Does the analysis have any applicability relevance that might be filtering the computer out?
  2. The computers may not yet have evaluated as relevant for the analysis so will default to until they have evaluated as relevant and have then evaluated the properties.
3

SLB, thank you! This was very fast response!

RE: 1 computers aren’t relevant
The relevance criteria is “exists package “tda-check-bigfix-agent” of rpm” (the only relevance criteria!), this is why analysis is asking for the version of that RPM.
RE: 2 computers may not have evaluated as relevant
Analysis shows “not reported” for several days at least. Properties are set to evaluate “Every report”.

[root@h0002039 ~]# /opt/BESClient/bin/qna
Default masthead location, using /etc/opt/BESClient/actionsite.afxm
Q: exists package “tda-check-bigfix-agent” of rpm
A: True
T: 9639281

Q: version of package “tda-check-bigfix-agent” of rpm as string
A: 0.4-1
T: 183

Q: ^C
[root@h0002039 ~]#