k8s icon indicating copy to clipboard operation
k8s copied to clipboard

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

Open jwtodd opened this issue 6 years ago • 8 comments

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

jwtodd avatar Nov 22 '19 23:11 jwtodd

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.

wallyqs avatar Nov 23 '19 01:11 wallyqs

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."

shyam-unnithan avatar Dec 19 '19 09:12 shyam-unnithan

I am having the issue;

image

kubectldescribe pod nats0 image

Any idea?

mariogruizdiaz avatar Jun 12 '20 17:06 mariogruizdiaz

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

ruyang-cloudnatix avatar Jan 06 '21 00:01 ruyang-cloudnatix

Same.

greg-md avatar Feb 23 '21 18:02 greg-md

same

MaxThom avatar Apr 23 '21 15:04 MaxThom

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!

eonward avatar Jul 11 '21 14:07 eonward

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.

plaisted avatar Jul 27 '21 02:07 plaisted

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

caleblloyd avatar May 03 '23 17:05 caleblloyd