Skip to content

Update troubleshooting.asciidoc #1573

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Dec 19, 2024
Merged

Update troubleshooting.asciidoc #1573

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2dc92c3
Update troubleshooting.asciidoc
BBQigniter Dec 19, 2024
ee0a3e4
Update docs/en/ingest-management/troubleshooting/troubleshooting.asci…
kilfoyle Dec 19, 2024
cb7a73a
Update docs/en/ingest-management/troubleshooting/troubleshooting.asci…
kilfoyle Dec 19, 2024
292ef6f
Update docs/en/ingest-management/troubleshooting/troubleshooting.asci…
kilfoyle Dec 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,7 @@ Find troubleshooting information for {fleet}, {fleet-server}, and {agent} in the
* <<agent-oom-k8s>>
* <<agent-sudo-error>>
* <<agent-kubernetes-kustomize>>
* <<agent-kubernetes-invalid-api-key>>


[discrete]
Expand Down Expand Up @@ -963,3 +964,15 @@ Extra resources for {agent} on Kubernetes troubleshooting and information:
* https://github.com/elastic/elastic-agent/tree/main/deploy/kubernetes/elastic-agent-kustomize/default[{agent} Kustomize Templates] documentation and resources.

* Other examples and manifests to deploy https://github.com/elastic/elastic-agent/tree/main/deploy/kubernetes[{agent} on Kubernetes].

[discrete]
[[agent-kubernetes-invalid-api-key]]
== Troubleshoot {agent} on Kubernetes seeing `invalid api key to authenticate with fleet` in logs

If an agent was unenrolled from a Kubernetes cluster data might be left in `/var/lib/elastic-agent-managed/kube-system/state` on the node(s). Reenrolling an agent later on the same nodes might then show error `invalid api key to authenticate with fleet` error messages.

Make sure to delete this state-folder before rolling out a new agent.

Extra information:

* https://github.com/elastic/elastic-agent/issues/3586
Loading