-
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
Beats running as a windows service randomly fail to restart #18914
Labels
Comments
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Jun 2, 2020
adriansr
added
Team:SIEM
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Jun 2, 2020
Pinging @elastic/siem (Team:SIEM) |
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Jun 2, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Fixes elastic#18914
adriansr
added a commit
that referenced
this issue
Jun 5, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes #18914
6 tasks
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Jun 5, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes elastic#18914 (cherry picked from commit f3ab7c7)
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Jun 5, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes elastic#18914 (cherry picked from commit f3ab7c7)
6 tasks
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Jun 5, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes elastic#18914 (cherry picked from commit f3ab7c7)
6 tasks
adriansr
added a commit
that referenced
this issue
Jun 8, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes #18914 (cherry picked from commit f3ab7c7)
adriansr
added a commit
that referenced
this issue
Jun 8, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes #18914 (cherry picked from commit f3ab7c7)
adriansr
added a commit
that referenced
this issue
Jun 8, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes #18914 (cherry picked from commit f3ab7c7)
melchiormoulin
pushed a commit
to melchiormoulin/beats
that referenced
this issue
Oct 14, 2020
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes elastic#18914
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
Update the Windows service handling logic so that the service doesn't transition to the STOPPED state until the beater is terminated. Before this patch, a Beats service would report to be STOPPED as soon as it received the stop request. This causes some problems during service restarts, as the new service would start while the old one was still cleaning up. Fixes elastic#18914 (cherry picked from commit 78e355b)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For confirmed bugs, please report:
Running the following powershell:
(and possibly any other Beat running as a service) can result in a failure to start the service:
Logs contain the following error:
The text was updated successfully, but these errors were encountered: