Member since
09-09-2016
29
Posts
8
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
6087 | 03-18-2017 08:42 PM | |
6729 | 09-11-2016 01:51 PM | |
3578 | 09-11-2016 01:49 PM |
03-13-2017
12:24 AM
Ambari ver 2.2.1.0 came with the HDP 2.4 Sandbox I set up back around Sep 2016. I am thinking of just killing my current Sandbox and setting up a new HDP 2.5 Sandbox and am especially looking forward to Ambari ver 2.4 because of its feature list. I would like to hear from anyone who already has the HDP 2.5 Sandbox set up on Azure to confirm that hope, as the Azure Marketplace item doesn't go into much detail.
... View more
03-12-2017
10:41 PM
Labels:
- Labels:
-
Hortonworks Data Platform (HDP)
03-05-2017
10:09 PM
@Attila Kanto - I see no option in Ambari to remove Atlas (which is an upgrade prerequisite), i.e. no 'Delete' option under 'Service Actions' for Atlas. After some research, realized that upgrading Ambari to 2.4 is prerequisite to upgrading HDP to 2.5 because the 'remove service' functionality was added to Ambari in 2.4: http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-release-notes/content/ambari_relnotes-2.4.2.0-new-features.html Related Links: https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-upgrade/content/upgrading_HDP_prerequisites.html http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-user-guide/content/removing_a_service.html
... View more
09-12-2016
12:26 PM
I agree. It was a HUGE hint. I had a few other things to think through but knowing I had to scp in as root was pivotal. Thank you! BTW the tutorial needs a little correction/elaboration on that step; not sure exactly who that needs to be communicated to?
... View more
09-11-2016
01:51 PM
3 Kudos
OK, I finally got it to work! The instruction in Step 1.4 in Section 2 of the "Learning the Ropes ..." tutorial (Sandbox in Microsoft Azure) is wrong, in 3 ways: The scp port for Azure is 22, not 2222 You must scp into Azure as root; therefore you must reset the root password in your Sandbox first using 'sudo passwd root' Your home directory is not just “RemoteUser” from root’s perspective, but /home/RemoterUser'
... View more
09-11-2016
01:49 PM
1 Kudo
OK, I finally got it to work! The instruction in Step 1.4 in Section 2 of the "Learning the Ropes ..." tutorial (Sandbox in Microsoft Azure) is wrong, in 3 ways: The scp port for Azure is 22, not 2222 You must scp into Azure as root; therefore you must reset the root password in your Sandbox first using 'sudo passwd root' Your home directory is not just “RemoteUser” from root’s perspective, but “/home/RemoterUser'
... View more
09-11-2016
02:09 AM
@slachterman The ‘Learning the Ropes’ tutorial (step 1.4 in Section 2) actually says to use localhost but I eventually realized that didn't make sense so I started using the Public IP address from my Azure Sandbox settings; that's what I mean by xx.xx.xx.xx in my subsequent posts. Sorry if that wasn't clear. I also tried my fully-qualified pubic hostname, logging in as root, and got the same result as when I used the IP address. The tutorial instructions say to use port 2222, but the SSH port is configured as 22 in my Azure Sandbox. In other words, the following 2 commands do not work. According to the console output, the file is transferred but I cannot find it anywhere on my Sandbox. scp -P 22 /Path/Somefile.txt root@40.76.83.227:/RemoteDirectory scp -P 22 /Path/Somefile.txt root@sdimant.cloudapp.azure.com:/RemoteDirectory
... View more
09-10-2016
04:38 PM
@Mayur Bhokase This did not work for me. Do you have a user on your Mac with the same name as a user on your Sandbox? Is your VM on Azure or on your machine?
... View more
09-10-2016
04:14 PM
Update: I was able to make a little progress by resetting my root password on my Sandbox (using 'sudo passwd root') and then scp'g in as root with that password. The console response makes it seems as if a file was actually transferred but I cannot find it anywhere on my Sandbox (even using 'find /*.txt'). In that case the console output was: root@xx.xx.xx.xx:'s password: Somefile.txt 100% 133KB 133.4KB/s 00:00 When I try port 2222 (as per the tutorial), I just time-out with the response below (I read in other posts that people are recommending port 22 for Azure): ssh: connect to host xx.xx.xx.xx port 2222: Operation timed out lost connection When I try to scp in as root from the web client, I'm back to ground zero: root@xx.xx.xx.xx:'s password: /Path/Somefile.txt: No such file or directory So confused ... 😞
... View more
09-10-2016
04:07 PM
It basically just says "Permission denied". MyMac:~ LocalUser$ scp -P 22 /Path/Somefile.txt RemoteUser@xx.xx.xx.xx:/RemoteUser RemoteUser@xx.xx.xx.xx:'s password: scp: /RemoteUser: Permission denied When I try port 2222 (as per the tutorial), I just time-out with: ssh: connect to host xx.xx.xx.xx port 2222: Operation timed out lost connection I was able to make a little progress by resetting my root password on my Sandbox (using 'sudo passwd root') and then scp'g in as root with that password. The console response makes it seems as if a file was actually transferred but I cannot find it anywhere on my Sandbox (even using 'find /*.txt'). In that case the console output was: root@xx.xx.xx.xx:'s password: Somefile.txt 100% 133KB 133.4KB/s 00:00 When I try to scp in as root from the web client, I'm back to ground zero: root@xx.xx.xx.xx:'s password: /Path/Somefile.txt: No such file or directory So confused ... 😞
... View more
- « Previous
-
- 1
- 2
- Next »