Announcements
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.
NES
Explorer
My Accepted Solutions
Show All

Re: cdsw init never finish

by Explorer in Support Questions
‎11-25-2017 10:56 PM
‎11-25-2017 10:56 PM
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... ... View more

Re: cdsw init never finish

by Explorer in Support Questions
‎11-23-2017 08:43 PM
‎11-23-2017 08:43 PM
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. ... View more

cdsw init never finish

by Explorer in Support Questions
‎11-22-2017 01:58 AM
‎11-22-2017 01:58 AM
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...   ... View more

Re: ContainerCreating: Creating engine container

by Explorer in Support Questions
‎07-10-2017 03:14 AM
‎07-10-2017 03:14 AM
the images/containers cannot resolve hostname with names but IP. scala project comes with error. Setting default log level to "ERROR". To adjust logging level use sc.setLogLevel(newLevel). For SparkR, use setLogLevel(newLevel). 17/07/10 08:26:54 ERROR spark.SparkContext: Error initializing SparkContext. java.lang.IllegalArgumentException: java.net.UnknownHostException: CDH-MN-511-CE1.EOH.COM at org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:406) at org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:310) at org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider$DefaultProxyFactory.createProxy(ConfiguredFailoverProxyProvider.java:68) if i use terminal, i cannot ping the server with their names but i can with IPs cdsw@zx991teec5q9o67g:~$ cat /etc/hosts # Kubernetes-managed hosts file. 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet fe00::0 ip6-mcastprefix fe00::1 ip6-allnodes fe00::2 ip6-allrouters 100.66.0.9 zx991teec5q9o67g 100.77.0.130 cdsw.domainz.com 100.77.0.130 models.cdsw.domainz.com 100.77.0.130 assets.cdsw.domainz.com 100.77.0.130 consoles.cdsw.domainz.com 100.77.0.129 livelog.cdsw.domainz.com cdsw@zx991teec5q9o67g:~$ cdsw@zx991teec5q9o67g:~$ cdsw@zx991teec5q9o67g:~$ ping master ping: unknown host cdh-mn-511-ce1 cdsw@zx991teec5q9o67g:~$ ping 10.10.51.216 PING 10.10.51.216 (10.10.51.216) 56(84) bytes of data. 64 bytes from 10.10.51.216: icmp_seq=1 ttl=63 time=0.220 ms 64 bytes from 10.10.51.216: icmp_seq=2 ttl=63 time=0.209 ms ^C --- 10.10.51.216 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.209/0.214/0.220/0.015 ms     ... View more

Re: ContainerCreating: Creating engine container

by Explorer in Support Questions
‎07-10-2017 03:00 AM
‎07-10-2017 03:00 AM
there was a problem with wildcard dns.   i built my own dns server and i went though and image and containers are created.   i can created and launch the projects. ... View more

ContainerCreating: Creating engine container

by Explorer in Support Questions
‎07-07-2017 02:22 AM
‎07-07-2017 02:22 AM
hi   i followed below steps to create project Setting Up a Scala Project Open Cloudera Data Science Workbench. Select   New Project . Enter a   Project Name . Choose whether the   Project Visibility   is   Private   or   Public. Under   Initial Setup , choose the   Template   tab. Select  any  Scala/python/R . Click   Create Project . Your new project displays sample files. Click   Open Workbench . Select   any  Scala/python/R   engine. Click   Launch Session . the session launching never complete with status of "ContainerCreating: Creating engine container" and scheduling   Regards Nkonzo ... View more

Re: Node stateful is none

by Explorer in Support Questions
‎07-07-2017 01:29 AM
‎07-07-2017 01:29 AM
hi   i am also expiriencing the same error.   my bench has 2 workers and master. the workers are enable and with " cdsw enable" i can see that they are running.   Regards Nes ... View more

Re: not ready yet: some system pods are not ready

by Explorer in Support Questions
‎07-05-2017 02:29 AM
‎07-05-2017 02:29 AM
Hi   the problem when  stuck in ContainerCreating state, base on logs generated by command"kubectl describe pod web-3826671331-5b7wk" was failing to mount masterserverIP:/var/lib/cdsw/projects   the reason was the the incorrect master IP at /etc/cdsw/config/cdsw.conf   Regards. NES             ... View more

Re: not ready yet: some system pods are not ready

by Explorer in Support Questions
‎07-05-2017 01:28 AM
‎07-05-2017 01:28 AM
hi   thanks, you are the best Peter.   i managed to find the issue via command "  kubectl describe pod  web-3826671331-5b7wk " and i am playing using it now.   Regard Nes ... View more

Re: not ready yet: some system pods are not ready

by Explorer in Support Questions
‎07-04-2017 10:19 PM
‎07-04-2017 10:19 PM
hi    thanks for assisting Peter   here is the output. i have done the cdsw reset and then init.   cdsw status Cloudera Data Science Workbench Status Service Status docker: active kubelet: active nfs: active Checking kernel parameters... Node Status NAME STATUS AGE STATEFUL master.local Ready 28m true System Pod status NAME READY STATUS RESTARTS AGE IP NODE dummy-2088944543-90otk 1/1 Running 0 27m 10.x.x.x master.local etcd-master.local 1/1 Running 0 28m 10.x.x.x master.local kube-apiserver-master.local 1/1 Running 0 28m 10.x.x.x master.local kube-controller-manager-master.local 1/1 Running 0 28m 10.x.x.x master.local kube-discovery-1150918428-p4bcn 1/1 Running 0 27m 10.x.x.x master.local kube-dns-3873593988-gxvyr 3/3 Running 0 26m 100.66.0.2 master.local kube-proxy-bru51 1/1 Running 0 27m 10.x.x.x master.local kube-scheduler-master.local 1/1 Running 0 28m 10.x.x.x master.local node-problem-detector-v0.1-xgfcd 1/1 Running 0 26m 10.x.x.x master.local weave-net-p0p53 2/2 Running 0 27m 10.x.x.x master.local Cloudera Data Science Workbench Pod Status NAME READY STATUS RESTARTS AGE IP NODE ROLE cron-2934152315-keyj7 1/1 Running 0 26m 100.66.0.7 master.local cron db-39862959-9aw8e 1/1 Running 0 26m 100.66.0.4 master.local db db-migrate-052787a-wgkjq 0/1 Completed 0 26m 100.66.0.5 master.local db-migrate engine-deps-m39yd 1/1 Running 0 26m 100.66.0.3 master.local engine-deps ingress-controller-3138093376-2gct2 1/1 Running 0 26m 10.x.x.x master.local ingress-controller livelog-1900214889-0gi1v 1/1 Running 0 26m 100.66.0.6 master.local livelog reconciler-459456250-qnuzc 1/1 Running 0 26m 100.66.0.8 master.local reconciler spark-port-forwarder-dxhjm 1/1 Running 0 26m 10.x.x.x master.local spark-port-forwarder web-3826671331-5b7wk 0/1 ContainerCreating 0 26m <none> master.local web web-3826671331-63il0 0/1 ContainerCreating 0 26m <none> master.local web web-3826671331-hf86v 0/1 ContainerCreating 0 26m <none> master.local web Cloudera Data Science Workbench is not ready yet: some application pods are not ready [root@master ~]# cdsw validate Checking services... Checking if docker is active and enabled Checking if docker is responsive Checking if kubelet is active and enabled Check if docker monitor is active Testing networking setup... Check if kubelet iptables rules exist Check that firewalld is disabled Check configuration file... Checking master node filesystem configuration... Checking kubernetes Checking system pods Checking application pods exist Checking application pods are running ERROR:: Application pod web-3826671331-5b7wk is not running, its state is ContainerCreating: 1 ... View more
Contact Me
Online
Offline
Last Visited
‎12-15-2017 04:00 AM
Public Statistics
Date Registered ‎07-03-2017 09:57 PM
Last Visited ‎12-15-2017 04:00 AM
Total Messages Posted 15