Suppose we added user peter in active directory then do we need to add OS level ... View more

Hello @GangWar,   Thank you for the reply,   Contacting Cloudera is certainly a best option and would most likely go for it. However, currently the project is in discussion and I was just trying to get views / thoughts from the community on such a scenario if anybody had ever come across.   Thanks snm1523 ... View more

@Hoony  You can use the CDH with express version but some of the feature will be discontinue. Please see the details here.  https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ag_licenses.html#cmug_topic_13_7 Also if you need any information on licensing don't hesitate to Contact Sales Team. ... View more

@pdev The file permission on manifest.json file should be like below -rw-r--r--. 1 root root 0 Jan 21 00:15 test.txt Please run below command on  manifest.json file and then restart the CM server. chmod -R ugo+rX manifest.json service cloudera-scm-agent restart Let me know if this resolves the issue. For more details on how to use/configure repo please follow the Cloudera doc: https://docs.cloudera.com/documentation/enterprise/5-14-x/topics/cm_ig_create_local_parcel_repo.html#cmig_topic_21_3_1   Don't forget to mark the post as solution if this resolves the issue.   Cheers, ... View more

Hi @GangWar, The SOLR principal is not present in CM. ... View more

I think you have to raise this issue with Oracle, This is not Cloudera software issue. ... View more

@ramineni Please find the netcat O/P   [hdfs@w0lxdhdp01 ~]$ nc -v w0lxqhdp01 8020 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 10.49.70.13:8020. ... View more

Your best resource would be to  contact sales  for the most up to date information. ... View more

@ChineduLB @TCloud This issue is most probably due to Zero Byte var/lib/cloudera-scm-agent/active_parcels.json file available. Please follow the below steps: 1. Stop the agent on this host. 2. Remove both: /var/lib/cloudera-scm-agent/active_parcels.json /var/lib/cloudera-scm-agent/response.avro 3. Start the Agent Please don't forget to mark this as a solution if resolves the issue.    Cheers.  ... View more

@tuk  You can upgrade the packages based cluster but it's very tedious process so not recommended. https://docs.cloudera.com/documentation/enterprise/upgrade/topics/ug_overview.html The best way is to migrate from packages to parcels and then upgrade. https://docs.cloudera.com/documentation/enterprise/6/latest/topics/cm_ig_migrating_packages_to_parcels.html#migrate_pkg_to_parcel Once you migrated you can use this page to get the CM server running with Web UI. https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/installation.html Regarding your ask " Is there any way by which an Unmanaged 5.x cluster can move to CDH 6.x (may be adding it in Cloudera Manager and then moving to 6.x)?"   I am thinking that you can build a 1 node CM server and then add these present cluster by adding node in that CM. (Though I haven't tried this on packages) ... View more

1. use Ranger Auditing for Hive to check the Query details run by a user. Hive does not store this detail in metastore. https://docs.cloudera.com/HDPDocuments/HDP3/HDP-3.1.4/audit-ref/content/managing_auditing_in_ranger_access.html 2.  You can use the below Query To get all the apps having states as FINISHED,KILLED by the specific user for specific time period GET "http://Resource-Manager-Address:8088/ws/v1/cluster/apps?limit=20&states=FINISHED,KILLED&user=<user-id>&startedTimeBegin={time in epoch}&startedTimeEnd={time in epoch}"   3. Simply make use of Tez view if your execution Engine is Tez     ... View more

Thanks @EricL for chime in. @manjj That's correct I found it later today as well this resides in desktop_document2 nowadays 🙂 ... View more

@kiranpune Can you tell me the context here.    The one could say that if the container is small could be more efficient and easy to pull and push and also could reduce the security issues.   ... View more

@pra_big  Thanks for posting on Cloudera community.   The error indicating that the CSD is not compatible with the new CDSW version (CDSW1.6) as you have CSD compatible for CDH 5.14.    You need to remove old CDS file compatible to CDH5 and then download the new CSD for CDH6 from this document. Also please follow the doc to configure the CSD locations and then proceed with upgrade procedure. https://docs.cloudera.com/documentation/data-science-workbench/1-6-x/topics/cdsw_upgrade_parcel.html#cdsw_upgrade_parcel   Don't forget to mark this post as a solution if this resolves your issue. Cheers.    ... View more

Hi @syedshakir ,   Please give oozie.access to the user and then try it again.   Thanks, Li ... View more

@MPI Can you share the full stderr/stdout logs? ... View more

@issa7100 If my understanding is correct then this is the Cloudera quick-start docker image on docker hub. https://hub.docker.com/r/cloudera/quickstart/   docker pull cloudera/quickstart If you are looking for CDSW installation on CDH cluster for production or testing purpose with broad functionality then please follow this installation guide.   https://docs.cloudera.com/documentation/data-science-workbench/1-6-x/topics/cdsw_install.html   Don't forget to mark this as solution if this resolves your query.   Cheers, ... View more

@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   ... View more

@MihailK does this resolved the issue? If yes, please spare some time to mark this as solution. Thanks. ... View more

@RashadX If issue is resolved, please spare some time to mark this as solution. Thanks. ... View more

@VamshiDevraj Does this resolves your issue? If yes please mark this as solution. ... View more

@srkphani Can you share the stderr/stdout logs? Make sure the DNS resolution is working and stop CDSW service and run a prepare node on the host using CM and then start the docker, master, application role respectively on the node. ... View more

@Imr This is a generic message if agent installation is failed. Please verify all these things for a quick sanity check. If agent installation still fails then please send the CM server logs: /var/log/cloudera-scm-server/cloudera-scm-server.log   ... View more

@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

Haven't yet had a chance to take another run with the installation.  ... View more