Beats Central Management in ECE error creating a new enrollment token unexpected number of tokens got 0 only one expected

Elastic Stack Beats
1

Were trying to use Beats Central Management in ECE 2.3 by using a username and password so that we can script this when we deploy to numerous servers. The metricbeat is not set as a service on one of our testing computers. Error message: "Error creating a new enrollment token: Unexpected number of tokens, got 0, only one expected"

PS C:\metricbeat-7.0.0-production-windows-x86_64> .\metricbeat.exe enroll https://xyz.gov:9243 --e
2019-10-08T14:34:01.336-0400    INFO    instance/beat.go:571    Home path: [C:\metricbeat-7.0.0-production-windows-x86_64] Config path: [C:\metricbeat-7.0.0-production-windows-x86_64] Data path: [C:\metricbeat-7.0.0-production-windows-x86_64\data] Logs path: [C:\metricbeat-7.0.0-production-windows-x86_64\logs]
2019-10-08T14:34:01.337-0400    INFO    instance/beat.go:579    Beat ID: xxxxx
This will replace your current settings. Do you want to continue? [Y/n]:2019-10-08T14:34:04.364-0400    INFO    add_cloud_metadata/add_cloud_metadata.go:340    add_cloud_metadata: hosting provider type not detected.
y
Enter password:
2019-10-08T14:35:52.955-0400    INFO    kibana/client.go:118    Kibana url: https://xyz.gov:9243
Error creating a new enrollment token: Unexpected number of tokens, got 0, only one expected

Seems like the beat is connecting to Kibana its just not recieving anything back. We are behind a VIP and are using Logstash to direct our beats traffic once the beat is enrolled if that info is of any help.

2

I'm going to move this to the beats forum to start with, since if it is related to ECE doing something differently to standalone deployments, then it's something we don't know about, and the beats team are more likely to know which logs to look at etc to figure that out

If there are any questions that come up about ECE's role in all this, feel free to ping me in

3

Sounds good. Wasn't sure exactly where to send it.

4

ECE 2.3
Elastic/Kibana 7.3
Metricbeat 7.0.0

We were able to enroll a beat after going through UX in Kibana. So thats a positive, however we have 200+ beats that we would like to enroll after they are deployed and the one we did enroll is reporting as offline even though data is reaching the cluster. When hovering over the Offline part it does say that the "Beat successfully applied last config". The documents appear to have the system and windows (perfmon) data that we are asking for. Any insight into the Offline and the "Error creating a new enrollment token: Unexpected number of tokens, got 0, only one expected" issue would be appreciated.

5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.