Cherry-pick #8347 to 6.x: Reduce errors on filebeat syslog stop#8376
Merged
jsoriano merged 2 commits intoelastic:6.xfrom Oct 16, 2018
Merged
Cherry-pick #8347 to 6.x: Reduce errors on filebeat syslog stop#8376jsoriano merged 2 commits intoelastic:6.xfrom
jsoriano merged 2 commits intoelastic:6.xfrom
Conversation
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)
Contributor
|
Needs a rebase. |
Member
Author
|
Changelog line was already merged in #8433 |
This file contains hidden or 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
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.
Cherry-pick of PR #8347 to 6.x branch. Original message:
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: