"bosh ssh" times out


Remi Tassing
 

Hi,
I was trying "bosh ssh" in the interactive mode and after choosing the VM it hangs for a bit then times out. I was following this tutorial: http://docs.pivotal.io/pivotalcf/customizing/trouble-advanced.html

Console snippet:
....
13. stats_z1/0
Choose an instance: 1
Acting as user 'admin' on deployment 'cf' on 'microbosh'
Enter password (use it to sudo on remote host): *
Target deployment is `cf'

Setting up ssh artifacts

Director task 43

Task 43 done
Starting interactive shell on job nats_z1/0
ssh: connect to host 10.0.16.103 port 22: Connection timed out
...

Has anyone encountered this problem? Is there other alternative?

Remi


Daniel Mikusa
 

Have you checked that the connection is not being blocked by a firewall?
What happens if you SSH directly to that IP?

Dan

On Thu, Oct 8, 2015 at 11:22 AM, Remi Tassing <tassingremi(a)gmail.com> wrote:

Hi,
I was trying "bosh ssh" in the interactive mode and after choosing the VM
it hangs for a bit then times out. I was following this tutorial:
http://docs.pivotal.io/pivotalcf/customizing/trouble-advanced.html

Console snippet:
....
13. stats_z1/0
Choose an instance: 1
Acting as user 'admin' on deployment 'cf' on 'microbosh'
Enter password (use it to sudo on remote host): *
Target deployment is `cf'

Setting up ssh artifacts

Director task 43

Task 43 done
Starting interactive shell on job nats_z1/0
ssh: connect to host 10.0.16.103 port 22: Connection timed out
...

Has anyone encountered this problem? Is there other alternative?

Remi


Remi Tassing
 

Hi Daniel,
10.0.16.103 is the internal address of that particular VM within the VPC (I've deployed CF in AWS). So I can't access it directly.
I thought that was the point of using "bosh ssh", i.e., connecting to the ha_proxy (which has a public address) first and then to the VM.

I have a feeling I've completed missed the point

Remi


Daniel Mikusa
 

I was under the impression that you need to be able to connect directly,
but I can't say that definitively. Perhaps someone else can confirm.

Dan

On Thu, Oct 8, 2015 at 11:43 AM, Remi Tassing <tassingremi(a)gmail.com> wrote:

Hi Daniel,
10.0.16.103 is the internal address of that particular VM within the VPC
(I've deployed CF in AWS). So I can't access it directly.
I thought that was the point of using "bosh ssh", i.e., connecting to the
ha_proxy (which has a public address) first and then to the VM.

I have a feeling I've completed missed the point

Remi


Jim Park
 

You can proxy through the director or whatever else if you'd like with
`bosh ssh --gateway_host director.example.com --gateway_user vcap
--gateway_identity_file /path/to/bosh_directors_key`.

BOSH director only manages creating a one-time use user login with sudo
privileges and passes it back to bosh_cli.

We use a bastion host to perform BOSH-ey things because of this.

Thanks,


Jim

On Thu, Oct 8, 2015 at 8:49 AM Daniel Mikusa <dmikusa(a)pivotal.io> wrote:

I was under the impression that you need to be able to connect directly,
but I can't say that definitively. Perhaps someone else can confirm.

Dan


On Thu, Oct 8, 2015 at 11:43 AM, Remi Tassing <tassingremi(a)gmail.com>
wrote:

Hi Daniel,
10.0.16.103 is the internal address of that particular VM within the VPC
(I've deployed CF in AWS). So I can't access it directly.
I thought that was the point of using "bosh ssh", i.e., connecting to the
ha_proxy (which has a public address) first and then to the VM.

I have a feeling I've completed missed the point

Remi


Amit Kumar Gupta
 

You can use your bosh director as a gateway:

bosh ssh --gateway-host ADDRESS-OF-DIRECTOR --gateway-user vcap

On Thursday, October 8, 2015, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:

I was under the impression that you need to be able to connect directly,
but I can't say that definitively. Perhaps someone else can confirm.

Dan


On Thu, Oct 8, 2015 at 11:43 AM, Remi Tassing <tassingremi(a)gmail.com
<javascript:_e(%7B%7D,'cvml','tassingremi(a)gmail.com');>> wrote:

Hi Daniel,
10.0.16.103 is the internal address of that particular VM within the VPC
(I've deployed CF in AWS). So I can't access it directly.
I thought that was the point of using "bosh ssh", i.e., connecting to the
ha_proxy (which has a public address) first and then to the VM.

I have a feeling I've completed missed the point

Remi


Remi Tassing
 

Jim, you are my savior, that worked perfectly. I did see those parameters and if I was smart enough I should have figured it out myself. But since I was following a tutorial I thought it wouldn't be that 'hard'.
Thanks mate!!


Remi Tassing
 

Amit: I tried this but it didn't work. I needed to add the "gateway_identity_file" as suggested by Jim. Thanks anyway!