Unable to check whether cluster is sane: None of the configured nodes are available

Search Guard
1

When asking questions, please provide the following information:

  • Search Guard search-guard-6-6.3.0-22.3 and Elasticsearch version 6.3

  • Installed and used enterprise modules, if any

  • JVM version 1.8.0

  • Search Guard configuration files

  • Elasticsearch log messages on debug level

  • Other installed Elasticsearch or Kibana plugins, if any

sudo “/usr/share/elasticsearch/plugins/search-guard-6/tools/sgadmin.sh” -icl -h 192.168.0.117 -p 9200 -cd “/usr/share/elasticsearch/plugins/search-guard-6/sgconfig” -icl -key “/etc/elasticsearch/kirk-key.pem” -cert “/etc/elasticsearch/kirk.pem” -cacert “/etc/elasticsearch/root-ca.pem” -nhnv

what happened???

elasticsearch[client][transport_client_boss][T#1], called closeOutbound()

elasticsearch[client][transport_client_boss][T#1], closeOutboundInternal()

elasticsearch[client][transport_client_boss][T#1], SEND TLSv1.2 ALERT: warning, description = close_notify

elasticsearch[client][transport_client_boss][T#1], WRITE: TLSv1.2 Alert, length = 2

elasticsearch[client][transport_client_boss][T#1], called closeInbound()

elasticsearch[client][transport_client_boss][T#1], fatal error: 80: Inbound closed before receiving peer’s close_notify: possible truncation attack?

javax.net.ssl.SSLException: Inbound closed before receiving peer’s close_notify: possible truncation attack?

elasticsearch[client][transport_client_boss][T#1], SEND TLSv1.2 ALERT: fatal, description = internal_error

elasticsearch[client][transport_client_boss][T#1], Exception sending alert: java.io.IOException: writer side was already closed.

Unable to check whether cluster is sane: None of the configured nodes are available: [{#transport#-1}{JTMd66anRjaFdqDpu5RFuw}{192.168.0.117}{192.168.0.117:9200}]

elasticsearch[client][transport_client_boss][T#1], called closeOutbound()

elasticsearch[client][transport_client_boss][T#1], closeOutboundInternal()

elasticsearch[client][transport_client_boss][T#1], called closeInbound()

elasticsearch[client][transport_client_boss][T#1], closeInboundInternal()

ERR: Cannot connect to Elasticsearch. Please refer to elasticsearch logfile for more information

Trace:

NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{JTMd66anRjaFdqDpu5RFuw}{192.168.0.117}{192.168.0.117:9200}]]

at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:347)

at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:245)

at org.elasticsearch.client.transport.TransportProxyClient.execute(TransportProxyClient.java:60)

at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:378)

at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:405)

at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:394)

at com.floragunn.searchguard.tools.SearchGuardAdmin.main0(SearchGuardAdmin.java:451)

at com.floragunn.searchguard.tools.SearchGuardAdmin.main(SearchGuardAdmin.java:124)

2

sgadmin works on the transport port, not the HTTP port of Elasticsearch. If you’re running on standard ports, just remove:

-p 9200

``

from your call. Standard ports are 9200 for HTTP, and 9300 for transport.

···

On Wednesday, July 25, 2018 at 3:15:59 AM UTC+2, flower k wrote:

When asking questions, please provide the following information:

  • Search Guard search-guard-6-6.3.0-22.3 and Elasticsearch version 6.3
  • Installed and used enterprise modules, if any
  • JVM version 1.8.0
  • Search Guard configuration files
  • Elasticsearch log messages on debug level
  • Other installed Elasticsearch or Kibana plugins, if any

sudo “/usr/share/elasticsearch/plugins/search-guard-6/tools/sgadmin.sh” -icl -h 192.168.0.117 -p 9200 -cd “/usr/share/elasticsearch/plugins/search-guard-6/sgconfig” -icl -key “/etc/elasticsearch/kirk-key.pem” -cert “/etc/elasticsearch/kirk.pem” -cacert “/etc/elasticsearch/root-ca.pem” -nhnv

what happened???

elasticsearch[client][transport_client_boss][T#1], called closeOutbound()

elasticsearch[client][transport_client_boss][T#1], closeOutboundInternal()

elasticsearch[client][transport_client_boss][T#1], SEND TLSv1.2 ALERT: warning, description = close_notify

elasticsearch[client][transport_client_boss][T#1], WRITE: TLSv1.2 Alert, length = 2

elasticsearch[client][transport_client_boss][T#1], called closeInbound()

elasticsearch[client][transport_client_boss][T#1], fatal error: 80: Inbound closed before receiving peer’s close_notify: possible truncation attack?

javax.net.ssl.SSLException: Inbound closed before receiving peer’s close_notify: possible truncation attack?

elasticsearch[client][transport_client_boss][T#1], SEND TLSv1.2 ALERT: fatal, description = internal_error

elasticsearch[client][transport_client_boss][T#1], Exception sending alert: java.io.IOException: writer side was already closed.

Unable to check whether cluster is sane: None of the configured nodes are available: [{#transport#-1}{JTMd66anRjaFdqDpu5RFuw}{192.168.0.117}{192.168.0.117:9200}]

elasticsearch[client][transport_client_boss][T#1], called closeOutbound()

elasticsearch[client][transport_client_boss][T#1], closeOutboundInternal()

elasticsearch[client][transport_client_boss][T#1], called closeInbound()

elasticsearch[client][transport_client_boss][T#1], closeInboundInternal()

ERR: Cannot connect to Elasticsearch. Please refer to elasticsearch logfile for more information

Trace:

NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{JTMd66anRjaFdqDpu5RFuw}{192.168.0.117}{192.168.0.117:9200}]]

at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:347)

at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:245)

at org.elasticsearch.client.transport.TransportProxyClient.execute(TransportProxyClient.java:60)

at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:378)

at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:405)

at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:394)

at com.floragunn.searchguard.tools.SearchGuardAdmin.main0(SearchGuardAdmin.java:451)

at com.floragunn.searchguard.tools.SearchGuardAdmin.main(SearchGuardAdmin.java:124)

3

thank you Jochen Kressin~~~!

2018년 7월 27일 금요일 오전 3시 20분 56초 UTC+9, Jochen Kressin 님의 말:

···

sgadmin works on the transport port, not the HTTP port of Elasticsearch. If you’re running on standard ports, just remove:

-p 9200

``

from your call. Standard ports are 9200 for HTTP, and 9300 for transport.

On Wednesday, July 25, 2018 at 3:15:59 AM UTC+2, flower k wrote:

When asking questions, please provide the following information:

  • Search Guard search-guard-6-6.3.0-22.3 and Elasticsearch version 6.3
  • Installed and used enterprise modules, if any
  • JVM version 1.8.0
  • Search Guard configuration files
  • Elasticsearch log messages on debug level
  • Other installed Elasticsearch or Kibana plugins, if any

sudo “/usr/share/elasticsearch/plugins/search-guard-6/tools/sgadmin.sh” -icl -h 192.168.0.117 -p 9200 -cd “/usr/share/elasticsearch/plugins/search-guard-6/sgconfig” -icl -key “/etc/elasticsearch/kirk-key.pem” -cert “/etc/elasticsearch/kirk.pem” -cacert “/etc/elasticsearch/root-ca.pem” -nhnv

what happened???

elasticsearch[client][transport_client_boss][T#1], called closeOutbound()

elasticsearch[client][transport_client_boss][T#1], closeOutboundInternal()

elasticsearch[client][transport_client_boss][T#1], SEND TLSv1.2 ALERT: warning, description = close_notify

elasticsearch[client][transport_client_boss][T#1], WRITE: TLSv1.2 Alert, length = 2

elasticsearch[client][transport_client_boss][T#1], called closeInbound()

elasticsearch[client][transport_client_boss][T#1], fatal error: 80: Inbound closed before receiving peer’s close_notify: possible truncation attack?

javax.net.ssl.SSLException: Inbound closed before receiving peer’s close_notify: possible truncation attack?

elasticsearch[client][transport_client_boss][T#1], SEND TLSv1.2 ALERT: fatal, description = internal_error

elasticsearch[client][transport_client_boss][T#1], Exception sending alert: java.io.IOException: writer side was already closed.

Unable to check whether cluster is sane: None of the configured nodes are available: [{#transport#-1}{JTMd66anRjaFdqDpu5RFuw}{192.168.0.117}{192.168.0.117:9200}]

elasticsearch[client][transport_client_boss][T#1], called closeOutbound()

elasticsearch[client][transport_client_boss][T#1], closeOutboundInternal()

elasticsearch[client][transport_client_boss][T#1], called closeInbound()

elasticsearch[client][transport_client_boss][T#1], closeInboundInternal()

ERR: Cannot connect to Elasticsearch. Please refer to elasticsearch logfile for more information

Trace:

NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{JTMd66anRjaFdqDpu5RFuw}{192.168.0.117}{192.168.0.117:9200}]]

at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:347)

at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:245)

at org.elasticsearch.client.transport.TransportProxyClient.execute(TransportProxyClient.java:60)

at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:378)

at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:405)

at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:394)

at com.floragunn.searchguard.tools.SearchGuardAdmin.main0(SearchGuardAdmin.java:451)

at com.floragunn.searchguard.tools.SearchGuardAdmin.main(SearchGuardAdmin.java:124)