https://github.com/osquery/osquery logo
#fleet
Title
# fleet
m

mikermcneil

12/23/2022, 3:45 PM
The only two windows hosts I have enrolled are not responding to custom queries (even the basic SELECT * FROM osquery_info) - Seems to be stuck at : Fleet is talking to your hosts, (0% responded). However, I am able to fetch fresh vitals within a couple of seconds for both hosts. Any ideas on what could be wrong here? Posted in #general
@Kathy Satterlee Seen this one before?
Whoops, and cc @Amith so you see replies
l

Lucas Rodriguez

12/23/2022, 3:47 PM
Have you checked Fleet successfully connects to Redis? (Live/custom queries need/use Redis.) You can check this via the
/healthz
endpoint:
curl https://<your_fleet_address>/healthz
z

zwass

12/23/2022, 4:03 PM
(there should also be an error message on the live query page if the redis connection fails)
l

Lucas Rodriguez

12/23/2022, 4:06 PM
Second thing to check would be websocket connections (live queries use websockets)
z

zwass

12/23/2022, 8:28 PM
I think websockets are a good guess. Can you open your browser devtools and see if there is any error?
a

Amith

12/26/2022, 11:37 AM
@Lucas Rodriguez Health check endpoint gave a 200, it seems like websocket errors on Chrome was the culprit and issue seems to be intermittent now. I'm able to run queries smoothly on Firefox, so I will be using this from now on. Thanks for the help!
m

mikermcneil

01/28/2023, 1:04 AM
@Amith Just curious: were you deployed over wss://? If so, then I'm wondering if it could have been coincidence (maybe the Fleet server was down) If you see this issue again, in Chrome or otherwise, could you create a bug? 🙇
@Amith How'd it go?