Two big questions, We setup fleetdm awhile ago and...
# fleet
p
Two big questions, We setup fleetdm awhile ago and just recently updated the core service to begin logging. Now that it is logging and we are looking into the logs I noticed we are getting a ton of these errors
Copy code
"enroll failed: no matching secret found: EnrollSecret was not found in the datastore"
"authentication error: missing node key"
"Requires Fleet Premium license"
I was wondering what we need to fix these errors and debug them?
g
Greetings @pickmansec 1. This comes up if have you have a host with an old enroll secret 2. These will come up from time to time when the token used to authenticate Fleet Desktop expires (how often are these showing in your logs?) 3. Will need full error for this one to try and track down what is causing this
p
1. This comes up if have you have a host with an old enroll secret
how do i fix this using fleet?
2. These will come up from time to time when the token used to authenticate Fleet Desktop expires (how often are these showing in your logs?)
2000hosts and about 540 per min
3. Will need full error for this one to try and track down what is causing this
Where do I get these logs?
g
Hey @pickmansec, Would you also enable debug logging (might already have this on) https://fleetdm.com/docs/configuration/fleet-server-configuration#logging-debug Then could you provide the full error line seeing for each of those?
t
I'm also experiencing tons of Requires Fleet Premium license. With debug log enabled, I've started to collect the logs and identify the IPs. Not sure why this happens, though. Why should an agent try to contact an API endpoint which is "Fleet Premium"?
Within twenty minutes, I see 545 unique IPs logging "Requires Fleet Premium license", ~ 3000 log entries in total. The fleet instance has ~ 900 hosts enrolled. It was set up a few days ago from scratch.