Skip to content
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

Add troubleshooting for Agent Out of Memory on K8s #842

Merged
merged 2 commits into from
Jan 24, 2024
Merged

Add troubleshooting for Agent Out of Memory on K8s #842

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
41febf6
Add troubleshooting for Agent Out of Memory on K8s
kilfoyle Jan 22, 2024
f56aa50
Fixup
kilfoyle Jan 22, 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
19 changes: 18 additions & 1 deletion docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -713,4 +713,21 @@ The final command will install {agent}. For example:
sudo ./elastic-agent install --url=https://fleet-server:8220 --enrollment-token=bXktc3VwZXItc2VjcmV0LWVucm9sbWVudC10b2tlbg==
----

After running these steps your {agents} should be able to connect with {fleet} again.
After running these steps your {agents} should be able to connect with {fleet} again.

[discrete]
[[agent-oom-k8s]]
== {agent} Out of Memory errors on Kubernetes

In a Kubernetes environment, {agent} may be terminated with reason `OOMKilled` due to inadequate available memory.

To detect the problem, run the `kubectl describe pod` command and check the results for the following content:

[source,sh]
----
Last State: Terminated
Reason: OOMKilled
Exit Code: 137
----

To resolve the problem, allocate additional memory to the agent and then restart it.