Also, don't know why but 4.2 randomly crashes with warnings about crypto. Setup hasn't changed from 4.1
08/15/2021, 1:19 AM
Is there anything else above what you have in that screenshot? Is this running in a container?
08/15/2021, 1:36 AM
@zwass 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?
08/15/2021, 1:51 AM
They are independent
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.
08/15/2021, 1:55 AM
@zwass Ubuntu server 20.04.2 LTS (fully updated), openssl 1.1.1k,
2GB RAM, 1 core, go version go1.16.6 linux/amd64Small server only managing a small number of devices
08/15/2021, 1:57 AM
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.
08/15/2021, 2:00 AM
I think when it is trying to do the vulnerabilitydb stuff is when it is failing
That's the complete stack trace
08/15/2021, 2:41 AM
Can you please copy/paste that entire stacktrace into a GitHub Issue?