[Airship-discuss] Airship in a Bottle - CrashLoopBackOff

JAYARAJ, BEN bj2343 at att.com
Thu Sep 10 19:39:58 UTC 2020


Matt,

I have seen the same error shown below (CrashLoopBackOff) yesterday when I was trying the deploy.

Today we tried the deploy with your suggestions - we got the error shown below at the end of install.

Just a thought -  Should we have run swapoff -a before the script begins. (WARNING: No swap limit – in the error message below)

Thanks

Ben


0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>Thu Sep 10 13:25:35 CDT 2020 API not returning node list before timeout.<br>Thu Sep 10 13:25:35 CDT 2020 General docker state report<br>Containers: 0<br> Running: 0<br> Paused: 0<br> Stopped: 0<br>Images: 3<br>Server Version: 18.06.3-ce<br>Storage Driver: overlay2<br> Backing Filesystem: extfs<br> Supports d_type: true<br> Native Overlay Diff: true<br>Logging Driver: json-file<br>Cgroup Driver: cgroupfs<br>Plugins:<br> Volume: local<br> Network: bridge host macvlan null overlay<br> Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog<br>Swarm: inactive<br>Runtimes: runc<br>Default Runtime: runc<br>Init Binary: docker-init<br>containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e<br>runc version: a592beb5bc4c4092b1b1bac971afed27687340c5<br>init version: fec3683<br>Security Options:<br> apparmor<br> seccomp<br> Profile: default<br>Kernel Version: 4.4.0-186-generic<br>Operating System: Ubuntu 16.04.7 LTS<br>OSType: linux<br>Architecture: x86_64<br>CPUs: 16<br>Total Memory: 31.42GiB<br>Name: tma-airship<br>ID: 4MOE:NJSF:L37S:ACYI:DNPJ:77BR:IFFL:L77C:6JXB:ZYEE:SVC2:2DUO<br>Docker Root Dir: var/lib/docker<br>Debug Mode (client): false<br>Debug Mode (server): false<br>Registry: https://index.docker.io/v1<br>Labels:<br>Experimental<https://index.docker.io/v1%3cbr%3eLabels:%3cbr%3eExperimental>: false<br>Insecure Registries:<br> 127.0.0.0/8<br>Live Restore Enabled: true<br><br>WARNING: No swap limit support<br>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES<br>Thu Sep 10 13:25:35 CDT 2020 General cluster state report<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>+ error 'running genesis'<br>+ set +x<br>Error when running genesis.<br>+ exit 1<br>+ clean<br>+ set +x<br>To remove files generated during this script's execution, delete /root/deploy/treasuremap/../.<br>This VM is disposable. Re-deployment in this same VM will lead to unpredictable results.<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port?<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port?

Thanks
Ben

From: MCEUEN, MATT <MM9745 at att.com>
Sent: Wednesday, September 9, 2020 7:02 PM
To: Matthew Hooker <mjhooker at gmail.com>
Cc: BOSE, ARIJIT <ab7180 at att.com>; airship-discuss at lists.airshipit.org; JAYARAJ, BEN <bj2343 at att.com>
Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff

Hi Matthew,

We are able to reproduce the issue, and have a fix that should be merged in the next couple hours.  Can you please give it another try and see if you still have any issues?

Sorry for the inconvenience!
Matt

From: Matthew Hooker <mjhooker at gmail.com<mailto:mjhooker at gmail.com>>
Sent: Saturday, September 5, 2020 3:07 PM
To: airship-discuss at lists.airshipit.org<mailto:airship-discuss at lists.airshipit.org>
Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff


Hi,



I've tried getting AiaB working several times on various machines but always end up with this:





NAMESPACE     NAME                                   READY   STATUS             RESTARTS   AGE

kube-system   auxiliary-etcd-ubuntu                  3/3     Running            0          13h

kube-system   bootstrap-armada-ubuntu                4/4     Running            0          13h

kube-system   haproxy-ubuntu                         1/1     Running            0          13h

kube-system   kubernetes-apiserver-ubuntu            1/1     Running            1          13h

kube-system   kubernetes-controller-manager-ubuntu   1/1     Running            0          13h

kube-system   kubernetes-etcd-ubuntu                 1/1     Running            0          13h

kube-system   kubernetes-proxy-f279z                 0/1     Pending            0          2m32s

kube-system   kubernetes-scheduler-ubuntu            0/1     CrashLoopBackOff   167        13h



This may be easily solvable by someone with sufficient knowledge of the underlying systems but I'm stuck.

Full transcript here:



https://drive.google.com/file/d/10l1hrtRNEMA0OYujk2V9sRILazQ2wZeq/view<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_file_d_10l1hrtRNEMA0OYujk2V9sRILazQ2wZeq_view&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=RwVrX3OKWt8Yk0QYzlry0M-8EFvbguDaOkjDdqCBVjA&m=PgVPvNs6YK_9oDpvL7NEaetCQuiGXjSZPoVl0d_RUCk&s=why6aXiC3z7cLO2XvFQA581oGKUzUno2yoqUUDSQLyU&e=>



Any help appreciated



Matthew


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.airshipit.org/pipermail/airship-discuss/attachments/20200910/d9ed9ff2/attachment-0001.html>


More information about the Airship-discuss mailing list