with the tls config plugin, are there expected sit...
# general
t
with the tls config plugin, are there expected situations a host will re-enroll other than receiving an invalid node_key response from the server?
s
Presumably missing local databases.
t
huh. so, i went off to take a peek at this; in at least one case the db appears to be there, but it doesn't look like osqueryd has touched it in... awhile
s
Are you sure it’s using that database?
t
lsof appears to show it having multiple fds open in the expected folder, at least
s
Okay then.
I don’t know this corner of the code. I’d believe there are reasons
t
i've always assumed that the IDENTITY file in osquery.db is related to the node_key; do you know if that's correct?
d
I don’t think this is true, no. I think the identity file is related to rocks specifically. It helps the system know which SST files to use. Not sure how this plays a role with the manifest
👍 1
t
the short version is that it looks like doing: service osqueryd stop rm -rf $osquery_db is not a great idea; in some cases the worker will still be alive and still have fds open even though the daemon is gone