I have Filebeat 8.11.1 configured on a server running Windows Server 2019 with an output to Logstash. I have Logstash 8.11.1 configured on a server running Windows Server 2022 with an input from beats and an output to JDBC.
The connection is reset when ingesting data from Filebeat to Logstash. How do I fix this?
[2023-12-05T13:01:22,793][INFO ][logstash.runner ] Log4j configuration path used is: E:\logstash\config\log4j2.properties
[2023-12-05T13:01:22,809][INFO ][logstash.runner ] Starting Logstash {"logstash.version"=>"8.11.1", "jruby.version"=>"jruby 9.4.2.0 (3.1.0) 2023-03-08 90d2913fda OpenJDK 64-Bit Server VM 17.0.9+9 on 17.0.9+9 +indy +jit [x86_64-mswin32]"}
[2023-12-05T13:01:22,809][INFO ][logstash.runner ] JVM bootstrap flags: [-Xms4g, -Xmx4g, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djruby.compile.invokedynamic=true, -XX:+HeapDumpOnOutOfMemoryError, -Djava.security.egd=file:/dev/urandom, -Dlog4j2.isThreadContextMapInheritable=true, -Djruby.regexp.interruptible=true, -Djdk.io.File.enableADS=true, --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED, --add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED, --add-exports=jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED, --add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED, --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED, --add-opens=java.base/java.security=ALL-UNNAMED, --add-opens=java.base/java.io=ALL-UNNAMED, --add-opens=java.base/java.nio.channels=ALL-UNNAMED, --add-opens=java.base/sun.nio.ch=ALL-UNNAMED, --add-opens=java.management/sun.management=ALL-UNNAMED]
[2023-12-05T13:01:22,840][WARN ][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified
[2023-12-05T13:01:24,007][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600, :ssl_enabled=>false}
[2023-12-05T13:01:25,179][INFO ][org.reflections.Reflections] Reflections took 125 ms to scan 1 urls, producing 132 keys and 464 values
[2023-12-05T13:01:28,059][INFO ][logstash.javapipeline ] Pipeline `main` is configured with `pipeline.ecs_compatibility: v8` setting. All plugins in this pipeline will default to `ecs_compatibility => v8` unless explicitly configured otherwise.
[2023-12-05T13:01:28,080][INFO ][logstash.outputs.jdbc ][main] JDBC - Starting up
[2023-12-05T13:01:28,104][INFO ][com.zaxxer.hikari.HikariDataSource][main] HikariPool-1 - Starting...
[2023-12-05T13:01:28,319][INFO ][com.zaxxer.hikari.HikariDataSource][main] HikariPool-1 - Start completed.
[2023-12-05T13:01:28,332][INFO ][logstash.outputs.jdbc ][main] JDBC - Starting up
[2023-12-05T13:01:28,333][INFO ][com.zaxxer.hikari.HikariDataSource][main] HikariPool-2 - Starting...
[2023-12-05T13:01:28,338][INFO ][com.zaxxer.hikari.HikariDataSource][main] HikariPool-2 - Start completed.
[2023-12-05T13:01:28,339][WARN ][logstash.filters.grok ][main] ECS v8 support is a preview of the unreleased ECS v8, and uses the v1 patterns. When Version 8 of the Elastic Common Schema becomes available, this plugin will need to be updated
[2023-12-05T13:01:28,433][WARN ][logstash.filters.grok ][main] ECS v8 support is a preview of the unreleased ECS v8, and uses the v1 patterns. When Version 8 of the Elastic Common Schema becomes available, this plugin will need to be updated
[2023-12-05T13:01:28,527][INFO ][logstash.javapipeline ][main] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>32, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>4000, "pipeline.sources"=>["E:/logstash/for_hou-ls4.conf"], :thread=>"#<Thread:0x2cfeb9b9 E:/logstash/logstash-core/lib/logstash/java_pipeline.rb:134 run>"}
[2023-12-05T13:01:31,050][INFO ][logstash.javapipeline ][main] Pipeline Java execution initialization time {"seconds"=>2.52}
[2023-12-05T13:01:31,062][INFO ][logstash.inputs.beats ][main] Starting input listener {:address=>"0.0.0.0:5044"}
[2023-12-05T13:01:31,077][INFO ][logstash.javapipeline ][main] Pipeline started {"pipeline.id"=>"main"}
[2023-12-05T13:01:31,096][INFO ][logstash.agent ] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]}
[2023-12-05T13:01:31,296][INFO ][org.logstash.beats.Server][main][cb11f0d15b0141deaed189e2bb8d61ff361425a9bbce7dc18ad6d3dcfa517fdf] Starting server on port: 5044
[2023-12-05T13:01:53,809][INFO ][org.logstash.beats.BeatsHandler][main][cb11f0d15b0141deaed189e2bb8d61ff361425a9bbce7dc18ad6d3dcfa517fdf] [local: 192.168.1.3:5044, remote: 10.1.5.10:57923] Handling exception: java.net.SocketException: Connection reset (caused by: java.net.SocketException: Connection reset)
[2023-12-05T13:01:53,809][INFO ][org.logstash.beats.BeatsHandler][main][cb11f0d15b0141deaed189e2bb8d61ff361425a9bbce7dc18ad6d3dcfa517fdf] [local: 192.168.1.3:5044, remote: 10.1.5.10:57924] Handling exception: java.net.SocketException: Connection reset (caused by: java.net.SocketException: Connection reset)
[2023-12-05T13:01:53,810][WARN ][io.netty.channel.DefaultChannelPipeline][main][cb11f0d15b0141deaed189e2bb8d61ff361425a9bbce7dc18ad6d3dcfa517fdf] 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:254) ~[netty-buffer-4.1.100.Final.jar:4.1.100.Final]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-buffer-4.1.100.Final.jar:4.1.100.Final]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357) ~[netty-transport-4.1.100.Final.jar:4.1.100.Final]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) ~[netty-transport-4.1.100.Final.jar:4.1.100.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) ~[netty-transport-4.1.100.Final.jar:4.1.100.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) ~[netty-transport-4.1.100.Final.jar:4.1.100.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) ~[netty-transport-4.1.100.Final.jar:4.1.100.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) [netty-transport-4.1.100.Final.jar:4.1.100.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.100.Final.jar:4.1.100.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.100.Final.jar:4.1.100.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.100.Final.jar:4.1.100.Final]
at java.lang.Thread.run(Thread.java:840) [?:?]