@Sujitha Subbiah Is there a particular reason you went for HDP 2.5? The 2.6.4 sandbox is out now and features more recent versions of underlying technologies that are more mature. ... View more

@Bill Brooks Hello, if this is still an issue at this time, could you please pastebin the logs from /var/log/ambari-server? ... View more

@SUBIN RAJU Hello, I believe this has to do with the memory constraints of the sandbox where it's usually staying at very close to 100% full. Also, there were issues we found and fixed regarding the Docker FS systems but there might have been some we missed. My recommendation is to use the latest sandbox since the underlying docker tech has evolved quite a bit in the last couple of months. ... View more

@Nikunj Solanki Hello, I just noticed this going over the opened issues. Your version of virtualbox is REALLY old, the latest version is 5.2.6. Could you please updated to the latest version and let us know if you're still getting issues? ... View more

@Hugo Koopmans The two issues you mentioned don't seem related to each other. Can you try using the default script and see if it works? ... View more

@Brandon Kirkland Helllo, What do you mean by 'unable to access the VM'? From what I read on your initial post ( adding in extra functionality ) I'm guessing you might be maxing out the memory of the machine which would explain the weird functionality. ... View more

@Ian Shrum Try connecting via SSH to the host machine ( ssh root@localhost -p2122 root/hadoop ) and then running docker ps to check if the docker container has been started. If so, from there login to the docker container ( ssh root@localhost -p2222 root/hadoop ) and run a ps ax command to check what processes are started. It's very strange that not even shellinabox is started ( port 4200 ), we haven't seen this behavior before. ... View more

@Anjal Naik Try looking at the ambari agent logs in /var/log/ambari-agent/ to see why it has a hard time connecting. Perhaps there is something there to explain the behavior. ... View more

Hello, @Wayne Deleersnyder in order for me to provide assistance I'm going to need more information. This isn't a bug we have run into and can't really replicate right now. A couple of questions: 1. Do you have the necessary 8GB of RAM needed by the box? 2. Did you try using virtualbox as well to see if you could replicate the issue? ... View more

@Moussa djamilou @Edmond AGBASSAGAN 1) The reason you're unable to connect via ssh is that the IP address is different. You can check that by running _> ip a sh The IP will be displayed, use that for the SSH command instead. 2) It seems that the docker daemon is not running. Do you have the minimum specs on your machine for it? You can try manually starting it up by running systemctl start docker and then running the start_sandbox.sh script again. ... View more

1.Try connecting to the host machine. a.For virtualbox: ssh root@localhost –p2122(password is hadoop) b.For vmware: ssh root@<ip_address>(password is hadoop) 2.Check to see if the docker container is running:[root@sandbox-host ~]# docker ps a.If it is running you should see something like this: [root@sandbox-host ~]# docker ps CONTAINER IDIMAGECOMMANDCREATEDSTATUSPORTSNAMES dd3b523063c1sandbox-hdp"/usr/sbin/sshd -D"15 hours agoUp 15 hours0.0.0.0:1000->1000/tcp, 0.0.0.0:1100->1100/tcp, 0.0.0.0:1220->1220/tcp, 0.0.0.0:1988->1988/tcp, 0.0.0.0:2049->2049/tcp, 0.0.0.0:2100->2100/tcp, 0.0.0.0:2181->2181/tcp, 0.0.0.0:3000->3000/tcp, 0.0.0.0:4040->4040/tcp, 0.0.0.0:4200->4200/tcp, 0.0.0.0:4242->4242/tcp, 0.0.0.0:5007->5007/tcp, 0.0.0.0:5011->5011/tcp, 0.0.0.0:6001->6001/tcp, 0.0.0.0:6003->6003/tcp, 0.0.0.0:6008->6008/tcp, 0.0.0.0:6080->6080/tcp, 0.0.0.0:6188->6188/tcp, 0.0.0.0:8000->8000/tcp, 0.0.0.0:8005->8005/tcp, 0.0.0.0:8020->8020/tcp, 0.0.0.0:8032->8032/tcp, 0.0.0.0:8040->8040/tcp, 0.0.0.0:8042->8042/tcp, 0.0.0.0:8080->8080/tcp, 0.0.0.0:8082->8082/tcp, 0.0.0.0:8086->8086/tcp, 0.0.0.0:8088->8088/tcp, 0.0.0.0:8090-8091->8090-8091/tcp, 0.0.0.0:8188->8188/tcp, 0.0.0.0:8443->8443/tcp, 0.0.0.0:8744->8744/tcp, 0.0.0.0:8765->8765/tcp, 0.0.0.0:8886->8886/tcp, 0.0.0.0:8888-8889->8888-8889/tcp, 0.0.0.0:8983->8983/tcp, 0.0.0.0:8993->8993/tcp, 0.0.0.0:9000->9000/tcp, 0.0.0.0:9090->9090/tcp, 0.0.0.0:9995-9996->9995-9996/tcp, 0.0.0.0:10000-10001->10000-10001/tcp, 0.0.0.0:10015-10016->10015-10016/tcp, 0.0.0.0:10500->10500/tcp, 0.0.0.0:10502->10502/tcp, 0.0.0.0:11000->11000/tcp, 0.0.0.0:15000->15000/tcp, 0.0.0.0:15002->15002/tcp, 0.0.0.0:15500-15505->15500-15505/tcp, 0.0.0.0:16000->16000/tcp, 0.0.0.0:16010->16010/tcp, 0.0.0.0:16020->16020/tcp, 0.0.0.0:16030->16030/tcp, 0.0.0.0:18080-18081->18080-18081/tcp, 0.0.0.0:19888->19888/tcp, 0.0.0.0:21000->21000/tcp, 0.0.0.0:33553->33553/tcp, 0.0.0.0:39419->39419/tcp, 0.0.0.0:42111->42111/tcp, 0.0.0.0:50070->50070/tcp, 0.0.0.0:50075->50075/tcp, 0.0.0.0:50079->50079/tcp, 0.0.0.0:50095->50095/tcp, 0.0.0.0:50111->50111/tcp, 0.0.0.0:60000->60000/tcp, 0.0.0.0:60080->60080/tcp, 0.0.0.0:2222->22/tcp, 0.0.0.0:1111->111/tcpsandbox-hdp b.If the container is not running, try to start it manually by running [root@sandbox-host ~]# /bin/bash start_scripts/start_sandbox.sh 3.Once it is up, try the connection to http://<ip_address>:8888 again ... View more

@Antonio Akiyama Hello, it looks like there is an issue with the network boot-up so that means the only way to debug is via single user mode. Can I suggest using one of our pre-built sandbox virtual machines? ( vmware/virtualbox ) We setup the environment for docker to run smoothly inside of them. ... View more

@Marshal Tito You're welcome! ... View more

@Marshal Tito Hello, I can't open that attached photo ( it says it has errors ). Please try allocating 11GB of Ram to the virtualbox and see if that fixes it. ... View more

That message seems to indicate that hive server is down ( if you can verify ). If that's the case, we would need the logs for hive server to further debug. Also note, the docker version is for advanced users, we recommend virtualbox/vmware versions for people that are just beginning. ... View more

Hello, Do you have the latest version of virtualbox? We noticed some quirks with previous versions. ... View more

Hello, There is no need to select anything on that screen as the bootloader will automatically select the first kernel which is the correct choice. Thanks for pointing this out, we will adapt future boxes so that that screen is not visible to create any further confusion. ... View more

Normally the /root/start_scripts/start_sandbox.sh is run at startup but from what you're telling me it seems like docker failed to start on the host machine. Can you please try running #> systemctl status docker? There might be information there regarding why docker is not running. Alternatively there should be docker logs in /var/log. ... View more

The login for the machine is root/hadoop on port 22 ( the host machine ) or the interface window of the vmware player. ... View more

You mentioned you are running the vmware version of it, so what I meant was login into the vmware host via port 22 and there you will have docker running ( hopefully ) the sandbox container. ... View more

From the vm host, can you please post the outputs of 'sudo docker ps' ? ... View more

Hello, @Philip du Plessis what are your computer specs? To me it sounds like the machine started but can't start all the required services. ... View more

Hello, @Philip du Plessis it seems you have the correct version of the sandbox however I cannot reproduce your issues. After importing the machine what are the exact steps you attempt? Please mind that there are 2 connection ports, the 2222 port leads to the docker container that's running the actual sandbox, it's here you need to go to run that find command. The 22 port is the virtual machine that hosts the docker container and therefore non of the actual sandbox code. ... View more

Hello, @Sadegh port 2222 leads to the docker container which runs the actual sandbox code. Port 22 leads to the virtual machine that hosts the running docker container. ... View more

@Sadegh hello, can you please check the docker container status on the vmware machine? You can do this by logging into the virtual machine via the window that pops up in vmware with (root/hadoop) and doing a docker ps. It should show a running container. From there, try logging in from there ( with ssh root@localhost -p2222 ). ... View more

Hello, @Philip du Plessis where did you download those versions? The correct place to download the latest bits is from https://hortonworks.com/downloads/#sandbox You can double check if you have the right version by doing a md5sum on the finished download and comparing it to the one listed next to it; in the case of vmware that is: d7bba72de7df82757fc9cc1f998fbe16 ... View more

@Arun Kumar M Why did you change your networking settings for it? By default it's set to NAT: ... View more

@Arun Kumar M Please explain what the issue is in more detail, from your screenshots the only thing I see is you've set your machine to a host-only network. ... View more

@pankaj kushwaha Making sure all the services are stopped and then doing a shutdown command from inside the host VM is your best bet at making sure nothing gets broken. ... View more

@Jonathan T The virtualbox and vmware versions of the sandbox are simply instances of virtualbox and vmware machines with the image pre-loaded onto them so if someone isn't accustomed to running scripts and/or installing docker on their machines they don't need to. Also docker so far isn't very OS friendly in that different distros present different bugs depending on flavors and kernel versions so downloading the vbox/vmware versions ensure that you're running it in an environment that was pre-screened to work accordingly. Regarding the behavior you are experiencing I can't really form on opinion by just the output you submitted but if I were to guess it would probably be a docker-related issue and perhaps your docker/ambari logs will provide more insight. Is everything else running alright now that you managed to bring it up? ... View more