The output is truncated. Can you upload the full output of cdsw status or you can just attach the file  cdsw-logs-cdsw-2019-11-15--15-21-38.redacted.tar.gz here. So that I can see the logs.    Also please make sure you have followed all the prerequisite from here: https://www.cloudera.com/documentation/data-science-workbench/latest/topics/cdsw_install.html#pre_install Make sure you have IPv6 enabled in the CDSW host. Take a look of known issue here: https://www.cloudera.com/documentation/data-science-workbench/latest/topics/cdsw_known_issues.html#known_issues_limitations     ... View more

@VamshiDevraj please remove the old IP tables from the host by running below command. 1. Stop CDSW service. 2. Run below commands on master host. sudo iptables -P INPUT ACCEPT sudo iptables -P FORWARD ACCEPT sudo iptables -P OUTPUT ACCEPT sudo iptables -t nat -F sudo iptables -t mangle -F sudo iptables -F 3. Start Docker role on master node, once complete than start Master role on the master node and then Application role on Master node. Run cdsw status command and send the output here. It will be good if you can send the cdsw logs output from the node. ... View more

@lafi_oussama you can simply do a nslookup <hostname> ... View more

@SandeepSingh A quick thing I noticed is that the RHEL7.7 is not supported for the CDH6.2: https://docs.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_os_requirements.html#c62_supported_os ... View more

@lafi_oussama The connection refused error looks likes the DNS and on top of that you are using CDSW 1.6 version so you need to be enable IPV6 in all the CDSW hosts. It's a known issue with this version.  Please enable IPV6 by below method on CDSW hosts: Edit /etc/default/grub and delete the ipv6.disable=1 entry from GRUB_CMDLINE_LINUX. For example: GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/swap crashkernel=auto rd.lvm.lv=rhel/root" Run the grub2-mkconfig command to regenerate the grub.cfg file: grub2-mkconfig -o /boot/grub2/grub.cfg Alternatively, on UEFI systems, you would run the following command: grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg Delete the /etc/sysctl.d/ipv6.conf file which contains the following entry: # To disable for all interfaces net.ipv6.conf.all.disable_ipv6 = 1 # the protocol can be disabled for specific interfaces as well. net.ipv6.conf.<interface>.disable_ipv6 = 1 Check the contents of the /etc/ssh/sshd_config file and make sure the AddressFamily line is commented out. #AddressFamily inet Make sure the following line exists in /etc/hosts, and is not commented out: ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 Enable IPv6 support on the ethernet interface. Double check /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-* to ensure you've set IPV6INIT=yes. This setting is required for IPv6 static and DHCP assignment of IPv6 addresses. Stop the Cloudera Data Science Workbench service. Reboot all the Cloudera Data Science Workbench hosts to enable IPv6 support. Test your changes: Run dmesg. The output should NOT contain ipv6.disable=1 as shown here: $ dmesg [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.10.0-514.el7.x86_64 root=UUID=3e109aa3-f171-4614-ad07-c856f20f9d25 ro console=tty0 crashkernel=auto console=ttyS0,115200 ipv6.disable=1 [ 5.956480] IPv6: Loaded, but administratively disabled, reboot required to enable This shows that IPv6 was not correctly enabled on reboot. Run sysctl to ensure IPv6 is not disabled. The output should NOT contain the following line: net.ipv6.conf.all.disable_ipv6 =1 Run the ip a commands to check IP addresses on all ethernet interfaces such as weave. They should now display an inet6 address. Start the Cloudera Data Science Workbench service. following the steps as I suggested earlier in the post https://community.cloudera.com/t5/Support-Questions/CDSW-bad-status/m-p/281186/highlight/true#M209231 . Run dmesg on the CDSW hosts to ensure there are no segfault errors seen. Also it's worth to check if you have followed all the prerequisite of CDSW like wildcard DNS setup, SeLinux etc. Make sure your DNS is resolving the names correctly. https://docs.cloudera.com/documentation/data-science-workbench/1-6-x/topics/cdsw_requirements_supported_versions.html ... View more

@lafi_oussama What version of CDSW you are using and is this RPM based install or CSD based? The error could caused by various issue, however could you please execute below steps (If this is CSD based and managed by Cloudera Manager): Stop the CDSW service from the CM. Clear all IP tables from the Master Role host by running below command: sudo iptables -P INPUT ACCEPT sudo iptables -P FORWARD ACCEPT sudo iptables -P OUTPUT ACCEPT sudo iptables -t nat -F sudo iptables -t mangle -F sudo iptables -F On master node run weave reset: # opt/cloudera/parcels/CDSW/cni/bin/weave reset Goto the CM > CDSW > Action > Prepare Node. Wait till this finish. Goto the CM > CDSW > Instances > and select the Docker role on the master host and start, after finishing select Master role on master host start, wait till finish and then select Application on Master node and start, then select Docker, Worker daemons on Worker nodes and start it. Let us know if this resolves the issue. If not then please send us the following command output from the CDSW master node: #cdsw validate #cdsw status #ps -eaf | grep -i kube ... View more

@roberto10 If that resolves your issue, please spare some time in accepting the solution. Thanks. ... View more

@farmountain If that resolves your issue, please spare some time in accepting the solution. Thanks. ... View more

@hadoophoot If that resolves your issue, please spare some time in accepting the solution. Thanks. ... View more

@neron If that resolves your issue, please spare some time in accepting the solution. Thanks. ... View more