Logstash 1.5.3 issue with elasticsearch 1.6.1/1.7.0 "undefined method"


(M1k3ga) #1

hi there,

yesterday we tried to update our production system.
we have N logstash instances (as shipper) to a few redis instances.
Then there are a few logstash indexer pulling from redis and putting them into the elasticsearch cluster.

with logstash 1.5.1 and elasticsearch 1.6.1 all was fines for weeks.
Now, with logstash 1.5.3 (JDK 7 and 8) we run into the problem that logstash is dying with notification like

"undefined method `close' for nil:NilClass".

Since i am no ruby expert, can anybody be of assistance what went wrong and how to fix this ?

Elasticsearch runs but does not receive events from logstash since logstash dies after nearly 30 sec.

thnx.
mike


(Joe Lawson) #2

An undefined on a nil class sounds like a missing plugin. Make sure with the bin/plugins script that everything you expect is there


(M1k3ga) #3

Continuing the discussion from Logstash 1.5.3 issue with elasticsearch 1.6.1/1.7.0 "undefined method":

I checked our plugins, they were ok so far i could see.

Meanwhile we found the error causing this:
In the configuration folder, where logstash looks for configuration files never ever has to be a folder!.
If, say /tmp/conf is your config folder, then in this folder only files should be located.
Otherwise logstash dies with NO error output useful to find this bug.

Is it worth an issue on github? or who can check this?

best regards,
mike


(David Li) #4

Hello Mike, I have the same problem, could you talk a little more about what you mean by, "configuration files never ever has to be a folder"?


(M1k3ga) #5

Hi David,

you call your logstash with "-f <path_to_config_file_or_folder>".
In our case the path was a folder like e.g. "logstash -f /tmp/ls_configs" where our logstash configuration resides.
The problem then was that inside the folder "/tmp/ls_configs" there was another folder e.g. "/tmp/ls_configs/foo/".
This caused the problem since logstash couldn't handle subfolders in the config path.
After we removed the "foo" folder from the config folder the problem was gone.

Hope i could help,
best regards,
mike


(David Li) #6

Thanks Mike!


(system) #7