Created 12-16-2016 05:19 PM
Context: using Virtual Box and HDP 2.5 sandbox
In section 2, it states "Navigate to Ambari welcome page using the url given on Sandbox welcome page.". The Sandbox Welcome page is "localhost:8888", but there is no URL on this page for Ambari. I do find it when I click on "quick links" a the bottom of the page. This should be clarified in the material.
However, there is only one link provided in the Ambari quick link and it takes me to Zeppelin.
When I go thru the steps using "ifconfig" to find my host address (which happened to be 172.17.0.2) and then open in my browser that address with 8080 appended, it just times out. Should this be different than "localhost:8080"? But as noted this link takes me to Zeppelin welcome page, not Ambari.
What should the link be to Ambari (or if I have missed something, what did I miss)?
Created 12-16-2016 06:12 PM
Ambari should always run on 8080 port, so connecting to http://localhost:8080 should take you directly to the ambari login.
Zeppelin runs on port 9995.
Created 12-16-2016 09:30 PM
Here you go:
[root@sandbox ~]# ifconfig -a docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 inet6 fe80::42:b5ff:fe1d:634f prefixlen 64 scopeid 0x20<link> ether 02:42:b5:1d:63:4f txqueuelen 0 (Ethernet) RX packets 1462 bytes 512300 (500.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1942 bytes 216711 (211.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::a00:27ff:fea5:537e prefixlen 64 scopeid 0x20<link> ether 08:00:27:a5:53:7e txqueuelen 1000 (Ethernet) RX packets 2256 bytes 271935 (265.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1972 bytes 734622 (717.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 12 bytes 1020 (1020.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12 bytes 1020 (1020.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth6cc2f97: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::3485:4aff:fe87:17d0 prefixlen 64 scopeid 0x20<link> ether 36:85:4a:87:17:d0 txqueuelen 0 (Ethernet) RX packets 1462 bytes 532768 (520.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1950 bytes 217359 (212.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@sandbox ~]#
Created 12-19-2016 01:25 PM
Back at it this morning and, while I don't quite get what's happening, I consider this resolved. This morning I did the following:
This is now the second time I have seen localhost and 127.0.0.1 be treated differently; one of these days I'll have to figure out why. But for now, I'm back in business and continuing the tutorial.
Thanks everyone for their help!
Cecil