Elasticsearch shutdowns every few days with this error

Elastic Stack Elasticsearch
1

My elasticsearch instance is connected to an application server I.e Liferay as a search engine.
I am getting the below error randomly every few days.

Can anyone explain what this means and how can I solve this?

[2022-06-26T23:59:35,269][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] invalid internal transport message format, got (4a,52,4d,49), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:52254}], closing connection
[2022-06-26T23:59:41,302][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] invalid internal transport message format, got (80,0,0,28), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:33000}], closing connection
[2022-06-26T23:59:41,533][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] invalid internal transport message format, got (0,1e,0,6), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:33210}], closing connection
[2022-06-26T23:59:41,764][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] invalid internal transport message format, got (48,45,4c,50), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:33348}], closing connection
[2022-06-26T23:59:41,991][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] SSL/TLS request received but SSL/TLS is not enabled on this node, got (16,3,0,0), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:33528}], closing connection
[2022-06-26T23:59:42,223][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] SSL/TLS request received but SSL/TLS is not enabled on this node, got (16,3,0,0), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:33696}], closing connection
[2022-06-26T23:59:42,449][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] invalid internal transport message format, got (0,0,0,71), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:33862}], closing connection
[2022-06-26T23:59:42,681][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] invalid internal transport message format, got (0,0,0,a4), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:34042}], closing connection
[2022-06-26T23:59:42,907][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] invalid internal transport message format, got (6c,0,b,0), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:34176}], closing connection
[2022-06-26T23:59:43,536][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] SSL/TLS request received but SSL/TLS is not enabled on this node, got (16,3,0,0), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:34576}], closing connection
[2022-06-26T23:59:43,590][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] invalid internal transport message format, got (e,0,0,0), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:34736}], closing connection
[2022-06-26T23:59:43,840][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] SSL/TLS request received but SSL/TLS is not enabled on this node, got (16,3,0,0), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:34986}], closing connection
[2022-06-26T23:59:53,721][WARN ][o.e.t.TcpTransport ] [elasticsearchnode_1] SSL/TLS request received but SSL/TLS is not enabled on this node, got (16,3,1,2), [Netty4TcpChannel{localAddress=/...:9300, remoteAddress=/...:40696}], closing connection

2

Just to be clear - there are no errors there, only warnings. And there's nothing there that shows Elasticsearch shutting down, as your title mentions.

This one seems pretty clear, you will need to find the source and see why it's wanting to use TLS - which we would recommend using anyway.

It's possible that something is wanting to talk to Elasticsearch via the HTTP API (ie on port 9200), but it's sending it to the transport API (ie port 9300).

(Also, please format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you :slight_smile:)

3

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