Build Cloud-Native apps with Apache Cassandra

GOT QUESTIONS from the Workshop? You're in the right place! Post a question here and we'll get you answers.

Click here for Week 8 Materials and Homework.

Follow us on Eventbrite to get notified when new workshops are scheduled!

question

krishnamohan100_189669 avatar image
krishnamohan100_189669 asked Erick Ramirez commented

The connection to the server 127.0.0.1:45451 was refused - did you specify the right host or port?

Hi Team

I am using the cloud instance to execute the week 6 homework.

I am getting the following error "The connection to the server 127.0.0.1:45451 was refused - did you specify the right host or port?"

after I execute the command

~/kubernetes-workshop-online/week6-App-in-k8s/kubefiles> kubectl cluster-info --context kind-kind-cassandra

How do I resolve this issue?

workshop
10 |1000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

1 Answer

bettina.swynnerton avatar image
bettina.swynnerton answered Erick Ramirez commented

Hi @krishnamohan100_189669,

I have not seen this issue myself, but I have had a couple of other users report this issue, and in those cases, deleting the kind cluster and recreating it solved the issue.

Would you try this?

To delete the kind cluster:

kind delete cluster --name kind-cassandra

To recreate the kind cluster:

kind create cluster --name kind-cassandra --config 01-kind-config.yaml

I hope this resolves this particular issue.

1 comment Share
10 |1000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

krishnamohan100_189669 avatar image krishnamohan100_189669 ·

Thank you Bettina. This helped resolve the above mentioned issue.

Actually this issue happens after we execute the command docker stop <containerid> mentioned in step 4b. I then retried the Steps 1 to 6 again without executing the docker stop command and was able to move forward.

[Follow up question posted in #7601]

0 Likes 0 ·