Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nats-0 CLBackoff, nats-surveyor CLB, stan-1 pending #9

Closed
jwtodd opened this issue Nov 22, 2019 · 9 comments · May be fixed by nats-io/nats-operator#322
Closed

nats-0 CLBackoff, nats-surveyor CLB, stan-1 pending #9

jwtodd opened this issue Nov 22, 2019 · 9 comments · May be fixed by nats-io/nats-operator#322

Comments

@jwtodd
Copy link

jwtodd commented Nov 22, 2019 •
edited

firstly, thx for the one-liner install :]

env: osx, docker-desktop/kubernetes latest, reset

test: % curl -sSL https://nats-io.github.io/k8s/setup.sh | sh

pods:

jwtodd> kubectl get pods
NAME                                     READY   STATUS                  RESTARTS   AGE
nats-0                                   0/3     Init:CrashLoopBackOff   5          5m38s
nats-box                                 1/1     Running                 0          5m39s
nats-setup                               0/1     Completed               0          6m9s
nats-surveyor-68fc4bbcc8-8bttt           0/1     CrashLoopBackOff        5          5m33s
nats-surveyor-grafana-55fb5584b6-vjf4f   1/1     Running                 0          5m34s
prometheus-nats-prometheus-0             3/3     Running                 1          5m25s
prometheus-nats-surveyor-0               3/3     Running                 1          5m25s
prometheus-operator-6d899fc8dd-47d78     1/1     Running                 0          5m37s
stan-0                                   2/2     Running                 1          5m38s
stan-1                                   0/2     Pending                 0          5m33s

logs:

jwtodd> kubectl logs nats-0
Error from server (BadRequest): a container name must be specified for pod nats-0, choose one of: [nats reloader metrics] or one of the init containers: [bootconfig]
jwtodd> kubectl logs nats-surveyor-68fc4bbcc8-8bttt
+ cp /etc/nats/certs/ca.crt /usr/local/share/ca-certificates
+ ls -al /usr/local/share/ca-certificates
total 12
drwxr-xr-x    1 root     root          4096 Nov 22 23:19 .
drwxr-xr-x    1 root     root          4096 Jul 18 16:53 ..
-rw-r--r--    1 root     root          1115 Nov 22 23:19 ca.crt
+ update-ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping
+ /nats-surveyor '-s=tls://nats:4222' '-c=3' '-creds=/var/run/nats/creds/sys/sys.creds' '-observe=/etc/nats/observations/'
2019/11/22 23:19:26 couldn't start surveyor: nats: no servers available for connection
jwtodd> kubectl logs stan-1
Error from server (BadRequest): a container name must be specified for pod stan-1, choose one of: [stan metrics]

ask: is there a means to cleanup the install? to get it teardown i opted for a dd/k8s reset
@wallyqs
Copy link
Member

wallyqs commented Nov 23, 2019

Thanks for the bug report, I’ll take a look at making it work in docker desktop. Also there is a destroy.sh script in the repo that can cleanup the install.

@shyam-unnithan
Copy link

Thanks for the installer :). I am also facing similar issue. Running the installer on minikube. Here are the logs. Hope it helps
kubectl logs nats-0 bootconfig
time="2019-12-19T09:15:21Z" level=info msg="Starting NATS Server boot config v0.5.2"
time="2019-12-19T09:15:21Z" level=info msg="Pod running on node "minikube""
time="2019-12-19T09:15:21Z" level=fatal msg="Could not find external IP address."

@mariogruizdiaz
Copy link

I am having the issue;

image

kubectldescribe pod nats0
image

Any idea?

@ruyang-cloudnatix
Copy link

I'm facing the same issue in the setup.sh script. Any updates on a fix?

@greg-md
Copy link

greg-md commented Feb 23, 2021

Same.

@MaxThom
Copy link

MaxThom commented Apr 23, 2021

same

@ZleFox ZleFox mentioned this issue Jun 9, 2021
Open
@eonward
Copy link
Contributor

eonward commented Jul 11, 2021

image

😓
Does anyone know how to set up an external IP on docker desktop?
I can't run minikube on this machine. Just trying to get around this issue temporarily

Thank you @ZleFox for the fix!

@plaisted
Copy link

plaisted commented Jul 27, 2021 •
edited

Scraping through the operator source led me to this solution if your setup is failing due to no external IP address set on the node:

kubectl label node my-node-wsl nats.io/node-external-ip=192.168.100.100

where my-node-wsl is your node name and 192.168.100.100 is your external ip.

@caleblloyd
Copy link
Collaborator

I don't think this is an issue anymore in recent versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add InternalIP fallback if no external is found ZleFox/nats-operator
10 participants
@wallyqs @jwtodd @caleblloyd @greg-md @plaisted @shyam-unnithan @mariogruizdiaz @MaxThom @eonward @ruyang-cloudnatix