-
Notifications
You must be signed in to change notification settings - Fork 81
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
Logstash-6.5.2 filter worker crash with Exception in pipelineworker #145
Comments
this can be replicated with:
The issue seems to be around for some time now |
could this be avoided with something like this? public boolean handleEvent(RubyEvent rubyEvent) {
final Event event = rubyEvent.getEvent();
Object input = event.getField(sourceField);
if (input == null) {
return false;
}
String ip;
if (input instanceof List) {
+ if (input.isEmpty()) {
+ return false;
+ }
ip = (String) ((List) input).get(0); in
|
I think I am right with the above..
|
Still troublesome in plugin v7.3.1. This looks like it should be an easy enough fix, similar to the NPE fixed recently by #225 - although here perhaps we should set a tag and continue processing? The logged message for the OOB exception is slightly different these days, and the error causes the pipeline to stop completely (and exit Logstash if it's the only one).
Looks like this was propagated from from the Ruby code, but there it didn't cause an immediate exception and would have been caught by subsequent
(since v7.1.0 the class moved to org/logstash/filters/geoip/GeoIPFilter.java) |
Hello
We have a problem with our Logstash installation and we think it is a bug.
Logstash version: 6.5.2
OS: Centos7
Description
One of the pipelines in our Logstash installation stops working with an "Exception in pipelineworker" error. The pipeline continues accepting events via the defined input but stops processing these events when they have been saved in a persisted queue. The persisted queue for the pipeline will keep growing with new events not processed by filters/output sections.
Cause
We have identified the cause of the problem. The filter worker will crash if one use a geoip filter and the geoip source value is an empty json object. This is triggered because sometimes the clients generate a log with an empty value for the attributte used by geoip/source.
Full errorlog
Pipeline configuration
Sample Data
Steps to Reproduce
Ref: https://discuss.elastic.co/t/logstash-6-5-2-filter-worker-crash-with-exception-in-pipelineworker/159933
The text was updated successfully, but these errors were encountered: