Unable to start elastic search 2.4 after enabling shield


(Karthik9u) #1

Hi,

When I am starting the elasticsearch after enabling shield SSL, the elastic search fails to start.


[2018-06-13 06:37:27,804][INFO ][node ] [Namor McKenzie] version[2.4.0], pid[5629], build[ce9f0c7/2016-08-29T09:14:17Z]
[2018-06-13 06:37:27,805][INFO ][node ] [Namor McKenzie] initializing ...
[2018-06-13 06:37:28,395][INFO ][plugins ] [Namor McKenzie] modules [reindex, lang-expression, lang-groovy], plugins [license, shield], sites []
[2018-06-13 06:37:28,425][INFO ][env ] [Namor McKenzie] using [1] data paths, mounts [[/ (rootfs)]], net usable_space [60.1gb], net total_space [97.4gb], spins? [unknown], types [rootfs]
[2018-06-13 06:37:28,425][INFO ][env ] [Namor McKenzie] heap size [1007.3mb], compressed ordinary object pointers [true]
[2018-06-13 06:37:28,426][WARN ][env ] [Namor McKenzie] max file descriptors [4096] for elasticsearch process likely too low, consider increasing to at least [65536]
[2018-06-13 06:37:28,835][INFO ][http ] [Namor McKenzie] Using [org.elasticsearch.http.netty.NettyHttpServerTransport] as http transport, overridden by [shield]
[2018-06-13 06:37:28,981][INFO ][transport ] [Namor McKenzie] Using [org.elasticsearch.shield.transport.ShieldServerTransportService] as transport service, overridden by [shield]
[2018-06-13 06:37:28,982][INFO ][transport ] [Namor McKenzie] Using [org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, overridden by [shield]
[2018-06-13 06:37:30,960][INFO ][node ] [Namor McKenzie] initialized
[2018-06-13 06:37:30,960][INFO ][node ] [Namor McKenzie] starting ...
[2018-06-13 06:37:31,267][INFO ][shield.transport ] [Namor McKenzie] publish_address {127.0.0.1:9310}, bound_addresses {127.0.0.1:9310}
[2018-06-13 06:37:31,272][INFO ][discovery ] [Namor McKenzie] elasticsearch/SA2KZWEEQY2F20UOtnDSRw
[2018-06-13 06:37:31,534][ERROR][shield.transport.netty ] [Namor McKenzie] SSL/TLS handshake failed, closing channel: null
[2018-06-13 06:37:34,389][ERROR][shield.transport.netty ] [Namor McKenzie] SSL/TLS handshake failed, closing channel: null
[2018-06-13 06:37:35,876][INFO ][cluster.service ] [Namor McKenzie] new_master {Namor McKenzie}{SA2KZWEEQY2F20UOtnDSRw}{127.0.0.1}{127.0.0.1:9310}, reason: zen-disco-join(elected_as_master, [0] joins received)
[2018-06-13 06:37:35,899][INFO ][shield ] [Namor McKenzie] adding the security index template
[2018-06-13 06:37:35,918][INFO ][http ] [Namor McKenzie] publish_address {127.0.0.1:9210}, bound_addresses {127.0.0.1:9210}
[2018-06-13 06:37:35,918][INFO ][node ] [Namor McKenzie] started
[2018-06-13 06:37:35,928][INFO ][gateway ] [Namor McKenzie] recovered [0] indices into cluster_state
[2018-06-13 06:37:35,940][INFO ][license.plugin.core ] [Namor McKenzie] license [a09088bc-6ee0-4010-a066-9c1c99a6d76d] - valid
[2018-06-13 06:37:35,942][ERROR][license.plugin.core ] [Namor McKenzie]

License will expire on [Friday, July 13, 2018]. If you have a new license, please update it.

Otherwise, please reach out to your support contact.

Commercial plugins operate with reduced functionality on license expiration:

- shield

- Cluster health, cluster stats and indices stats operations are blocked

- All data operations (read and write) continue to work

[2018-06-13 06:38:11,779][INFO ][node ] [Namor McKenzie] stopping ...
[2018-06-13 06:38:11,787][INFO ][node ] [Namor McKenzie] stopped
[2018-06-13 06:38:11,788][INFO ][node ] [Namor McKenzie] closing ...
[2018-06-13 06:38:11,795][INFO ][node ] [Namor McKenzie] closed

The error, "[ERROR][shield.transport.netty ] [Namor McKenzie] SSL/TLS handshake failed, closing channel: null" is very generic. I am not able to isolate the issue with this error.

Any help is appreciated.

Thanks,
Karthick


(Mark Walkom) #2

2.4 has reached EOL, is there any reason you are still using it?


(Karthik9u) #3

Hi Warkolm,

Thank you for the quick response.

This is an issue observed for one of my clients. Elastic search is integrated with Talend platform. The latest versions of Talend has the supported version of Elastic Search. However, in this use case, my client is using a older version of Talend.

We should use Elastic Search for some more time. Can you please provide some inputs to debug this issue ?

Thanks,
Karthick


(system) #4

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