Reply
NES
Explorer
Posts: 15
Registered: ‎07-03-2017

cdsw init never finish

hi

 

my installatiotion is via local repo (rpm), version 1.2.0. 

 

Please help.

 

cdsw init get stucked here 

[certificates] Generated service account token signing key and public key.
[certificates] Generated front-proxy CA certificate and key.
[certificates] Generated front-proxy client certificate and key.
[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
[apiclient] Created API client, waiting for the control plane to become ready

 

##cdsw logs

Generating Cloudera Data Science Workbench diagnostic bundle...
Checking system basics...
Saving kernel parameters...
Getting the list of kernel modules
Getting the list of systemd units
Checking validation output...
Checking application configuration...
Checking disks...
Checking Hadoop configuration...
Checking network...
Checking system services...
Checking Docker...
Checking Kubernetes...
Checking Kubelet...
Checking CDSW Host Controller...
Checking application services...
Checking cluster info...
Checking app cluster info...
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
Exporting user ids...
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?
Checking system logs...
Collecting health logs...
Exporting metrics...
The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?

ERROR:: Unable to get service account credentials. Provide SERVICE_ACCOUNT_SECRET or run on master node.: 2
Producing logs tarball...

 

Cloudera Employee
Posts: 33
Registered: ‎04-28-2017

Re: cdsw init never finish

A few questions:

 

1. Are you using a HTTP Proxy?

2. Does localhost resolve to 127.0.0.1?

3. Do you have multi-homed network configuration?

 

There are a few potential causes for an initialization hang.

 

Tristan

NES
Explorer
Posts: 15
Registered: ‎07-03-2017

Re: cdsw init never finish

1. I am not using proxy, servers do not have access to internet (blocked). intallation is via local repo

 

2. it resolve to 127.0.0.1 [root@server ~]$ ping localhost '

PING localhost (127.0.0.1) 56(84) bytes of data.

64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.043 ms

64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.027 ms

64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.033 ms

64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.043 ms

^C --- localhost ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3000ms rtt min/avg/max/mdev = 0.027/0.036/0.043/0.009 ms

 

3. It's not multi homed. it's a small vm.

Highlighted
NES
Explorer
Posts: 15
Registered: ‎07-03-2017

Re: cdsw init never finish

proxy config options.
option 1
both http_proxy and no_proxy blank
ERROR: The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?

option 2
http_proxy =proxyserver:8080 and no_proxy ="127.0.0.1,localhost,10.masterIP,100.66.0.1,100.66.0.1/24"
ERROR: The connection to the server 10.x.x.x:6443 was refused - did you specify the right host or port?

option 3
http_proxy ="" and no_proxy ="127.0.0.1,localhost,10.masterIP,100.66.0.1,100.66.0.1/24"
ERROR: new below error


etcd-cdswserver.local 1/1 Running 0 22m 10.x.x.x cdswserver.local
kube-apiserver-cdswserver.local 1/1 Running 0 21m 10.x.x.x cdswserver.local
kube-controller-manager-cdswserver.local 1/1 Running 0 22m 10.x.x.x cdswserver.local
kube-dns-3913472980-xtsrm 2/3 CrashLoopBackOff 15 22m 100.66.0.2 cdswserver.local
kube-proxy-2fqts 1/1 Running 0 22m 10.x.x.x cdswserver.local
kube-scheduler-cdswserver.local 1/1 Running 0 22m 10.x.x.x cdswserver.local
weave-net-hd8pw 2/2 Running 0 22m 10.x.x.x cdswserver.local

Cloudera Data Science Workbench Pod Status


WARNING: Unable to bring up pods tagged as 'k8s-app' in the kube-system cluster.

WARNING: Unable to bring up kube-system cluster.: 1

WARNING: Some pods in the CDSW application are not yet up.: 1

WARNING: Application services are incomplete

WARNING: Config maps are incomplete

WARNING: Secrets are incomplete

WARNING: Persistent volumes are incomplete

WARNING: Persistent volume claims are incomplete

WARNING: Ingresses are incomplete

WARNING: Unable to bring up pods tagged as 'k8s-app' in the kube-system cluster.

ERROR:: Cloudera Data Science Workbench is not ready yet: some system pods are not ready: 1
[admin@cdswserver ~]$ sudo cdsw logs
Generating Cloudera Data Science Workbench diagnostic bundle...
Checking system basics...
Saving kernel parameters...
Getting the list of kernel modules
Getting the list of systemd units
Checking validation output...
Checking application configuration...
Checking disks...
Checking Hadoop configuration...
Checking network...
Checking system services...
Checking Docker...
Checking Kubernetes...
Checking Kubelet...
Checking application services...
Checking cluster info...
Checking app cluster info...
Exporting user ids...
Error from server (NotFound): configmaps "internal-config" not found
error: pod name must be specified
Checking system logs...
Producing logs tarball...

Announcements