-
Notifications
You must be signed in to change notification settings - Fork 154
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
Elastic-Agent standalone fails to start on Linux if /tmp
is a tmpfs
#4628
Comments
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Is the agent installed when this happens? Is it installed as root? Can your user succeed with |
No, it's a standalone Elastic-Agent, not installed.
Yes, my user can succeed running |
The way I'm running it:
|
If you run it as root and/or install it does this get fixed? |
Running as root does not change anything. Installing creates other problems. I'll have to carefully reproduce/report later/next week. But the gist is: install succeeds, the Elastic-Agent does not start and I cannot uninstall it. |
On a Linux VM (Archlinux) whenever I try to start a standalone Elastic-Agent (built from a recent
main
) I get the following error:Full logs:
It just stays in this error loop with Filebeat never starting. It likely affects other Beats as well, but on my tests only Filebeat was used. Here are a whole set of logs until Filebeat is restarted
Creating the folder
/tmp/elastic-agent
solves the problem.Details about my
/tmp
:The text was updated successfully, but these errors were encountered: