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 | |
2053 | 03-02-2022 08:40 PM | |
1277 | 01-05-2022 07:01 AM |
11-28-2019
09:42 AM
@VamshiDevraj Does this resolves your issue? If yes please mark this as solution.
... View more
11-28-2019
09:28 AM
@SandeepSingh This looks like the issue with TLS. Eventhough the flag 'Use TLS Authentication of Agents to Server' in CM WebUI is not set, the following flag must be set for status_server to use TLS protocol using port 9000. Go to the /opt/cloudera/security/x509/ directory and use 'pem' and 'key' file under that directory. You may also have to use the password file for the private key if there is one. Then edit the /etc/cloudera-scm-agent/config.ini file with below parameters. # PEM file containing client private key. client_key_file= # If client_keypw_cmd isn't specified, instead a text file containing the client private key password can be used. client_keypw_file= # PEM file containing client certificate. client_cert_file=/etc/cdep-ssl-conf/CA_STANDARD/cm_server-cert.pem verify_cert_file= Restart of the status_server is required cd /var/run/cloudera-scm-agent/supervisord /opt/cloudera/cm-agent/bin/supervisorctl -c /var/run/cloudera-scm-agent/supervisor/supervisord.conf restart status_server In addition, restart of the cloudera-scm-agent is also needed service cloudera-scm-agent restart
... View more
11-20-2019
09:15 AM
@isingh Your Welcome. Please spare sometime to mark this as solution. Thanks Keep exploring the Cloudera Community!
... View more
11-20-2019
07:45 AM
1 Kudo
@isingh NO, GPU supports started from C6 release. https://docs.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_cdh_600_new_features.html#concept_hsn_zgc_cdb
... View more
11-19-2019
12:57 PM
@TheBroMeister Please spare some time in accepting the solution. Thanks.
... View more
11-19-2019
12:56 PM
@nanda_bigdata Please spare some time in accepting the solution. Thanks.
... View more
11-19-2019
12:44 PM
@MihailK In RHEL7 chronyd is taking preference over the NTP. So it's worth to check if NTP service is running, if yes then disable it. System should use chronyd only. Secondly agent checks the status of clock in every 2 seconds and read the output of chronyd sources or ntpq. If this does not find * in the output then it marked that instant false and triggers an alert. So you also have to check that NTP servers is in sync every-time and ask with your OS team if they have any drops.
... View more
11-19-2019
12:38 PM
1 Kudo
Yes @VamshiDevraj . Please use the supported OS as this could cause other issues. Also as previously said, I am in doubt that your DNS is resolving correctly. Looking at the errors and the hosts file it appears an issue with this. cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 172.16.40.3 master.ezydata.fr master 172.16.40.4 worker1.ezydata.fr worker1 172.16.40.5 worker2.ezydata.fr worker2 172.16.40.6 worker3.ezydata.fr worker3 172.16.40.7 cdsw.ezydata.fr cdws 172.16.40.7 *.cdsw.ezydata.fr The 7th line is incorrect, short name should be cdsw not cdws. Please correct this and follow the steps to remove IP tables. Check the DNS resolution working correctly. If DNS works, then got to CM and run prepare node first. Start CDSW service.
... View more
11-17-2019
04:05 AM
1 Kudo
@nanda_bigdata Normally this is admin/admin but this depends on initial setup. If you do not remember the original password, you can reset it by going directly to http://cdsw.company.com/forgot-password Once reset, use debug login URL http://cdsw.company.com/login?debug=1 to fallback to the local database. FYI: https://docs.cloudera.com/documentation/data-science-workbench/1-0-x/topics/cdsw_external_authentication.html#debug_login_url Let us know if this resolves your issue.
... View more
11-17-2019
03:40 AM
@TheBroMeister Yes, you require the new set of hosts to install CDSW on that. Cloudera Data Science Workbench does not support running any other services except gateway roles on CDSW dedicated hosts. Cloudera Data Science Workbench runs on one or more dedicated gateway hosts on CDH clusters. Each of these hosts has the Cloudera Manager Agent installed on them. Each gateway host must be dedicated solely to Cloudera Data Science Workbench. This is because user workloads require dedicated CPU and memory, which might conflict with other services running on these hosts. You can refer the CDSW architecture from below doc. https://www.cloudera.com/documentation/data-science-workbench/latest/topics/cdsw_overview.html#cdsw_architecture
... View more