This repository has been archived by the owner on Mar 21, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
[DeadEventLoggingListener] Received unhandled event of type org.graylog.plugins.pipelineprocessor... #147
Labels
Comments
I've had the same Problem today, i changed some rules form:
to
then i got this error messages flooding my log:
then i changed it back to.
and everything is normal now. Maybe some problem with the Comment? Graylog 2.2.0+d9681cb on syslog.xyz.local (Oracle Corporation 1.8.0_121 on Linux 3.10.0-327.22.2.el7.x86_64) |
@gruselglatz Is the |
@joschi ups, sry, copy paste error. The end keyword wasn't missing |
+1 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem description
When testing out some pipeline rules, I am seeing inconsistent execution times for the same message when run at different time. I had a thread which has additional information that might give some background to the issue. https://groups.google.com/forum/#!topic/graylog2/FyWgYIzUSMc.
I was having this same issue with a prior version of graylog, which is what prompted me to upgrade to the beta version hoping things would work better but no luck. I do now see some new information in the log files, though.
Steps to reproduce the problem
Environment
Any Ideas?
The text was updated successfully, but these errors were encountered: