I facing error while setup elasticsearch cluster in docker using 2 host server those servers from azure ERROR i am getting like this Peer{transportAddress=10.33.8.79:9300, discoveryNode=null, peersRequestInFlight=false} connection failed org.elasticsearc

Elastic Stack Elasticsearch
1 
ERROR: [2024-01-04T09:04:24,575][DEBUG][o.e.d.PeerFinder         ] [odfe-node2] Peer{transportAddress=10.33.8.79:9300, discoveryNode=null, peersRequestInFlight=false} connection failed
org.elasticsearch.transport.ConnectTransportException: [odfe-node2][172.22.0.2:9300] local node found
        at org.elasticsearch.discovery.HandshakingTransportAddressConnector$1$1$1.innerOnResponse(HandshakingTransportAddressConnector.java:105) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.discovery.HandshakingTransportAddressConnector$1$1$1.innerOnResponse(HandshakingTransportAddressConnector.java:95) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.action.NotifyOnceListener.onResponse(NotifyOnceListener.java:40) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.action.ActionListener$4.onResponse(ActionListener.java:163) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.transport.TransportService$5.onResponse(TransportService.java:476) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.transport.TransportService$5.onResponse(TransportService.java:466) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.action.ActionListenerResponseHandler.handleResponse(ActionListenerResponseHandler.java:54) [elasticsearch-7.10.2.jar:7.10.2]
        at com.amazon.opendistroforelasticsearch.security.transport.OpenDistroSecurityInterceptor$RestoringTransportResponseHandler.handleResponse(OpenDistroSecurityInterceptor.java:278) [opendistro_security-1.13.1.0.jar:1.13.1.0]
        at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleResponse(TransportService.java:1171) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.transport.InboundHandler.doHandleResponse(InboundHandler.java:253) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.transport.InboundHandler.lambda$handleResponse$1(InboundHandler.java:247) [elasticsearch-7.10.2.jar:7.10.2]
        at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:684) [elasticsearch-7.10.2.jar:7.10.2]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
        at java.lang.Thread.run(Thread.java:832) [?:?]
[2024-01-04T09:04:24,575][TRACE][o.e.t.n.ESLoggingHandler ] [odfe-node2] [id: 0x8b30f6c6, L:/172.22.0.2:9300 - R:/172.22.0.1:39934] USER_EVENT: SslCloseCompletionEvent(SUCCESS)
[2024-01-04T09:04:24,576][TRACE][o.e.t.n.ESLoggingHandler ] [odfe-node2] [id: 0xf67bd2fe, L:/172.22.0.2:49510 ! R:/10.33.8.79:9300] USER_EVENT: SslCloseCompletionEvent(java.nio.channels.ClosedChannelException)
[2024-01-04T09:04:24,576][TRACE][o.e.t.n.ESLoggingHandler ] [odfe-node2] [id: 0xf67bd2fe, L:/172.22.0.2:49510 ! R:/10.33.8.79:9300] INACTIVE
[2024-01-04T09:04:24,576][TRACE][o.e.t.n.ESLoggingHandler ] [odfe-node2] [id: 0xf67bd2fe, L:/172.22.0.2:49510 ! R:/10.33.8.79:9300] UNREGISTERED
[2024-01-04T09:04:24,576][TRACE][o.e.t.n.ESLoggingHandler ] [odfe-node2] [id: 0x8b30f6c6, L:/172.22.0.2:9300 ! R:/172.22.0.1:39934] INACTIVE
[2024-01-04T09:04:24,577][TRACE][o.e.t.n.ESLoggingHandler ] [odfe-node2] [id: 0x8b30f6c6, L:/172.22.0.2:9300 ! R:/172.22.0.1:39934] UNREGISTERED
[2024-01-04T09:04:25,555][TRACE][o.e.d.PeerFinder         ] [odfe-node2] probing master nodes from cluster state: nodes:
   {odfe-node2}{PEVkwMFiSDejdmk4dcU0Gg}{DlOAtvwtRSSg5t368L50UA}{172.22.0.2}{172.22.0.2:9300}{dimr}, local

[2024-01-04T09:04:25,555][TRACE][o.e.d.PeerFinder         ] [odfe-node2] startProbe(172.22.0.2:9300) not probing local node
[2024-01-04T09:04:25,556][TRACE][o.e.d.SeedHostsResolver  ] [odfe-node2] resolved host [10.33.8.136:9300] to [10.33.8.136:9300]
[2024-01-04T09:04:25,556][TRACE][o.e.d.SeedHostsResolver  ] [odfe-node2] resolved host [10.33.8.79:9300] to [10.33.8.79:9300]
[2024-01-04T09:04:25,556][TRACE][o.e.d.PeerFinder         ] [odfe-node2] probing resolved transport addresses [10.33.8.136:9300, 10.33.8.79:9300]
[2024-01-04T09:04:25,556][TRACE][o.e.d.PeerFinder         ] [odfe-node2] Peer{transportAddress=10.33.8.79:9300, discoveryNode=null, peersRequestInFlight=false} attempting connection
[2024-01-04T09:04:25,557][TRACE][o.e.d.HandshakingTransportAddressConnector] [odfe-node2] [connectToRemoteMasterNode[10.33.8.79:9300]] opening probe connection
[2024-01-04T09:04:25,557][TRACE][o.e.t.TcpTransport       ] [odfe-node2] Tcp transport client channel opened: Netty4TcpChannel{localAddress=null, remoteAddress=null}
[2024-01-04T09:04:25,558][TRACE][o.e.t.n.ESLoggingHandler ] [odfe-node2] [id: 0xa60bd55b] REGISTERED
[2024-01-04T09:04:25,558][TRACE][o.e.t.n.ESLoggingHandler ] [odfe-node2] [id: 0xa60bd55b] CONNECT: /10.33.8.79:9300
[2024-01-04T09:04:25,559][TRACE][o.e.t.TransportLogger    ] [odfe-node2] Netty4TcpChannel{localAddress=/172.22.0.2:49512, remoteAddress=/10.33.8.79:9300} [length: 51, request id: 923, type: request, version: 6.8.0, action: internal:tcp/handshake] WRITE: 51B

i am getting this error need help on this

cat elasticsearch_node2.yml
cluster.name: "odfe-cluster"
node.name: odfe-node2
network.host: [_site_, _local_]
#network.publish_host: 0.0.0.0
transport.host: 0.0.0.0
transport.port: 9300
discovery.seed_hosts: "10.33.8.136:9300, 10.33.8.79:9300"
cluster.initial_master_nodes: "odfe-node1, odfe-node2"
bootstrap.memory_lock: true
# # minimum_master_nodes need to be explicitly set when bound on a public IP
# # set to 1 to allow single node clusters
# # Details: https://github.com/elastic/elasticsearch/pull/17288
#discovery.zen.minimum_master_nodes: 2
logger.org.elasticsearch.discovery: TRACE
logger.org.elasticsearch.transport: TRACE
# # Breaking change in 7.0
# # https://www.elastic.co/guide/en/elasticsearch/reference/7.0/breaking-changes-7.0.html#breaking_70_discovery_changes
# cluster.initial_master_nodes:
#    - elasticsearch1
#    - docker-test-node-1
######## Start OpenDistro for Elasticsearch Security Demo Configuration ########
# WARNING: revise all the lines below before you go into production
opendistro_security.ssl.transport.pemcert_filepath: odfe-node2.pem
opendistro_security.ssl.transport.pemkey_filepath: odfe-node2.key
opendistro_security.ssl.transport.pemtrustedcas_filepath: MyRootCA.pem
opendistro_security.ssl.transport.enforce_hostname_verification: false
opendistro_security.ssl.transport.enabled_ciphers: "TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA"
opendistro_security.ssl.http.enabled: true
opendistro_security.ssl.http.pemcert_filepath: odfe-node2.pem
opendistro_security.ssl.http.pemkey_filepath: odfe-node2.key
opendistro_security.ssl.http.pemtrustedcas_filepath: MyRootCA.pem
opendistro_security.ssl.http.enabled_protocols:
    - 'TLSv1.2'
opendistro_security.nodes_dn:
    - 'CN=odfe-node1,OU=IT,O=ExampleOrg,L=SL,ST=SS,C=US'
    - 'CN=odfe-node2,OU=IT,O=ExampleOrg,L=SL,ST=SS,C=US'
    - 'CN=odfe-cluster*'
    - '/CN=.*regex/'
#opendistro_security.allow_unsafe_democertificates: true   ## Reoved for Selfigned cert
opendistro_security.allow_default_init_securityindex: true
opendistro_security.authcz.admin_dn:
    - 'CN=ADMIN,OU=IT,O=ExampleOrg,L=SL,ST=SS,C=US'

opendistro_security.audit.type: internal_elasticsearch
opendistro_security.enable_snapshot_restore_privilege: true
opendistro_security.check_snapshot_restore_write_privileges: true
opendistro_security.restapi.roles_enabled: ["all_access", "security_rest_api_access"]
cluster.routing.allocation.disk.threshold_enabled: false
node.max_local_storage_nodes: 3
######## End OpenDistro for Elasticsearch Security Demo Configuration ########

i am setuping elasticsearch cluster in docker using 2 host azure servers but i facing above error can you please help me on this

2

OpenSearch/OpenDistro are AWS run products and differ from the original Elasticsearch and Kibana products that Elastic builds and maintains. You may need to contact them directly for further assistance.

(This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: )

3

@warkolm @DavidTurner
please help on my issue

4

Hey

Apparently, you are not using Elasticsearch but another product.
If you switch your platform to Elasticsearch we can hopefully help as we know the code running behind the scene :wink:

BTW did you look at Cloud by Elastic, also available if needed from Azure Marketplace?
That's the easiest way to deploy Elasticsearch on Azure nowadays.

Cloud by elastic is one way to have access to all features, all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, Maps UI, Alerting and built-in solutions named Observability, Security, Enterprise Search and what is coming next :slight_smile: ...

5

In addition to the fact that your question is unrelated to Elasticsearch as David P mentions, it's rather rude to ping random volunteers to try and get their attention, and extremely rude to do so just one hour after your original post. See https://www.elastic.co/community/codeofconduct for more details, particularly the "be patient" section.

1 Like
6

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