Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 01-30-2018 04:57 AM
I am not able to open Http connect to zeppelin on my sandbox.
I am using Virtualbox. Here are things I have tried.
-- Added port 9995 to port forwarding under network under settings.
--Use either localhost:9995, 127.0.0.1:9995 or sandbox-hdf.hortonworks.com:9995
--Restarted zeppelin a few times. Running service check returns no error. Looks like zeppelin server is running.
--Tried to update group owner from hadoop to zeppelin on folder (and subfolder) /usr/hdp/2.6.3.0-235/zeppelin/webapps/
The error I get in Chrome:
This site can't be reached.
The connect was reset.
Not sure what else to try.
Thanks
Long
Created 02-01-2018 04:55 AM
Final resolved the issue after following steps in this link.
https://hortonworks.com/tutorial/sandbox-port-forwarding-guide/
Looks like in addition to open port in Virtualbox, I also had to open port in docker image.
The only thing is that the start script is actually under /sandbox not /root. Also the file to modify is /sandbox/sandbox-deploy.sh
Also I was not able to save my current VM image so after I ran the commands the VM images was re-initialized. So I had to re-configure everything again. I did not run docker commit as instructed. It took some time to run, but I have no idea what was saved and why I was not able to use saved VM image.
Created 01-30-2018 04:58 AM
The VM image I am using: HDF_3.0.2.0.virtualbox_28_11_2017.ova
Created 01-31-2018 09:07 AM
@Long M Can you try ambari quick link to access the zeppelin UI. Attaching the screenshot so that its more evident.
Created 02-01-2018 04:55 AM
Final resolved the issue after following steps in this link.
https://hortonworks.com/tutorial/sandbox-port-forwarding-guide/
Looks like in addition to open port in Virtualbox, I also had to open port in docker image.
The only thing is that the start script is actually under /sandbox not /root. Also the file to modify is /sandbox/sandbox-deploy.sh
Also I was not able to save my current VM image so after I ran the commands the VM images was re-initialized. So I had to re-configure everything again. I did not run docker commit as instructed. It took some time to run, but I have no idea what was saved and why I was not able to use saved VM image.
Created 02-01-2018 04:56 AM
I did run docker commit