Hi, i have deployed a new k8ssandra cluster in GKE and the server-system-logger fails with Readiness probe failed: HTTP probe failed with statuscode: 500
cassandra container logs
INFO [nioEventLoopGroup-3-9] 2023-03-09 05:31:42,864 UnixSocketCQLAccess.java:88 - Cannot create Driver CQLSession as the driver socket has not been created. This should resolve once Cassandra has started and created the socket at /tmp/cassandra.sock
INFO [nioEventLoopGroup-2-2] 2023-03-09 05:31:42,864 Cli.java:617 - address=/10.200.1.174:53888 url=/api/v0/metadata/endpoints status=500 Internal Server Error
INFO [nioEventLoopGroup-3-10] 2023-03-09 05:31:43,147 UnixSocketCQLAccess.java:88 - Cannot create Driver CQLSession as the driver socket has not been created. This should resolve once Cassandra has started and created the socket at /tmp/cassandra.sock
INFO [nioEventLoopGroup-2-2] 2023-03-09 05:31:43,148 Cli.java:617 - address=/10.175.0.74:40282 url=/api/v0/probes/liveness status=200 OK
INFO [nioEventLoopGroup-2-1] 2023-03-09 05:31:43,148 Cli.java:617 - address=/10.175.0.74:40266 url=/api/v0/probes/readiness status=500 Internal Server Error
INFO [nioEventLoopGroup-3-12] 2023-03-09 05:31:44,887 UnixSocketCQLAccess.java:88 - Cannot create Driver CQLSession as the driver socket has not been created. This should resolve once Cassandra has started and created the socket at /tmp/cassandra.sock
INFO [nioEventLoopGroup-2-1] 2023-03-09 05:31:44,888 Cli.java:617 - address=/10.200.1.174:35030 url=/api/v0/metadata/endpoints status=500 Internal Server Erro
when I have checked the logs of server-system-logger , it says tail: cannot open ‘/var/log/cassandra/system.log’ for reading: No such file or directory
I understand from the above message that Cassandra hasn’t started and server log have not initialized but I do not understand why cassandra would not start.
My config
cassandra:
podSecurityContext:
runAsNonRoot: true
runAsUser: 999
runAsGroup: 999
fsGroup: 999
image:
registry:
clusterName: cassandra
cassandraLibDirVolume:
# StorageClass is determined automatically by cloud provider, and it’s region
# also, required StorageClass object is created
# storageClass: standard
size: 5Gi
allowMultipleNodesPerWorker: true
heap:
size: 2G
newGenSize: 2G
resources:
requests:
cpu: 2
memory: 4Gi
limits:
cpu: 2
memory: 4Gi
ingress:
enabled: true
port: 9042
datacenters:
- name: dc1
size: 3
racks:
- name: rack1
affinityLabels:
topology.kubernetes.io/zone: us-east4-a
spot: “false”
- name: rack2
affinityLabels:
topology.kubernetes.io/zone: us-east4-b
spot: “false”
- name: rack3
affinityLabels:
topology.kubernetes.io/zone: us-east4-c
spot: “false”