-
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
Reduce errors on filebeat syslog stop #8347
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ph
approved these changes
Sep 18, 2018
@jsoriano Maybe add a changelog entry? |
Changelog entry added |
jsoriano
force-pushed
the
filebeat-syslog-stop
branch
from
September 19, 2018 08:07
ff2be84
to
3634106
Compare
jenkins, test this again please |
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Sep 20, 2018
Fix a couple of errors seen when syslog input is stopped. In case the input couldn't be started (e.g. port was already in use), there was a nil pointer reference error when trying to stop it. In any case, on stop, an error about use of closed connection was logged lots of times: (cherry picked from commit 9b27040)
jsoriano
added
v6.5.0
and removed
needs_backport
PR is waiting to be backported to other branches.
labels
Sep 20, 2018
jsoriano
added a commit
to jsoriano/beats
that referenced
this pull request
Sep 20, 2018
Fix a couple of errors seen when syslog input is stopped. In case the input couldn't be started (e.g. port was already in use), there was a nil pointer reference error when trying to stop it. In any case, on stop, an error about use of closed connection was logged lots of times: (cherry picked from commit 9b27040)
jsoriano
added a commit
that referenced
this pull request
Sep 24, 2018
Fix a couple of errors seen when syslog input is stopped. In case the input couldn't be started (e.g. port was already in use), there was a nil pointer reference error when trying to stop it. In any case, on stop, an error about use of closed connection was logged lots of times. (cherry picked from commit 9b27040)
jsoriano
added a commit
that referenced
this pull request
Oct 16, 2018
Fix a couple of errors seen when syslog input is stopped. In case the input couldn't be started (e.g. port was already in use), there was a nil pointer reference error when trying to stop it. In any case, on stop, an error about use of closed connection was logged lots of times: (cherry picked from commit 9b27040)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
Fix a couple of errors seen when syslog input is stopped. In case the input couldn't be started (e.g. port was already in use), there was a nil pointer reference error when trying to stop it. In any case, on stop, an error about use of closed connection was logged lots of times. (cherry picked from commit e39ae43)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix a couple of errors seen when syslog input is stopped.
In case the input couldn't be started (e.g. port was already in use), there was a nil pointer reference when trying to stop it:
In any case, on stop, this error was logged lots of times: