Member since
01-19-2017
3679
Posts
632
Kudos Received
372
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1019 | 06-04-2025 11:36 PM | |
| 1575 | 03-23-2025 05:23 AM | |
| 790 | 03-17-2025 10:18 AM | |
| 2851 | 03-05-2025 01:34 PM | |
| 1867 | 03-03-2025 01:09 PM |
10-06-2019
05:08 AM
1 Kudo
@ThanhP I can see you are accessing the web shell UI on 192.168.1.37 yet the sandbox is pointing to 172.18.0.2:8020. Now if you type in your browser http://192.168.1.37:1080/splash2.html you should land on the splash screen Choose the Ambari UI link , this should give you the normal Ambari user UI if you reset your password before as I had stated please use that admin/[password] combination and you will realize that none of the components are started HDFS, YARN, MR, HIVE, HBASE etc Note: some components are in maintenance mode unless you want any of them beware of the dependencies e.g ATLAS must have HBASE running etc.. that could explain why you got the error "Failed on connection error java.net.Connection" At a certain point during your startup, "Timeline Service V1.5" will error out with the message to do with "safemode on" get to the shell as hdfs $ hdfs dfsadmin -safemode get This should indicate it's ON so get it out of safemode $ hdfs dfsadmin -safemode leave And again use the option Ambari start all it will pick up from the last point of failure, after the components startup you can simply access them eg the name node UI will automatically point to http://sandbox-hdp.hortonworks.com:50070/dfshealth.html#tab-overview Please do that an revert
... View more
10-05-2019
10:52 AM
@Mitchel Is your virtual box running on Ubuntu? How much memory are you allocating to the Virtualbox and also descript your network setup Page1 Page2 page01See the attached
... View more
10-05-2019
04:30 AM
1 Kudo
@ThanhP What @Herman was trying to explain is what happens in the background and you cannot influence or manually replicate the process. The screenshots I attached are the best you can get to resolve the issue because the screenshots are from exactly the same sandbox you are using. So follow those steps and revert
... View more
10-05-2019
04:24 AM
@erkansirin78 Great !! it worked out for you, If you found this answer addressed your question, please take a moment to log in and click the thumbs up button. That would be a great help to Cloudera Community to find the solution quickly for these kinds of errors and mark it as a solution
... View more
10-04-2019
01:05 PM
@saivenkatg55 What are the permission on that file? It should be -rw-r--r-- 1 yarn hadoop $ ls /var/log/hadoop-yarn/yarn/hadoop-yarn-nodemanager-<host_name>.org.out Permissions should be # chmod 644 /var/log/hadoop-yarn/yarn/hadoop-yarn-nodemanager-<host_name>.org.out Ownership should be yarn:hadoop
... View more
10-04-2019
12:54 PM
@Alieer It looks likes white space issue between the $ sqoop import-all-tables \ -m 1 \ --connect jdbc:mysql://quickstart:3306/retail_db \ --username=retail_dba \ --password=cloudera \ --compression-codec=snappy \ --as-parquetfile \ --warehouse-dir=/user/hive/warehouse \ --hive-import Please try to copy and paste the above
... View more
10-04-2019
12:24 PM
@erkansirin78 It seems you have an issue with your known_hosts file, you need to remove the third(3) line in known_hosts file /c/Users/user/.ssh/known_hosts:3 Most likely an SSH altered the encryption keys due to a possible security hole. You can then purge that specific line from your known_hosts file: # sed -i 377d ~/.ssh/known_hosts but it seems your known_hosts file is mounted on the C drive on /c/Users/user/ windows 10!! You can also remove StrictHostKey checking in your ssh configuration file, typically stored at ~/.ssh/config. An example Host block is provided below: Host 101 HostName yourip|hostname User your_Userid IdentityFile /path/to/keyfile Port 22 StrictHostKeyChecking no The specifically added line is the last one StrictHostKeyChecking no which does just that. Please do that and revert
... View more
10-01-2019
12:31 PM
2 Kudos
@ThanhP I had the same situation with my Sandbox I had not used for a while. Here is my config I disabled all the network adapters except one which I attached to my LAN using the Bridged Adapter, 12 GB, 4 CPU's see attached screenshots once my Sandbox had booted I accessed the CLI and managed to turn off safe mode as the namenode was not starting. You should access the Linux CLI through the web interface. Can you try that and revert
... View more
09-26-2019
12:44 PM
@anbazhagan_muth When I look at your scripts, your Kafka scripts should run like shell scripts so your syntax should look like this from the Kafka install directory kafka/bin/kafka-console-consumer.sh --bootstrap-server quickstart.cloudera:9092 --topic smoke --from-beginning Please revert
... View more