Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1092
There's also a generic ES message that you'll see when the client can't
connect to the ES hosts, e.g.
```
"None of the configured nodes are available:
[{#transport#-1}{MUuqzLIvSqSvt_TH6heDoQ}{some.host.namel}{123.44.55.678:9300}]"
```
This can come from any and all of the following:
1. ES not configured with X-Pack
2. Client not configured with X-Pack
3. Wrong host/ip for connecting to ES master
4. Permissions issue with cert, username, password for X-Pack
5. Wrong TransportClient being used with X-Pack (i.e. if you did NOT
correctly specify org.elasticsearch.xpack.client.PreBuiltXPackTransportClient)
5. ES client is intimidated by ElasticsearchUtils.
There are others as well that I would need to spend a bit of time hunting
down and consolidating. They're things that are probably more obvious, however.
E.g. unable to read a cert.
---
