Created 01-10-2018 02:45 PM
I've imported the respective OVAs to Virtualbox 5.1.3 and VMware, on both Workstation 14.1.1 and ESXi 6.0, with no connect success to http://<IP_address>:8888/. Only the third CentOS rescue boot entry allowed me to reach the login screen. In this latter case, I logged in as "root", and realized that no Docker service was started, because of missing "overlay" file system. What's going on?
Created 01-10-2018 06:49 PM
Can you please provide the Sandbox Version?
When you run into an issue, one of the first things someone will ask is “what sandbox version are you using“? To get this information:
Login using shell web client and execute:
Created 01-11-2018 12:34 AM
Actual link is:
Could you also provide screen shots from VirtualBox / VMWare?
If you're using VirtualBox:<IP_address> should be 127.0.0.1. For more details, refer to Learning the Ropes tutorial
Created on 01-11-2018 11:42 AM - edited 08-18-2019 01:10 AM
@gdeleon This is the screen capture of the boot output using the "rescue" Linux version (3rd boot option). VM has been imported into VMware ESXi 6.0 with 4 CPUs and 8 GB of RAM.
Created on 01-11-2018 11:44 AM - edited 08-18-2019 01:10 AM
@Rafael Coss Cannot start the Web Shell Client nor running the "sandbox-version" command from SSH as it failed to open the "/opt/sandbox.info" file, so I looked for it myself.
Created on 01-11-2018 03:34 PM - edited 08-18-2019 01:10 AM
Screen capture of the behaviour with VMware Worstation Player 14.1.1, plus journalctl-xe-log.txt
Created 01-11-2018 03:37 PM
VMware Workstation is running on my Windows 10 laptop, with an i5 and 8 GB of RAM. VM was allocated 4 virtual CPUs and either 6 or 8 GB of RAM. Still the same behaviour with the rescue kernel. All the other two fail with no messages neither allowing to log in. I guess either I'm very short of resources or the latest HDP sandbox has serious errors.
Created 01-12-2018 03:33 AM
On boot, select the first kernel (3.10 non-rescue). The rescue option won't start the system with the appropriate resources/state to run the services that need to run.
If I understood your original post correctly, booting with the default kernel won't get you to a login screen and you may not immediately be able to visit http://<ip-address>:8888 (also try port 8080 [ambari] and port 4200 [ssh in the browser]). You're probably seeing a loading bar that seems to hang for a really long time. That's an issue that the current sandbox has and will be fixed in a very near-future release. Underneath the covers, though, services are started/starting - even though the screen appears for a while.
After a minute of booting up your VM, you should be able to navigate to <ip-add>:4200, :8080, and lastly :8888.
... However ...
The thing about VMWare (at least in most cases) is that it's not obvious what ip address the VM is given, so you have to wait until that Centos "loading bar" actually goes away, which depending on the machine could be upwards of 10minutes. I see your screenshots have an IP at the top - that *seems* to be it, though I've never used ESXi so I can't say for certain.
TL:DR; boot the first kernel, and give the VM a few minutes to do it's thing. It's getting fixed in an upcoming build.
Also, if you're okay not using ESXi for a bit, the VirtualBox/Docker versions of the sandbox.
Let me know how it goes or if I misunderstood and something else is also going wrong.