Member since
10-01-2018
802
Posts
143
Kudos Received
130
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2252 | 04-15-2022 09:39 AM | |
1742 | 03-16-2022 06:22 AM | |
5122 | 03-02-2022 09:44 PM | |
2051 | 03-02-2022 08:40 PM | |
1277 | 01-05-2022 07:01 AM |
10-23-2019
09:38 PM
If that resolves your issue, please spare some time in accepting the solution. Thanks.
... View more
10-18-2019
09:14 AM
@SandeepSingh Have you tried to run below command in problematic host as stated earlier? /opt/cloudera/cm-agent/bin/supervisorctl -c /var/run/cloudera-scm-agent/supervisor/supervisord.conf restart status_server This bug has been fixed in the 6.2. I may be possible the status server did not being restarted after making the changes. Please run the command and also follow the other steps stated in previous post and let us know how this goes.
... View more
10-17-2019
11:14 AM
@SandeepSingh If the same error is also can be observed from the API then this is most probably the issue with TLS. However could you please try to narrow down the issue by following methods: Run the following command on every Agent host with supervisorctl: /opt/cloudera/cm-agent/bin/supervisorctl -c /var/run/cloudera-scm-agent/supervisor/supervisord.conf restart status_server If Enable Kerberos Authentication for HTTP Web-Consoles is checked in respective service then please configure SPNEGO for browsers: https://docs.cloudera.com/documentation/enterprise/latest/topics/cdh_sg_browser_access_kerberos_protected_url.html Please let us know how this goes. If the issue remains then please run the Host Inspector and share the result.
... View more
10-17-2019
11:14 AM
@pramana I am not able to understand your ask here, could you please elaborate what is exactly the issue here. Apologies for inconvenience.
... View more
10-17-2019
08:43 AM
Happy to hear that. Yes, we have this in Radar and soon our doc will be updated with known issue in 1.6 version. Cheers, Keep visiting and contributing Cloudera Community
... View more
10-17-2019
08:01 AM
1 Kudo
@Baris We’ve known issue where in air-gapped environment the nvidia-device-plugin-daemonset pod will throw ImagePullBackOff due to inability to find a k8s-device-plugin:1.11 image in the cache. Eventually it tries to looks up to the public repository over internet and fails because the env doen’t have public access. The workaround for that is to tag the image on CDSW hosts. Please run the below command on the CDSW hosts. # docker tag docker-registry.infra.cloudera.com/cdsw/third-party/nvidia/k8s-device-plugin:1.11 nvidia/k8s-device-plugin:1.11 Let me know if your environment is outside internet. Try the above command and keep us posted.
... View more
10-16-2019
03:14 PM
@neron Yes, Public IP should be fine. The wildcard DNS hostname configured for Cloudera Data Science Workbench must now be resolvable from both, the CDSW cluster, and your browser. This means The wildcard DNS resolution needs to work on both the CDSW nodes and on your end user machine. If you configured it correctly from CDSW master/worker, but fails from your laptop/PC/end user machine, this could be an issue.
... View more
10-16-2019
03:05 PM
@Baris Things looks good and the steps you followed looks also fine. Can you stop CDSW service and reboot the host and restart the CDSW again. Check if the CDSW detecting GPU, If not then please run below command send us the cdsw logs from the cdsw master role host. cdsw logs
... View more
10-15-2019
03:28 PM
@Baris Can you paste a CDSW home page's screenshot here? Also check the latest cdsw.conf file on the master role host like below and upload here. /run/cloudera-scm-agent/process/xx-cdsw-CDSW_MASTER/cdsw.conf (Where xx is the greatest number)
... View more
10-15-2019
03:06 PM
@simps Can you please Goto the CDSW > Account settings > Hadoop Authentication and delete the principal and credentials (password) save changes and then try to launch the session.
... View more