Cannot run dsetool status on k8s cluster running on Ubuntu 20.04

Question

question

francisdomoney@aol.com asked Jul 30, '20 francisdomoney@aol.com commented Aug 3, '20

Cannot run dsetool status on k8s cluster running on Ubuntu 20.04

I have two issues I have encountered trying to run Logs and dsetool

kubectl -n cass-operator exec -it cluster2-dc2-default-sts-0 -- /bin/bash
Defaulting container name to cassandra.
Use 'kubectl describe pod/cluster2-dc2-default-sts-0 -n cass-operator' to see all of the containers in this pod.
dse@cluster2-dc2-default-sts-0:~$ dsetool status
Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)

Any ideas. I have faithfully followed the README.md and the cluster is running

[UPDATE] Thanks. I am at the same point again. I have attached two screenshots

workshop cass-operator

screenshot-from-2020-07-31-19-20-40.png (35.7 KiB)

screenshot-from-2020-07-31-19-36-59.png (112.5 KiB)

1

10 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

francisdomoney@aol.com commented · Jul 31, 2020 at 06:42 PM

[Re-posted comments in original question since this is not an "answer"]

0 ·

screenshot-from-2020-07-31-19-36-59.png (290.4 KiB)

screenshot-from-2020-07-31-19-20-40.png (252.2 KiB)

DataStax Enterprise is powered by the best distribution of Apache Cassandra ™

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.

Privacy Policy Terms of Use

Answer 1 · 2020-07-31T11:21:33Z

Cedrick Lunven answered Jul 31, '20 francisdomoney@aol.com commented Jul 31, '20

Hi,

Looking at the logs are here It feels that the cluster is still initializing, As the Cassandra is not started yet the internal cqlsh command cannot reach any service. You need to wait until the pod move to state READY and RUNNING.

1 Share

10 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

francisdomoney@aol.com commented · Jul 31, 2020 at 06:55 PM

here is another screenshot of the machine state

0 ·

screenshot-from-2020-07-31-19-52-22.png (335.5 KiB)

Answer 2 · 2020-08-01T01:28:07Z

jim.dickinson_187342 answered Aug 1, '20 francisdomoney@aol.com commented Aug 1, '20

Since you're seeing a number of containers restarting, I would bet that you're running out of memory.

1 Share

10 |1000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

francisdomoney@aol.com commented · Aug 01, 2020 at 07:07 AM

Thanks Jim. I will try again once more this morning. I think I am identifying the limits of what I can run on a fairly well provisioned Ubuntu desktop machine. This valuable information. If Kubernetes drives me onto cloud I will needto think through the issues associated with this for use in a pan African context. There are cost, cybersecurity and geopolitical issues.

0 ·

question