Support Questions
Find answers, ask questions, and share your expertise

HDP 2.5 Sandbox not starting

Super Collaborator

Hi,

Today I downloaded the Sandbox from http://hortonworks.com/downloads/#sandbox When I start it though it seems like some but not all components are launched. First the Virtualbox screen is stuck in this mode:

7851-screen-shot-2016-09-21-at-94723-pm.png

When you hit a button I get more info:

7852-screen-shot-2016-09-21-at-94624-pm.png

The time counter just runs forever. By this time the Ambari login screen is up and the YARN app WebUI on 8088 as well, but that is it. It is stuck on start up. What is going on?

UPDATE

7892-screen-shot-2016-09-22-at-71256-am.png

After 36 minutes it it still doing something

1 ACCEPTED SOLUTION

Super Collaborator

Well, I turned to the Docker version instead. That one is working!

View solution in original post

33 REPLIES 33

Rising Star

@ Jasper How much RAM is in the host machine? The newer sandbox has a lot of components in it and typically needs about 8GB of RAM allocated to it in order to run right. One other thing I've noticed is that the 2.5 sandbox takes longer to start than the earlier ones, but after 6+ minutes you should see some progress.

Super Collaborator

I have 8GB allocated. Longest time I ran the start up was well over 12 min.

New Contributor

@Jasper Even i have the same problem as yours ,my host machine is 16gb , i thought it was related to network settings and troubleshooting for past 2 days but couldn't figure out . If anyone has fixed the pbm please help me out.

Can you provide details to your Network settings of VM ? I did face issue getting my VM up due to Network issue. I got it working now.

New Contributor

Having the same problem but my host machine has 8gb. I can only allocate about 5gb max.

Neil, with 8GB of RAM in the localhost it won't work, it hangs, I tried it and it dint work until I upgraded my RAM capacity to 12 GB.

Super Collaborator

Well, I turned to the Docker version instead. That one is working!

Hi, I did a lot of work on HDP 2.4 sandbox on VMWare Player and it worked like charm. I decided to download the HDP 2.5 (to check out the latest offerings) and that too the Virtualbox image and thats when all my troubles began . All hell breaks loose in acquiring an IP address for guest machine. Attached are screenshots for Network Options

8449-default-settings-hdp2-5.jpg

and the final outcome when VM is up after around 10-15 minutes on my machine (i7 Dual Core, 16 Gb RAM) is that

127.0.0.1:8888 IP generated.

And putty fails to connect to this IP .

My questions -

1) Why is it unable to generate a proper IP like it did for HDP 2.4 on VMware (am i doing something wrong)

2) How to get putty to connect to this IP (if at all possible)

What's the deal with docker version ? Can we use it like VM ?

Rising Star

The move to docker, meant we had to upgrade the operating system to Centos 7 which is a requirement for Docker. Doing so added this change of not being able to see the step by step progress of the bootup. On virtualbox, if you click inside the console of the VM and type an arrow key, you should see the progress. Typically the initial boot up sequence takes about 3.5 minutes if you have a Core I7 2.3GHZ with 16 GB of physical memory. We are continuing to look into improving the experience.

@Jasper @Neil Prakasam @Mike Riggs - I was able to get the HDP 2.5 Virtual Machine up on VirtualBox and it took around 5-7 minutes. I kept the default memory allocation to 8 GB but once the VM was up, my RAM utilization went up to around 12 GB . So I think the recommended memory should be 16 GB for VM to perform properly on a Windows 10 machine with i7 Dual Core processors.

Expert Contributor

Hello All - I'm having the same issue with the 2.5 Sandbox ..

I've worked with the sandbox earlier, and it was starting up (though taking much longer than 2.4) .. but today it seems to be just hanging.. any idea what needs to be done ?

I've a Mac with 16GB RAM.

Expert Contributor

attaching screenshot of the sandboxscreen-shot-2016-11-09-at-112408-pm.png

@Karan Alang - Please hit the "down" arrow key when your VM boots up to see which process is your boot sequence stuck on.

Only then can we see what's going on. Down arrow acts like a toggle key to show or hide the background daemons/processes getting started. If your VM is stuck on starting docker container then something has gone corrupt in your VM since 16Gb RAM and a good processor should be fine to get ti working in 5-8 minutes.

Expert Contributor

@Nitin Saraswat,

Thanks for response.. pls see screenshot with an error ..

Pls let me know if this is an issue, and what needs to be done ?

Sandbox is still starting up after 10-15 minsscreen-shot-2016-11-10-at-104903-am.png

Expert Contributor

@Nitin Saraswat

Additional logs (VBox.log)

Karans-MacBook-Pro-3:Logs karanalang$ tail -50 VBox.log 00:00:09.267120 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=86 00:00:09.267436 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=87 00:00:09.267729 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=87 00:00:09.268053 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=88 00:00:09.268365 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=88 00:00:09.268680 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=89 00:00:09.268974 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=89 00:00:09.269289 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8a 00:00:09.269584 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8a 00:00:09.269901 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8b 00:00:09.270196 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8b 00:00:09.270607 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8c 00:00:09.270906 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8c 00:00:09.271200 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8d 00:00:09.271475 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8d 00:00:09.271769 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8e 00:00:09.272043 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8e 00:00:09.272337 VMMDev: Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8f 00:00:09.272612 VMMDev: Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8f 00:00:09.419937 GIM: KVM: VCPU 0: Enabled system-time struct. at 0x000000021ff83000 - u32TscScale=0xbda12f6d i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x50762cf37 uVirtNanoTS=0x1dcd2046d 00:00:09.419999 TM: Switching TSC mode from 'VirtTscEmulated' to 'RealTscOffset' 00:00:09.667554 GIM: KVM: Enabled wall-clock struct. at 0x0000000001c6ff08 - u32Sec=1478801606 u32Nano=905054757 uVersion=2 00:00:09.727196 PIT: mode=2 count=0x4a9 (1193) - 1000.15 Hz (ch=0) 00:00:09.880403 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0) 00:00:09.895191 GIM: KVM: VCPU 1: Enabled system-time struct. at 0x000000021ff83040 - u32TscScale=0xbda12f6d i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x50762cf37 uVirtNanoTS=0x1dcd2046d 00:00:09.909969 GIM: KVM: VCPU 2: Enabled system-time struct. at 0x000000021ff83080 - u32TscScale=0xbda12f6d i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x50762cf37 uVirtNanoTS=0x1dcd2046d 00:00:09.926711 GIM: KVM: VCPU 3: Enabled system-time struct. at 0x000000021ff830c0 - u32TscScale=0xbda12f6d i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x50762cf37 uVirtNanoTS=0x1dcd2046d 00:00:10.123431 OHCI: Software reset 00:00:10.380271 OHCI: USB Reset 00:00:10.430578 OHCI: Software reset 00:00:10.430702 OHCI: USB Operational 00:00:11.070707 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xc4 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:00:11.070770 PIIX3 ATA: Ctl#0: finished processing RESET 00:00:11.071194 PIIX3 ATA: Ctl#1: RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago) 00:00:11.071269 PIIX3 ATA: Ctl#1: finished processing RESET 00:00:14.084596 NAT: IPv6 not supported 00:00:14.179503 NAT: DHCP offered IP address 10.0.2.15 00:00:16.068282 NAT: Link up 00:00:50.066652 NAT: DHCP offered IP address 10.0.2.15 00:00:54.700790 NAT: Link up 00:05:38.346443 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices 00:05:47.904933 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices 00:12:17.096962 GUI: UIMediumEnumerator: Medium-enumeration started... 00:12:17.323011 GUI: UIMediumEnumerator: Medium-enumeration finished! 00:12:42.310920 PIIX3 ATA: execution time for ATA command 0xca was 9 seconds 00:12:52.575301 PIIX3 ATA: execution time for ATA command 0xca was 8 seconds 00:13:49.375336 PIIX3 ATA: execution time for ATA command 0xca was 8 seconds 00:30:14.732950 NAT: DHCP offered IP address 10.0.2.15 00:30:19.588913 NAT: Link up 00:47:37.856692 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices Karans-MacBook-Pro-3:Logs karanalang$

Expert Contributor

I re-downloaded the Sandox & re-imported into VirtualBox - and am able to start the SanbBox now.. i guess the earlier SandBox was corrupted .. Unfortunately, the earlier changes i made are lost now 😞

Sorry to hear that @Karan Alang . But its always a good practice to copy the scripts and codes to your local machine or a repository using Filezilla or other FTP application.

New Contributor

I downloaded the 2.5 Sandbox and I have not been able to get it to run. The sandbox failed to start with error message something about vboxadd-service. Do you know what this mean? It looked like they posted a bad image of the sandbox? Thanks.

10201-hdp25error.png

Explorer

Hi Kho, did you manage to get past this error or issue? I just downloaded HDP 2.5 sandbox (11.1GB) from the following link: https://s3.ap-south-1.amazonaws.com/hwx-sandbox-distribution-apsouth1/images/HDP_2.5_vmware.ova and a VM Player version 12 (selected HOST only instead of NAT). Imported the sandbox, and selected the second CentOS 7 image. Booted successfully iun 12-15 mins. (I am using Thinkpad w530, allocated 4GB out of 8GB RAM max I have, core i7, speed 2.65 GHz, 4th gen processor) ... everything worked like a charm! I think your sandbox image is "incomplete". Try to re-download the image from that link which I received from Hortonworks guy yesterday! I am a novice and exploring HDP!

New Contributor

@Madhav Gudimetla i'm stuck on the same issue for past 2 days.. it was working before for several months with same configuration.. please help if solved the issue..

; ;