-
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
some agents go offline, some agents report startup issues #1772
Comments
This caught my attention. Is there any other beat running? perhaps a filebeat to collect logs from the VM?
|
I'm going to run the test again. We added code to tag the IP of the VM so I will login and look if there are issues. |
that's good :) Check the status ( |
btw, the integration s should not conflict, the agent should correctly turn it into a single config for each beats necessary for the integrations |
|
elastic-agent-diagnostics-2022-11-23T17-02-03Z-00.zip was emailed to Anderson. |
How is the agent installed on the VMs? This error is due to an inconsistent state, it's like filebeat was abruptly finished and did not clean its lock file. To fix that, it'd be necessary to delete the lock file. It's located on:
|
This should be fixed in 8.5.1. Note that the original bug has been reopened (elastic/beats#31670) with reports that we haven't fixed it on containers where the agent or beats can get recycled PIDs, but that shouldn't apply to VMs. |
You can recover from this by deleting the lock file as is suggested above. |
I was able to correct the issue by doing ...
|
Forgot to add this info yesterday ... this is how the agent is installed on the VMs.
|
Issues encountered during Fleet Scaling testing with drones and a subset of real VMs.
Version: 8.5.0
Operating System: Linux Ubuntu VM (e2-standard-8)
Steps to Reproduce:
We used some tooling to bring up 200 VMs and 9800 Horde drones, some VM's report errors in the logs on the way up and take longer to come up. Once we begin testing some VMs go unhealthy(18/199).
Here is an example of the errors on startup:
The text was updated successfully, but these errors were encountered: