Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

CDSW bad status

Highlighted

Re: CDSW bad status

Expert Contributor

@lafi_oussama This needs to be fixed. The resolution not looks good. Could you send "cdsw logs" if the problem still there.

[root@master ~]# nslookup master.example.com
Server: 192.168.180.2
Address: 192.168.180.2#53

** server can't find master.example.com: NXDOMAIN

 

Re: CDSW bad status

@police 

Yes it was executed as root.

[root@master ~]# sudo ps -ef | grep -i kube
root 61190 61158 44 12:37 ? 00:03:12 /opt/cloudera/parcels/CDSW-1.6.0.p1.1294376/docker/bin/dockerd --log-driver=journald --log-opt labels=io.kubernetes.pod.namespace,io.kubernetes.container.name,io.kubernetes.pod.name --iptables=false -s devicemapper --storage-opt dm.basesize=100G --storage-opt dm.thinpooldev=/dev/mapper/docker-thinpool --storage-opt dm.use_deferred_removal=true
root 61953 61781 0 12:37 ? 00:00:00 /bin/sh -x /opt/cloudera/parcels/CDSW-1.6.0.p1.1294376/scripts/wait-for-kubelet.sh
root 67555 41485 0 12:45 pts/1 00:00:00 grep --color=auto -i kube

Don't have an account?
Coming from Hortonworks? Activate your account here