-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Windows service for Beat does not stop gracefully #38666
Open
Labels
bug
Team:Elastic-Agent
Label for the Agent team
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
Comments
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Mar 27, 2024
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
botelastic
bot
removed
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Mar 27, 2024
pierrehilbert
added
the
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
label
Jun 3, 2024
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
6 tasks
4 tasks
Re-introduced by revert #40705 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Team:Elastic-Agent
Label for the Agent team
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
Version
8.13.0
Operating System
Windows Server 2019
Steps to Reproduce:
Observed behavior
The Event Viewer shows messages like this:
Expected behavior
The service stops gracefully and there are no messages like the one shown above in the Event Viewer.
Related
A similar issue was reported for Elastic Agent in #27527. It was fixed in #27730. The fix was to wait until the stop was reported to the service manager or wait 500ms, whichever happens first. We need a similar fix for Beats.
The text was updated successfully, but these errors were encountered: