ES 6.8.9 + SG 25.6: Connection reset by peer at each request

This is a double post of as we had no answer on the GitLab issue, and it seems the good place to get support is here :slight_smile:

Elasticsearch version: tested with 6.8.6 and 6.8.9

Search Guard version: 25.5 and 25.6

Describe the issue:

We have been deploying Elastcsearch along with Search Guard for a while and since the last release, we get a weird behavior which is flooding our logs. Each requests to the cluster outputs a “Connection reset by peer” error. Any request leads to this error but the one we execute for the following example is GET / and the result is 200 OK with the correct content.

2020-05-19 08:58:20.715755243 +0200 CEST [elasticsearch-1] [2020-05-19T06:58:20,712][ERROR][c.f.s.s.h.n.SearchGuardSSLNettyHttpServerTransport] [] Exception during establishing a SSL connection: Connection reset by peer
2020-05-19 08:58:20.715763272 +0200 CEST [elasticsearch-1] Connection reset by peer
2020-05-19 08:58:20.715764838 +0200 CEST [elasticsearch-1] 	at Method) ~[?:?]
2020-05-19 08:58:20.715765965 +0200 CEST [elasticsearch-1] 	at ~[?:?]
2020-05-19 08:58:20.715766851 +0200 CEST [elasticsearch-1] 	at ~[?:?]
2020-05-19 08:58:20.715767616 +0200 CEST [elasticsearch-1] 	at ~[?:?]
2020-05-19 08:58:20.715816539 +0200 CEST [elasticsearch-1] 	at ~[?:?]
2020-05-19 08:58:20.715818174 +0200 CEST [elasticsearch-1] 	at ~[?:?]
2020-05-19 08:58:20.715819183 +0200 CEST [elasticsearch-1] 	at io.netty.buffer.PooledHeapByteBuf.setBytes( ~[netty-buffer-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715820180 +0200 CEST [elasticsearch-1] 	at io.netty.buffer.AbstractByteBuf.writeBytes( ~[netty-buffer-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715842799 +0200 CEST [elasticsearch-1] 	at ~[netty-transport-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715844245 +0200 CEST [elasticsearch-1] 	at$ [netty-transport-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715845217 +0200 CEST [elasticsearch-1] 	at [netty-transport-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715846179 +0200 CEST [elasticsearch-1] 	at [netty-transport-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715868128 +0200 CEST [elasticsearch-1] 	at [netty-transport-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715869388 +0200 CEST [elasticsearch-1] 	at [netty-transport-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715884696 +0200 CEST [elasticsearch-1] 	at io.netty.util.concurrent.SingleThreadEventExecutor$ [netty-common-4.1.32.Final.jar:4.1.32.Final]
2020-05-19 08:58:20.715885932 +0200 CEST [elasticsearch-1] 	at [?:?]

This is kind of annoying as it really floods the logs on every request.

The previous version was Elasticsearch 6.8.2 along with Search Guard 25.4, and it was working as expected (i.e. no “Connection reset by peer” log at each request)

Is it a known issue on Search Guard side? Do you have any idea on where does it come from?

Thanks a lot for your help :slight_smile:

For your information, I downloaded Search Guard 25.4, updated the file so that the line elasticsearch.version equals 6.8.9, and re-created the archive.

I can now start an Elasticsearch and query it without having my logs flooded :slight_smile:

But I would prefer if it would be possible to use the latest version (25.6) of Search Guard