-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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][logstash.pipeline] A plugin had an unrecoverable error. Will restart this plugin #6279
Comments
looking at |
Thanks. Two instances were running. Its fixed now. I will update the ticket. Thank you. On Nov 18, 2016 10:26 PM, "João Duarte" notifications@github.com wrote:
|
we should shutdown gracefully or provide a better error message when the port is in use. The stacktrace is not useful to our users. I've created an issue here: logstash-plugins/logstash-input-beats#161 |
You are right. I was not aware of logstash using initctl. so used the kill
command.
Thanks for the information.
regards,
Arun
…On Tue, Nov 22, 2016 at 11:29 PM, Suyog Rao ***@***.***> wrote:
we should shutdown gracefully or provide a better error message when the
port is in use. The stacktrace is not useful to our users. I've created an
issue here: logstash-plugins/logstash-input-beats#161
<logstash-plugins/logstash-input-beats#161>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6279 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARZWJUugK9hMXh6miF_ONobUdS8UoNIEks5rAy18gaJpZM4K2fro>
.
|
Something else that can cause the issue, is if you have two identical input configuration in your logstash config
twice, it will cause the same error |
Thanks Julien.
Two instances was running, after killing one instance it worked like charm.
Thanks for email.
Regards,
Arun
…On Wed, Jan 4, 2017 at 9:06 PM, Julien Vey ***@***.***> wrote:
Something else that can cause the issue, is if you have two identical
input configuration in your logstash config
input {
beats {
port => 5044
}
}
twice, it will cause the same error
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6279 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARZWJViYc5z02LGuPfTVlKOW8_TCceyIks5rO7xngaJpZM4K2fro>
.
|
João Duarte Two instances were running ,used kill command ,it is working fine now . thank you |
Hi, Maybe a newbie question. ][ERROR][logstash.pipeline ] A plugin had an unrecoverable error. Will restart this plugin. |
@suraj1538 if two instances are running then kill the process and restart logstash server |
getting the same issue .. any suggestion. |
logstash will read |
If anyone stumbles upon this, I had a Edit: it does not seem to be related to the filename, just having a file in the pipelines folder was enough to get logstash to read it, probably because I'm using https://github.com/deviantony/docker-elk |
I have logstash-5.0.1-1.noarch installed in redhat server. I have ELK in one server and filebeat installed in another server. Filebeat config looks good and no errors. It is pushing the logs to logstash server. From logstash to Eleasticsearch the data is not pushed to ES database. The error is shown when logstash pipleline is started.
Here is the configuration, please help figure out the issue.
The below is the /etc/logstash/logstash.yml
Error output from /var/log/logstash/logstash-plain.log
The text was updated successfully, but these errors were encountered: