Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

Screen Shot 2021-08-15 at 11.12.55 am.png

Also, don't know why but 4.2 randomly crashes with warnings about crypto. Setup hasn't changed from 4.1

Is there anything else above what you have in that screenshot? Is this running in a container?

<@U0JFM04MS> This is not in a container, this is the fleet binary ran as a systemd service (which works without any error until now). I don't see anything else but also I'm not sure where fleet writes logs so I can check?

Also I did migrate the DB  with fleet prepare db --config=blah so that is ok as well

The only thing is I didn't bother with the fleetctl binary this time, I just removed it as I don't use it. Would that cause an issue? I figure given that they are in seperate zip files they are independent of each other right?

What platform is this running on? We enabled CGO which changes some things about the build -- this could be related. Anything that could help us reproduce this would help to get a fix.

<@U0JFM04MS> Ubuntu server 20.04.2 LTS (fully updated), openssl 1.1.1k,
2GB RAM, 1 core, go version go1.16.6 linux/amd64

Small server only managing a small number of devices

There's nothing else in the systemd logs there?

Hoping we can find where in the Fleet code that could be coming from -- the stack trace I can see in that screenshot only includes stdlib.

Screen Shot 2021-08-15 at 12.00.05 pm.png

Screen Shot 2021-08-15 at 12.01.03 pm.png

Screen Shot 2021-08-15 at 12.01.33 pm.png

Screen Shot 2021-08-15 at 12.01.59 pm.png

Screen Shot 2021-08-15 at 12.02.21 pm.png

I think when it is trying to do the vulnerabilitydb stuff is when it is failing

Can you please copy/paste that entire stacktrace into a GitHub Issue?