. we are able to fix it by refreshing
(No node key returned from TLS enroll plugin)
, but i was wondering if there is a way to just reset the node key without "factory-resetting" osqueryd on the host?
. in our case osquery stopped running queries entirely. on existing hosts, we just pretty much purged that dir so osquery starts fresh. we fixed it at the source by adding a step in our provisioning scripts to remove the directory (apparently generated when the OS images are being built). though i still see that error pop up occasionally but the affected hosts are otherwise fine. we just ignore it for now /shrug
so osquery.db doesn't exist. I've also attempted
but I'm still seeing the error message, although as you see also, it seems to have no effect.