-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] setup failed: An internal server error occurred #95896
Comments
Pinging @elastic/fleet (Team:Fleet) |
Another stack trace:
|
My suspicion is that the |
We tried here: #90148 |
Maybe we can improve the healthcheck by checking the status of
We can check if that shard has been started, WDYT? |
@ycombinator Any idea? |
Looking at the errors in the various logs, this looks like an internal Kibana error to me. When the Fleet Server (or is it Agent? or either?) is calling A similar thing seems to be happening when In either case, I think it would be great if Kibana could expose a Fleet health check API that will allow Fleet Server or Agent to ask the question, "Is Fleet ready or not?" before calling Thoughts? |
I think I partially mimicked it here: elastic/elastic-package#311 . Could you please take a look? |
Blocker: elastic/elastic-package#278
I spotted this while integrating with Fleet Server. Fun fact - all our integration tests passed! I mean, Kibana/Fleet/Agent behave correctly in terms of HTTP responses, but logs are full or errors. I suppose that someone would like to check it.
Fleet Server:
Kibana:
(source: https://beats-ci.elastic.co/job/Ingest-manager/job/elastic-package/job/PR-279/33/artifact/build/elastic-stack-dump/check/logs/kibana.log)
Elasticsearch:
(source: https://beats-ci.elastic.co/job/Ingest-manager/job/elastic-package/job/PR-279/33/artifact/build/elastic-stack-dump/check/logs/elasticsearch.log) - not sure if this one is relevant.
The text was updated successfully, but these errors were encountered: