Member since
11-07-2016
637
Posts
253
Kudos Received
144
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2720 | 12-06-2018 12:25 PM | |
| 2862 | 11-27-2018 06:00 PM | |
| 2194 | 11-22-2018 03:42 PM | |
| 3567 | 11-20-2018 02:00 PM | |
| 6273 | 11-19-2018 03:24 PM |
12-01-2017
06:43 PM
@Chaitanya D, For the hostname : You can give either localhost or chaitu For SSH private key : you should give SSH private of root sudo su cat ~/.ssh/id_rsa --> This is the private key for root ssh username : root (not chaitu) Can you please paste the complete log. There is no error on the log above.
... View more
12-01-2017
06:11 PM
1 Kudo
@Chaitanya D, Oops!! There was a typo in my command above.It should be id_rsa.pub and not id_rsa Please run this command. cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
### to verify passwordless ssh run below command
ssh root@localhost --> should login without asking for passwordl Make these changes and run the Register step again in Ambari GUI. Thanks, Aditya
... View more
12-01-2017
05:40 PM
@Chaitanya D, 1) If you choose public repository , then all the rpms will be downloaded from the hortonworks public repository. If you choose local repository then you need to set up a local yum repo and put the tarball there and run a webserver to serve these tarball. This is generally used in a setup where network access is blocked to outside world. You can use public repo. 2) In the target hosts , you need to mention hostnames of all the nodes which are going to be as part of the cluster. SSH private key is ssh key of the user running ambari-server. 3) No. Each machine is treated as a single node. You need to setup password-less ssh before giving the details in #2 . Since you are using a single node you do the below #sudo su ---> to become root user
#ssh-keygen -----> generate the ssh keys
# cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys ---> for password-less ssh
#cat ~/.ssh/id_rsa ----> copy the output and put it in SSH private key in UI
# cat /etc/hostname ----> copy and put in target hosts Thanks, Aditya
... View more
12-01-2017
03:22 PM
@yassine sihi, Server error attempting a GET to /rhsm/ returned status 503 The above looks like a error from RedHat Subsrciption Manager. Can you try installing manually and retry failed nodes from UI yum install ambari-agent
... View more
12-01-2017
03:01 PM
@yassine sihi, Can you please check if passwordless ssh is configured from ambari server node to the node where you are facing the issue. Also check that the hostname which you gave in ambari GUI exists in /etc/hosts and you are able to do passwordless ssh to the hostname mentioned. Can you also attach the ambari-server.log (/var/log/ambari-server/ambari-server.log) Thanks, Aditya
... View more
12-01-2017
02:40 PM
@Chaitanya D, Glad that it worked. Can you please open a new question instead of piggybacking. This will divert the main thread. Please tag me in the new question and I am happy to help 🙂
... View more
12-01-2017
12:21 PM
1 Kudo
@yassine sihi, Ambari will by default run on port 8080. 3306 is default port for mysql . If you still want to use 3306 for ambari (though it is not recommended) You can add this line in /etc/ambari-server/conf/ambari.properties client.api.port=3306 Restart ambari server after doing this ambari-server restart Also check the logs to find out exact issue, (/var/log/ambari-server/ambari-server.log) Thanks, Aditya
... View more
12-01-2017
12:18 PM
2 Kudos
@Jon Udaondo, Edit this line in cluster_configuration.json ( %) is missing "dfs.namenode.shared.edits.dir" : "qjournal://%HOSTGROUP::namenode1:8485;%HOSTGROUP::namenode2%:8485;%HOSTGROUP::namenode3%:8485/mycluster", to "dfs.namenode.shared.edits.dir" : "qjournal://%HOSTGROUP::namenode1%:8485;%HOSTGROUP::namenode2%:8485;%HOSTGROUP::namenode3%:8485/mycluster", Thanks, Aditya
... View more
12-01-2017
06:23 AM
@Ashikin, You can see that json is corrupted. 1)Login to Ambari -> Hosts- > Select Zeppelin Host -> Refresh Client configs 2)Make sure that json is valid 3)Restart zeppelin (or) Try moving the file to a back up file and try restarting zeppelin and see if it creates a new file
... View more
12-01-2017
06:00 AM
@Ashikin, Can you please attach your /etc/zeppelin/conf/interpreter.json file.
... View more