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.

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

ERROR [ExtractorFilter] Could not apply extractor #896

Ubay opened this issue Jan 19, 2015 · 0 comments

ERROR [ExtractorFilter] Could not apply extractor #896

Ubay opened this issue Jan 19, 2015 · 0 comments


Copy link

@Ubay Ubay commented Jan 19, 2015


I have a graylog 0.92.4 server and sometimes i get the following error in /var/log/graylog2-server/server.log:

2015-01-19T12:25:06.979Z ERROR [ExtractorFilter] Could not apply extractor.
java.lang.ArrayIndexOutOfBoundsException: 1
        at org.graylog2.inputs.extractors.SplitAndIndexExtractor.cut(
        at org.graylog2.plugin.inputs.Extractor.runExtractor(
        at org.graylog2.filters.ExtractorFilter.filter(
        at org.graylog2.buffers.processors.ServerProcessBufferProcessor.handleMessage(
        at org.graylog2.shared.buffers.processors.ProcessBufferProcessor.onEvent(
        at org.graylog2.shared.buffers.processors.ProcessBufferProcessor.onEvent(
        at com.codahale.metrics.InstrumentedExecutorService$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

I have enabled the "dead letters" feature but for this case i get no information about the extractor with the problem. I have several Split and Index extractors.

Is there any way to get more info to identify the extractor?

Thanks in advance.

joschi pushed a commit that referenced this issue Jan 19, 2015
@joschi joschi added this to the 1.0.0 milestone Jan 19, 2015
@joschi joschi self-assigned this Jan 19, 2015
@joschi joschi closed this in c3ba09b Jan 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants