Issue with Jaeger V2 deployment with cassandra TLS enabled #7130

Sidhartha-Biswal · 2025-05-16T05:14:51Z

Sidhartha-Biswal
8000 May 16, 2025

Hi,

We are working on Jaeger V1 to V2 Migration, as part of this trying to deploy jaeger with backend as cassandra(with TLS) with below exporter configuration, but the deployment is failing with below error, without TLS deployment works fine.

is Cassandra with TLS support is there in V2? if yes please help us with how to configure.

https://github.com/jaegertracing/jaeger/blob/main/cmd/jaeger/config-cassandra.yaml

From the above link configuration given for no TLS case, TLS case how to pass certificates configuration is missing and did not find this information in below cassandra V1 to V2 migration guide also.

https://docs.google.com/document/d/16M50j-ATIGb0AgKQBz-719XzJNwJWoouNTs7_N3fKfY/edit?tab=t.0#heading=h.qbckwiyz30oe

jaeger_storage:

    backends:

      another_storage:

        cassandra:

          schema:

            keyspace: "jaeger_v1_datacenter1"

            create: true

          connection:

            local_dc: "datacenter1"

            servers: cassandra:9042

            port: 9042

            auth:

              basic:

                username: ""

                password: ""

            tls:

              cert_file: /path/client/tls.crt

              key_file: /path/client/tls.key

              ca_file: /path/root-cert/ca.crt

              cipher_suites:

              min_version: "1.2"

              max_version: "1.3"

exporters:

  jaeger_storage_exporter:

    trace_storage: another_storage

We are getting the below error we are getting with this configuration.

2025-05-16T05:26:51.355Z info extensions/extensions.go:41 Starting extensions...

2025-05-16T05:26:51.355Z info extensions/extensions.go:45 Extension is starting...

2025-05-16T05:26:51.355Z info jaegerstorage/extension.go:159 Initializing storage 'another_storage'

2025/05/16 05:26:54 error: failed to connect to "[HostInfo hostname="192.168.x.x" connectAddress="192.168.x.x" peer="" rpc_address="192.168.x.x" broadcast_address="192.168.x.x" preferred_ip="" connect_addr="192.168.x.x" connect_addr_source="connect_address" port=9042 data_centre="datacenter1" rack="rack1" host_id="bd3436-ab35-450e-893" version="v4.1.0" state=UP num_tokens=16]" due to error: tls: failed to verify certificate: x509: cannot validate certificate for 192.168.x.x because it doesn't contain any IP SANs

2025-05-16T05:26:54.499Z error extensions/extensions.go:58 Failed to start extension {"error": "failed to initialize storage 'another_storage': no connections were made when creating the session"}

@dosu · 2025-05-16T05:27:04Z

dosubot[bot]
bot May 16, 2025

Yes, Cassandra with TLS support is available in Jaeger V2. To configure it correctly for deployment, you need to specify paths to the TLS certificates (.pem files) in the tls: section under connection:. You can refer to the configtls.ClientConfig in the OpenTelemetry Collector repository for available properties. Additionally, you can create a custom cqlshrc file for the schema tool to support TLS. Here is an example configuration for the cqlshrc file:

[ssl]
certfile = ~/.cassandra/ca-cert
userkey = ~/.cassandra/client-key
usercert = ~/.cassandra/client-cert
# validate = false

For the collector and query components, you can use the following environment variables to enable TLS:

docker run \
  -e CASSANDRA_SERVERS=<...> \
  -e CASSANDRA_TLS=true \
  -e CASSANDRA_TLS_SERVER_NAME="CN-in-certificate" \
  -e CASSANDRA_TLS_KEY=<path to client key file> \
  -e CASSANDRA_TLS_CERT=<path to client cert file> \
  -e CASSANDRA_TLS_CA=<path to your CA cert file> \
  jaegertracing/jaeger-collector:{{< currentVersion >}}

Ensure that you verify the correctness of your TLS certificates using cqlsh first. Jaeger can automatically create the schema on start-up with the appropriate configuration, or you can manually initialize it using the provided script in the Jaeger repository. For production deployment, pass MODE=prod DATACENTER={datacenter} arguments to the script, where {datacenter} is the name used in the Cassandra configuration/network topology. The script also allows overriding TTL, keyspace name, replication factor, etc. Run the script without arguments to see the full list of recognized parameters. See this README for more details on Cassandra schema management ^[1]^[2]^[3]^[4].

To continue talking to Dosu, mention @dosu.

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

1 reply

Sidhartha-Biswal Jun 25, 2025
Author

Hi @yurishkuro, the issue still present can you help in fixing this issue

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Jaeger - Distributed Tracing Platform

Issue with Jaeger V2 deployment with cassandra TLS enabled #7130

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Jaeger - Distributed Tracing Platform

Issue with Jaeger V2 deployment with cassandra TLS enabled #7130

Uh oh!

Uh oh!

Sidhartha-Biswal 8000 May 16, 2025

Replies: 1 comment · 1 reply

Uh oh!

dosubot[bot] bot May 16, 2025

Uh oh!

Sidhartha-Biswal Jun 25, 2025 Author

Sidhartha-Biswal
8000 May 16, 2025

Replies: 1 comment 1 reply

dosubot[bot]
bot May 16, 2025

Sidhartha-Biswal Jun 25, 2025
Author