Logstash Error: A plugin had an unrecoverable error. Will restart this plugin.Address already in use

# 异常出现场景

        使用filebeat + ELK进行日志采集分析，由于是使用docker部署的ELK发现容器正常，就没有去查看容器的详细日志，发现这个异常是因为在kibana中查看采集的日志的时候有很多条重复的日志，在filebeat的日志发现时常连接不上logstash，会发生重试。随即在logstash日志中发现异常报错。

logstash plugin发生异常，并进行了重启。

[ERROR][logstash.javapipeline    ][main][26c88b816999b4576d5ced7ce2d08942df2dc5b0a0170a572d1e2c8c64527ce8] A plugin had an unrecoverable error. Will restart this plugin.
Pipeline_id:main
Plugin: <LogStash::Inputs::Beats port=>5044, id=>"26c88b816999b4576d5ced7ce2d08942df2dc5b0a0170a572d1e2c8c64527ce8", enable_metric=>true, codec=><LogStash::Codecs::Plain id=>"plain_3416fcc7-573a-4ece-bb09-c27879011b26", enable_metric=>true, charset=>"UTF-8">, host=>"0.0.0.0", ssl=>false, add_hostname=>false, ssl_verify_mode=>"none", ssl_peer_metadata=>false, include_codec_tag=>true, ssl_handshake_timeout=>10000, tls_min_version=>1, tls_max_version=>1.2, cipher_suites=>["TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256", "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256", "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384", "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384", "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256", "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256"], client_inactivity_timeout=>60, executor_threads=>56>
Error: Address already in use
Exception: Java::JavaNet::BindException
Stack: sun.nio.ch.Net.bind0(Native Method)
sun.nio.ch.Net.bind(sun/nio/ch/Net.java:455)
sun.nio.ch.Net.bind(sun/nio/ch/Net.java:447)
sun.nio.ch.ServerSocketChannelImpl.bind(sun/nio/ch/ServerSocketChannelImpl.java:227)
io.netty.channel.socket.nio.NioServerSocketChannel.doBind(io/netty/channel/socket/nio/NioServerSocketChannel.java:134)
io.netty.channel.AbstractChannel$AbstractUnsafe.bind(io/netty/channel/AbstractChannel.java:550)
io.netty.channel.DefaultChannelPipeline$HeadContext.bind(io/netty/channel/DefaultChannelPipeline.java:1334)
io.netty.channel.AbstractChannelHandlerContext.invokeBind(io/netty/channel/AbstractChannelHandlerContext.java:506)
io.netty.channel.AbstractChannelHandlerContext.bind(io/netty/channel/AbstractChannelHandlerContext.java:491)
io.netty.channel.DefaultChannelPipeline.bind(io/netty/channel/DefaultChannelPipeline.java:973)
io.netty.channel.AbstractChannel.bind(io/netty/channel/AbstractChannel.java:248)
io.netty.bootstrap.AbstractBootstrap$2.run(io/netty/bootstrap/AbstractBootstrap.java:356)
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(io/netty/util/concurrent/AbstractEventExecutor.java:164)
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(io/netty/util/concurrent/SingleThreadEventExecutor.java:472)
io.netty.channel.nio.NioEventLoop.run(io/netty/channel/nio/NioEventLoop.java:500)
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(io/netty/util/concurrent/SingleThreadEventExecutor.java:989)
io.netty.util.internal.ThreadExecutorMap$2.run(io/netty/util/internal/ThreadExecutorMap.java:74)
io.netty.util.concurrent.FastThreadLocalRunnable.run(io/netty/util/concurrent/FastThreadLocalRunnable.java:30)
java.lang.Thread.run(java/lang/Thread.java:834)

排查解决方法

1.查看是否存在其他进程占用端口号

netstat -tuln | grep 5044

如果存在其他进程占用，可以考虑更换logstash端口，或者kill掉占用进程；

2.检查logstash的配置是否正确

检查logstash的pipeline目录下的logstash.conf配置是否编写有误

3.最后一步检查一下是否存在备份文件

为了防止把配置文件改坏，就把pipeline下的logstash.conf做了一个logstash.conf.bak备份，就是因为这个备份就导致logstash抛出上面所出现异常，只需把备份文件删除，或者换个位置存放就好了。希望能够帮助遇到同样问题的人。

问题解决参考博客：

​https://stackoverflow.com/questions/47680499/logstash-error-address-already-in-use ​