Skip to content
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.

Sign up for GitHub

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

Jump to bottom

filebeat nil point crash when new configuration pushed from kibana central management #11945

Closed
jerryjune opened this issue Apr 26, 2019 · 2 comments · Fixed by #11950
Closed

filebeat nil point crash when new configuration pushed from kibana central management #11945

jerryjune opened this issue Apr 26, 2019 · 2 comments · Fixed by #11950
Assignees
@ph
Labels
bug Filebeat Filebeat Management

Comments

@jerryjune
Copy link

My customer report a filebeat crash bug to me. They have a trial for elastic xpack features. Their filebeats are enrolled and managed in kibana, sometimes when they change the input paths and deploy the new configuration to filebeat, some of the filebeats will crash. From the log, it throws nil pointer error when applying configuration for output, the output is kafka. See following screenshot
Filebeat version 6.7.0
Kafka version 2.12

ErrorImage
@ph ph self-assigned this Apr 26, 2019
@ph
Copy link
Contributor

ph commented Apr 26, 2019

Looking at the code this look like a race inside our kafka client implementation, Connect didn't happen yet and we try to close the producer.

@ph ph mentioned this issue Apr 26, 2019
Merged
@ph
Copy link
Contributor

ph commented Apr 26, 2019

PR is at #11950

@ph ph closed this as completed in #11950 Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ph ph

Labels
bug Filebeat Filebeat Management
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix a race condition with the kafka pipeline client. ph/beats
2 participants
@ph @jerryjune