Error: failed to start extensions: failed to initialize storage 'elastic_storage': failed to create primary Elasticsearch client: health check timeout: no Elasticsearch node available

[yogesh119905]

Hello, I have prepared jaeger 2.2.0 single docker container. In docker compose I have mentioned below things. please refer the attached screen shot

After using this configuration jaeger node is able to connect elastic search storage with http.
In case for https jaeger is unable to connect elastic search node. we have checked on jaeger node to elastic search node that prompting authentication to connect elastic search storage. Please refer below screenshot.

Now I am getting an error for elastic search node not available.

Anyone can help me to fix this issue?

[dosubot[bot]]

To resolve the issue of Jaeger 2.2.0 failing to connect to an Elasticsearch node over HTTPS due to a health check timeout and authentication errors, ensure the following configurations are correctly set:

1. TLS Configuration: Verify that the TLS settings are correctly configured. Ensure that the TLS configuration in your setup is properly set up, including the paths to the CA, certificate, and key files. Also, make sure ES_TLS_ENABLED is set to true.

2. Authentication: Check that the authentication details are correct. If using basic authentication, ensure that both ES_USERNAME and ES_PASSWORD are correctly set in your environment variables.

3. Sniffing and HTTPS: If sniffing is enabled, ensure that UseHTTPS is set to true to use HTTPS for sniffing.

4. Health Check: If you are using bearer token authentication and allowing tokens from context, ensure that health checks are disabled as they might not have a valid token at the time of the check.

5. Timeouts: Check the QueryTimeout setting to ensure it is not set too low, which could cause timeouts during health checks or other operations.

Additionally, you might find these similar threads helpful:

• Jaeger Deployment issue with Elasticsearch Backend ^[1]
• Problems connecting Jaeger query with OpenSearch ^[2]
• Unable to connect Elasticsearch from docker image 'jaegertracing/all-in-one:1.36' ^[3]

These discussions might provide additional insights or solutions that could be applicable to your situation.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[yogesh119905]

@dosu, As per provided by you, I have double cheked all point still it not working. Error: failed to start extensions: failed to initialize storage 'elastic_storage': failed to create primary Elasticsearch client: health check timeout: no Elasticsearch node available
2025/02/06 08:36:35 failed to start extensions: failed to initialize storage 'elastic_storage': failed to create primary Elasticsearch client: health check timeout: no Elasticsearch node available
root@virttracing1:~#

[dosubot[bot]]

To address the "no Elasticsearch node available" error when using HTTPS, consider the following steps:

1. Verify Elasticsearch URL: Ensure that the ES_SERVER_URLS environment variable or configuration setting points to the correct HTTPS URL of your Elasticsearch cluster.

2. TLS Configuration: Double-check that the TLS settings are correctly configured. Ensure that the paths to the CA, certificate, and key files are correct and accessible by the Jaeger container. Also, confirm that ES_TLS_ENABLED is set to true.

3. Authentication: Make sure that the authentication credentials (username and password) are correctly set in the environment variables or configuration file. If using a bearer token, ensure the token file path is correct.

4. Sniffing: If sniffing is enabled, ensure that ES_SNIFFER_TLS_ENABLED is set to true to use HTTPS for node discovery.

5. Firewall and Network: Check if there are any firewall rules or network policies that might be blocking the connection to the Elasticsearch nodes over HTTPS.

6. Elasticsearch Logs: Review the Elasticsearch logs for any errors or warnings that might indicate why the connection is failing.

7. Jaeger Logs: Increase the log level for the Elasticsearch client in Jaeger to get more detailed logs, which might provide additional insights into the issue:

   es.log-level: "debug"

These steps should help in diagnosing and resolving the connectivity issue with Elasticsearch over HTTPS.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}