Can no longer Login to Sandbox on Port 2222

[#1]

Hello Community,

Can someone let me know why for some reason I can no longer ssh to the Sandbox on port 2222?

Cheers

Carlton

[#2]

@Carlton Patterson

Please check if your Docker Container started fine or not?

For that you will need to login to your VM on port 2122. From here actually the docker container is started.

# ssh root@127.0.0.1  -p 2122
Enter Password : hadoop

.

Please check if the sandbox docker container is started properly or not?

# systemctl status sandbox.service
# docker ps -a
# cd /root/start_scripts
# ./start_sandbox.sh

.

[#3]

Hi Jay,

Going to check that now .. stay with me mate

[#4]

Hi Jay,

Please take a look at the screen shot when I attempt your suggestion

[#5]

@Carlton Patterson

Looks like you are already inside the "root@sandbox-host" so from there ssh to 2122 will not work.

If you want to login to the VM where the Docker is starting then you will need to do SSH to port 2122 form your Laptop.

If that too does not work then please try to power off the Virtualbox instance and then Start it freshly.

[#6]

Hi Jay,

Will a reboot allow me to enter on port 2222 ? At the moment I keep on getting the error below

[#7]

@Carlton Patterson

I have a quick query ... Which host is this "root@sandbox-host" which we see in your terminal? (Is it your latrop host)

Are you able to do ssh to port 2122 form your laptop?

[#8]

Hi Jay,

It's hosted on ESXi 5.5 and I access it using vSphere client

[#9]

Hi Jay,

Another other thoughts?

[#10]

@Carlton Patterson

For example:

From my physical machine i do this:

localmachine:~ jsensharma$ ssh root@127.0.0.1 -p 2122
root@127.0.0.1's password:  hadoop

Then i am able to login to the VM and can see the following prompt where i run the below set of commands:

[root@sandbox-host ~]# 

.

Checking if docker is running? And you see that port 2222 is mapped as "0.0.0.0:2222->22"

# docker ps -a
CONTAINER ID  IMAGE  COMMAND  CREATED  STATUS  PORTS  NAMES
abf422a247dc
  sandbox  "/usr/sbin/sshd -D"  6 days ago  Up 4 minutes  
0.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:7777->7777/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/tcp  sandbox

I see that the docker container is running.

[#11]

Hi Jay,

I have highlighted port 2222 from the command you suggested, see image

[#12]

@Carlton Patterson

Yes, based on your last comment it looks like port 2222 is mapped properly and also the docker container is running fine. So this looks strange.

I am running out of ideas right now. But two last things i will try:

1. I will check the network port forwarding if virtualbox has the port forwarding on 2222 enabled properly ( By default it has .. until some one changes it).

VirtualBox --> HDP 2.6 Sandbox --> Setings --> Network --> Adapter 1 --> Advanced --> Port Forwarding

2. I will try to Shutdown the Sandbox completely and then will start it again.

.

[#13]

Jay,

I just found the following link that might explain it

https://github.com/hortonworks/data-tutorials/issues/411

[#14]

Hi Jay,

I think I'm going to call it a night. Thanks for your help tonight mate.

I think the only solution left is a complete rebuild

[#15]

Hi Jay,

I think I'm going to call it a night. Thanks for your help tonight mate.

I think the only solution left is a complete rebuild