Hi community,
I’ve three node Cassandra Cluster and Dataminer can reach 2 of them without issues.
I can reach all 3 nodes via DataStax Devcenter, cqlsh and nodetool (from DMA and Linux nodes).
The “Apache Cassandra Cluster Monitor” driver also works fine.
But the Cassandra cluster health is always yellow in the alarm console:
“Cassandra cluster health is yellow. DataMiner is still fully functional. 1 out of 3 Cassandra nodes are unavailable: 192.168.2.163:9042.”
In the SLDBConnection log there is a message every minute:
2024/05/03 10:19:06.930|SLDBConnection|.ctor|INF|0|147|RemoteCertificateNameMismatch detected. Manually checking if the Cassandra Host(s) “192.168.2.162,192.168.2.163,192.168.2.164” match the SAN of the certificate for cassandra-02.
2024/05/03 10:19:06.931|SLDBConnection|.ctor|INF|0|147|Found SAN: IP-Adresse=192.168.2.163
2024/05/03 10:19:06.931|SLDBConnection|.ctor|INF|0|147|Filtered SAN: IP-Adresse=192.168.2.163
2024/05/03 10:19:06.931|SLDBConnection|.ctor|INF|0|147|No contactpoint is part of the SAN. Continuing normal validation.
But if I look into the certificate it looks similar to the other nodes and the correct SAN is specified:
#2: ObjectId: 2.5.29.17 Criticality=false
SubjectAlternativeName [
IPAddress: 192.168.2.163
]
What else can I do to find the root cause of this issue?
Hi Seppe,
It was a good idea to take a wireshark capture.
There is an old SNI in the Client Hello of Dataminer to the non working node.
Looks like a bug of our DNS server.
Have a nice weekend!
Hi Felix,
I get the impression that this question has already been answered in the comments. If this is indeed the case, could you select this answer to indicate that the question can be closed?
Hi Felix,
I would suggest to take a wireshark trace on the DataMiner agent in order to debug this issue.