-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Crashing 5.0.0-alpha1 #1466
Comments
For reference: https://discuss.elastic.co/t/crashing-5-0-0-alpha1/48212 |
@LoungeFlyZ Thanks for the report. Could you post the full panic you get? Sometimes there is some more information below about the line that it exactly happens. @monicasarbu Based on the panic I would think the error is filter related, but it seems like no filters are configured? |
The panic happens before the event is passed to the generic filtering when it's trying to convert the fields of the event to basic types. It might be due to a strange type that is found in the json object. |
@ruflin that's the full panic. There isn't anything logged after this. Prior it logs out the log entries like this:
Then the rest of the panic is listed. If i understood correctly, you are right ... i'm not using any filters. |
@LoungeFlyZ thanks for the good bug report. This is an example line causing the panic:
More precisely, it's the |
The cause was a nil value in the incoming JSON, which the generic filtering code didn't expect. I considered adding a `recover` to generic filtering so that things like this don't crash the whole process, but decided against. One reason is that it's better to discover these things while we're still in alpha/beta. Second is that if we recover here, there could still be a crash later in filtering our outputs. Also took the opportunity to add a couple of system tests that combine json and generic filtering.
The cause was a nil value in the incoming JSON, which the generic filtering code didn't expect. I considered adding a `recover` to generic filtering so that things like this don't crash the whole process, but decided against. One reason is that it's better to discover these things while we're still in alpha/beta. Second is that if we recover here, there could still be a crash later in filtering our outputs. Also took the opportunity to add a couple of system tests that combine json and generic filtering.
That's right, thanks. |
Thanks everyone for you help with this! I have the nightly running fine now. Much appreciated! |
I am hitting a problem where filebeat is crashing 5.0.0-alpha1 like this:
I am playing with 5.0.0-alpha1 for the JSON support. I am using the same filebeat.yml file as with 1.2 except with the added JSON section:
Repro'd on OSX and linux (debian:jessie)
Here are the log files i am testing this with that repro this issue:
https://dl.dropboxusercontent.com/u/27238389/logs.zip
Any ideas?
The text was updated successfully, but these errors were encountered: