I have a problema with send data from filebeat to Logstash

Hello, can you help me pleae, I have a filebeat in my local computer and logstash in a VM Ubuntu in VirtualBox, so I check conectivity from my PC to remote server ubuntu with telnet 192.168.1.12 5044 and was successfull I think... but in my logstash I have a error:

If you need more informatións, please tell me! Thanks so much.

[2023-01-31T12:11:55,485][INFO ][logstash.javapipeline    ] Pipeline terminated {"pipeline.id"=>"input"}

[2023-01-31T12:12:40,658][WARN ][org.logstash.instrument.metrics.gauge.LazyDelegatingGauge] A gauge metric of an unknown type (org.jruby.specialized.RubyArrayOneObject) has been created for key: send_to. This may result in invalid serialization.  It is recommended to log an issue to the responsible developer/development team.

[2023-01-31T12:12:40,757][INFO ][logstash.javapipeline    ] Starting pipeline {:pipeline_id=>"input", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>500, "pipeline.sources"=>["/etc/logstash/conf.d/input.conf"], :thread=>"#<Thread:0x748810fe@/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:131 run>"}

[2023-01-31T12:12:42,501][INFO ][logstash.javapipeline    ] Pipeline Java execution initialization time {"seconds"=>1.74}

[2023-01-31T12:12:42,579][INFO ][logstash.inputs.beats    ] Starting input listener {:address=>"0.0.0.0:5044"}

[2023-01-31T12:12:42,622][INFO ][logstash.javapipeline    ] Pipeline started {"pipeline.id"=>"input"}

[2023-01-31T12:12:42,975][INFO ][org.logstash.beats.Server] Starting server on port: 5044





[2023-01-31T12:22:59,893][INFO ][org.logstash.beats.BeatsHandler] [local: 192.168.1.12:5044, remote: 192.168.1.10:58674] Handling exception: java.net.SocketException: Connection reset (caused by: java.net.SocketException: Connection reset)

[2023-01-31T12:22:59,893][INFO ][org.logstash.beats.BeatsHandler] [local: 192.168.1.12:5044, remote: 192.168.1.10:58676] Handling exception: java.net.SocketException: Connection reset (caused by: java.net.SocketException: Connection reset)

[2023-01-31T12:22:59,896][WARN ][io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.

java.net.SocketException: Connection reset

	at sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:394) ~[?:?]

	at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:426) ~[?:?]

	at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253) ~[netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350) ~[netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) ~[netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719) ~[netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655) ~[netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581) ~[netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) [netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-all-4.1.65.Final.jar:4.1.65.Final]

	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-all-4.1.65.Final.jar:4.1.65.Final]

	at java.lang.Thread.run(Thread.java:833) [?:?]

[2023-01-31T12:22:59,898][WARN ][io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.

java.net.SocketException: Connection reset

	at sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:394

How did you set filebeat.yml and input.conf, with our without https?

1 Like

Hi Rios, the pipeline is works for me, I forgot the enable input with "True" in filebeat.yml

Excellent! Self-resolving cases are the best :slight_smile:

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.