I am trying to run a query using the “Evaluate using Query Channel using QnA”, and it hangs with a message: “Waiting for evaluation to finish”.
Is the endpoint able to receive UDP notifications from its parent relay?
I have seen that behavior when the endpoints are not able to be notified.
You can see in the client log whether the client received and processed the query. Also worth noting, as @fermt says, that the clients need to be able to receive UDP notifications. If you’re trying to query a device behind a NAT, and you’re on a modern enough version, make sure you enable persistent connections.
I have three test machines on the same subnet. One of them completes a simple query, “name of operating system” and the other two stay at “Waiting for evaluation to finish”.
The debug log looks the same on all three systems. They all show that the query completed successfully.
I added debug logging for the fixletdebugger.
Registry settings
To enable debug logging on the Fixlet Debugger, make the registry settings as follows:
HKCU\Software\Bigfix\FixletDebugger
DebugOut - REG_SZ - Specify the full path to the log file.
EnableLogging - DWORD - Set to 0 for disabling or 1 for enabling.
EnabledLogs - Reg_SZ - Set to “all”.
The query that never completes repeats the following lines indefinitely.
Thu, 25 Jul 2019 14:54:31 -0700 – SendAPIRequest: GET with clientqueryresults/88
Thu, 25 Jul 2019 14:54:31 -0700 – QCResultPoller: No result received for 88. Readding to list. Size is now: 1
The query that completes successfully looks like this.
Thu, 25 Jul 2019 14:55:10 -0700 – SendAPIRequest: GET with clientqueryresults/89
Thu, 25 Jul 2019 14:55:10 -0700 – QCResultPoller: No result received for 89. Readding to list. Size is now: 1
Thu, 25 Jul 2019 14:55:10 -0700 – QCResultPoller: Start of result request loop. Sleeping for: 4000ms.
Thu, 25 Jul 2019 14:55:14 -0700 – SendAPIRequest: GET with clientqueryresults/89
Thu, 25 Jul 2019 14:55:14 -0700 – Waiting Dialog finish request received.
Thu, 25 Jul 2019 14:55:14 -0700 – Clearing data for next evaluation
I found that restarting the BES Root Server Service and the FillDB Service temporarily resolves the issue. I don’t know how long it takes before remote QnA stops working.