Reindex remote-Received Error "socket_exception" & "Connection reset"

[Ragul_R]

I'm Copying index remotely cluster1 to Cluster2.[Received Error "socket_exception" & "Connection reset"]

i haved tried Type 1& 2 configuration, im facing same error

elasticsearch.yml

Type1:

reindex.remote.whitelist: ["*:*"]
reindex.ssl.certificate: pc1.crt
reindex.ssl.key: pc1.key
reindex.ssl.certificate_authorities: ca.crt
reindex.ssl.verification_mode: full

Type2:

reindex.remote.whitelist: ["*:*"]
reindex.ssl.verification_mode: none

please me help, how to overcome remotely Reindex SSL issue.

[warkolm (Mark Walkom)]

What is the response if you run that via curl? The 500 error should be reporting a log in the Elasticsearch logs as well.

[Ragul_R]

Curl Command

curl -XPOST "https://pc1.com:9200/_reindex" -H "Content-Type: application/json" -H "Authorization: Basic ZWxhc3RpYzpljAyMQ==" -k -v -d "{\"source\":{\"remote\":{\"host\":\"https://pc1:9200\",\"username\":\"elastic\",\"password\":\"elastic11\"},\"index\": \"testing\"},\"dest\": {\"index\": \"testing1\"}}"

Output for Curl Command:

    Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 10.x.x.102...
* TCP_NODELAY set
* connect to 10.x.x.102 port 9200 failed: Connection refused
* Failed to connect to pc1.com port 9200: Connection refused
* Closing connection 0
curl: (7) Failed to connect to pc1.com port 9200: Connection refused

[warkolm (Mark Walkom)]

@Ragul_R

* Failed to connect to pc1.com port 9200: Connection refused

Ok so Elasticsearch isn't listening, or something is stopping it.
What do the logs on the pc1.com node show?

[Ragul_R]

I'm Copying index remotely cluster1 to Cluster2

Cluster1:

cluster.name: Cluster1
node.name: pc1.com
node.master: true 
node.data: true 
node.ingest: true 
path.data: E:\Elasticstorage-7x\data
path.logs: E:\Elasticstorage-7x\logs
bootstrap.memory_lock: true
network.host: pc1.com
http.port: 9200
discovery.type: single-node
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.key: pc1.key
xpack.security.transport.ssl.certificate: pc1.crt
xpack.security.transport.ssl.certificate_authorities: ca.crt
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.key: pc1.key
xpack.security.http.ssl.certificate: pc1.crt
xpack.security.http.ssl.certificate_authorities: ca.crt


reindex.remote.whitelist: ["*:*"]
reindex.ssl.verification_mode: none

Cluster2:

cluster.name: Cluster1
node.name: pc1.com
node.master: true 
node.data: true 
node.ingest: true 
path.data: E:\Elasticstorage-7x\data
path.logs: E:\Elasticstorage-7x\logs
bootstrap.memory_lock: true
network.host: pc1.com
http.port: 80
discovery.type: single-node
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.key: pc1.key
xpack.security.transport.ssl.certificate: pc1.crt
xpack.security.transport.ssl.certificate_authorities: ca.crt
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.key: pc1.key
xpack.security.http.ssl.certificate: pc1.crt
xpack.security.http.ssl.certificate_authorities: ca.crt


reindex.remote.whitelist: ["*:*"]
reindex.ssl.verification_mode: none

Im Running following in Cluster2:

POST _reindex?pretty
{
"source": {
"remote": {
"host": "https://pc1.com:9200",
"username": "elastic",
"password": "elastic11"
},
"index": "testing"
},
"conflicts": "proceed",
"dest": {
"index": "test1"
}
}

[warkolm (Mark Walkom)]

I can't see how this would work, as you can't run two nodes using the same data paths like that without an error. What do your Elasticsearch logs show?

[Ragul_R]

Hi warkolm,

Its 2 Different cluster.

I found the issue.

Cluster2 is not able to access the Cluster1 along with port, Bcz 9200 port is blocking.

Thank for your Supporting!!!