Hi all,
I am in the process of bringing up cloud foundry setup using BOSH for the
first time.

when i execute bosh micro deploy it got stuck at below point. I see a Vm
got created in AWS. I am not aware of which log file that i should check.
Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save state?
(type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light. Done
(00:00:35)

Started deploy micro bosh > Waiting for the agent

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH for the
first time.

when i execute bosh micro deploy it got stuck at below point. I see a Vm
got created in AWS. I am not aware of which log file that i should check.
Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save state?
(type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light. Done
(00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is there. I
brought up a VM manually then I was able to SSH to it. So i believe key is
correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM I run
BOSH>Custom
TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH for the
first time.

when i execute bosh micro deploy it got stuck at below point. I see a Vm
got created in AWS. I am not aware of which log file that i should check.
Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save state?
(type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light. Done
(00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the rule you
suggested. No luck yet :(

Sincerely,
Dulanjalie

--
Dulanjalie

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the rule you
suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com> wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is there. I
brought up a VM manually then I was able to SSH to it. So i believe key is
correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM I run
BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH for
the first time.

when i execute bosh micro deploy it got stuck at below point. I see a
Vm got created in AWS. I am not aware of which log file that i should
check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save
state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light.
Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

I tried. Allowed all the IPs. Still the same issue. Removed the VDC and
started all over again. Still the same issue. Is there any ruby/gem version
that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the rule
you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com> wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is there. I
brought up a VM manually then I was able to SSH to it. So i believe key is
correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM I run
BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <getourneau(a)pivotal.io

wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH for
the first time.

when i execute bosh micro deploy it got stuck at below point. I see a
Vm got created in AWS. I am not aware of which log file that i should
check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save
state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light.
Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the VDC and
started all over again. Still the same issue. Is there any ruby/gem version
that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the rule
you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com> wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is there. I
brought up a VM manually then I was able to SSH to it. So i believe key is
correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM I run
BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH
for the first time.

when i execute bosh micro deploy it got stuck at below point. I see
a Vm got created in AWS. I am not aware of which log file that i should
check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save
state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light.
Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the VDC and
started all over again. Still the same issue. Is there any ruby/gem version
that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the rule
you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com> wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is there. I
brought up a VM manually then I was able to SSH to it. So i believe key is
correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM I
run BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH
for the first time.

when i execute bosh micro deploy it got stuck at below point. I see
a Vm got created in AWS. I am not aware of which log file that i should
check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save
state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light.
Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

bosh task tasknumber --debug


On Wed, Jun 17, 2015 at 2:12 PM, Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
wrote:

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the VDC and
started all over again. Still the same issue. Is there any ruby/gem version
that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the rule
you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com> wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is there.
I brought up a VM manually then I was able to SSH to it. So i believe key
is correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM I
run BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH
for the first time.

when i execute bosh micro deploy it got stuck at below point. I
see a Vm got created in AWS. I am not aware of which log file that i should
check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save
state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light.
Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Hi Gwenn,
I executed "cfoundry(a)c-foundry:~/micro-deployment$ bosh tasks recent
--no-filter" to get the task number but i get "Please choose target first"
as the output. I am unable to get any logs because of this.

On Tue, Jun 16, 2015 at 10:29 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

bosh task tasknumber --debug


On Wed, Jun 17, 2015 at 2:12 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the VDC and
started all over again. Still the same issue. Is there any ruby/gem version
that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <getourneau(a)pivotal.io

wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the
rule you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com> wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is there.
I brought up a VM manually then I was able to SSH to it. So i believe key
is correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM I
run BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH
for the first time.

when i execute bosh micro deploy it got stuck at below point. I
see a Vm got created in AWS. I am not aware of which log file that i should
check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save
state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c
light. Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

Hi.

You won't get any information from bosh tasks while troubleshooting a bosh
micro deployment, because bosh micro plugin (used to deploy microbosh) does
not perform a regular BOSH deployment. There are no regular bosh tasks
involved (in fact, there is no director owning tasks because you are
deploying it).

I think you may get information from bosh_micro_deploy.log or
bosh-registry.log files (if they exist), generated at the directory from
which you launched bosh micro deploy.




2015-06-17 7:51 GMT+02:00 Dulanjalie Dhanapala <dulanjalie(a)gmail.com>:

Yes sorry, I forgot that you file a the micro bosh deployment, so you can
use the log file generated by bosh.

Thanks Gwenn and Pablo.
I have attached bosh-registry.log and bosh_micro_deploy.log herewith.

Thanks for your time.
Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 12:40 AM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Yes sorry, I forgot that you file a the micro bosh deployment, so you can
use the log file generated by bosh.

On Wed, Jun 17, 2015 at 4:24 PM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

Hi.

You won't get any information from bosh tasks while troubleshooting a
bosh micro deployment, because bosh micro plugin (used to deploy microbosh)
does not perform a regular BOSH deployment. There are no regular bosh tasks
involved (in fact, there is no director owning tasks because you are
deploying it).

I think you may get information from bosh_micro_deploy.log or
bosh-registry.log files (if they exist), generated at the directory from
which you launched bosh micro deploy.




2015-06-17 7:51 GMT+02:00 Dulanjalie Dhanapala <dulanjalie(a)gmail.com>:

Hi Gwenn,
I executed "cfoundry(a)c-foundry:~/micro-deployment$ bosh tasks recent
--no-filter" to get the task number but i get "Please choose target first"
as the output. I am unable to get any logs because of this.

On Tue, Jun 16, 2015 at 10:29 PM, Gwenn Etourneau <getourneau(a)pivotal.io

wrote:

bosh task tasknumber --debug


On Wed, Jun 17, 2015 at 2:12 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the VDC
and started all over again. Still the same issue. Is there any ruby/gem
version that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the
rule you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com>
wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is
there. I brought up a VM manually then I was able to SSH to it. So i
believe key is correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the VM
I run BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh
agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using
BOSH for the first time.

when i execute bosh micro deploy it got stuck at below point.
I see a Vm got created in AWS. I am not aware of which log file that i
should check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can
save state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done
(00:00:00)

Started deploy micro bosh > Uploading stemcell. Done
(00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c
light. Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

I brought up the VM that I used to issue boch micro command to AWS. I was
able to proceed.

Now i am hitting a different issue

when i execute bosh upload release
~/cf-deployment/cf-release/releases/cf-193.yml it fails with below
highlighted error. I have about 8.2G available space. Do you think this is
due to space issue. I allocate only 15G HD for this VM.

Generated /tmp/d20150617-7220-b7hvs5/d20150617-7220-nqf1mz/release.tgz

Release size: 3.5G

Verifying release...

File exists and readable OK

Extract tarball FAILED

Release is invalid, please fix, verify and upload again
Sincerely,
Dulanjalie





On Wed, Jun 17, 2015 at 8:36 AM, Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
wrote:

Thanks Gwenn and Pablo.
I have attached bosh-registry.log and bosh_micro_deploy.log herewith.

Thanks for your time.
Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 12:40 AM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Yes sorry, I forgot that you file a the micro bosh deployment, so you can
use the log file generated by bosh.

On Wed, Jun 17, 2015 at 4:24 PM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

Hi.

You won't get any information from bosh tasks while troubleshooting a
bosh micro deployment, because bosh micro plugin (used to deploy microbosh)
does not perform a regular BOSH deployment. There are no regular bosh tasks
involved (in fact, there is no director owning tasks because you are
deploying it).

I think you may get information from bosh_micro_deploy.log or
bosh-registry.log files (if they exist), generated at the directory from
which you launched bosh micro deploy.




2015-06-17 7:51 GMT+02:00 Dulanjalie Dhanapala <dulanjalie(a)gmail.com>:

Hi Gwenn,
I executed "cfoundry(a)c-foundry:~/micro-deployment$ bosh tasks recent
--no-filter" to get the task number but i get "Please choose target first"
as the output. I am unable to get any logs because of this.

On Tue, Jun 16, 2015 at 10:29 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

bosh task tasknumber --debug


On Wed, Jun 17, 2015 at 2:12 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the VDC
and started all over again. Still the same issue. Is there any ruby/gem
version that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added the
rule you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com>
wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is
there. I brought up a VM manually then I was able to SSH to it. So i
believe key is correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the
VM I run BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh
agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using
BOSH for the first time.

when i execute bosh micro deploy it got stuck at below point.
I see a Vm got created in AWS. I am not aware of which log file that i
should check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can
save state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable
OK

Verifying tarball...

Read tarball
OK

Manifest exists
OK

Stemcell image file
OK

Stemcell properties
OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done
(00:00:00)

Started deploy micro bosh > Uploading stemcell. Done
(00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c
light. Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

--
Dulanjalie

It seems that your local machine is running out of space.

On Wed, Jun 17, 2015 at 5:03 PM, Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
wrote:

I brought up the VM that I used to issue boch micro command to AWS. I was
able to proceed.

Now i am hitting a different issue

when i execute bosh upload release
~/cf-deployment/cf-release/releases/cf-193.yml it fails with below
highlighted error. I have about 8.2G available space. Do you think this is
due to space issue. I allocate only 15G HD for this VM.

Generated /tmp/d20150617-7220-b7hvs5/d20150617-7220-nqf1mz/release.tgz

Release size: 3.5G

Verifying release...

File exists and readable OK

Extract tarball FAILED

Release is invalid, please fix, verify and upload again
Sincerely,
Dulanjalie





On Wed, Jun 17, 2015 at 8:36 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Thanks Gwenn and Pablo.
I have attached bosh-registry.log and bosh_micro_deploy.log herewith.

Thanks for your time.
Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 12:40 AM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Yes sorry, I forgot that you file a the micro bosh deployment, so you
can use the log file generated by bosh.

On Wed, Jun 17, 2015 at 4:24 PM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

Hi.

You won't get any information from bosh tasks while troubleshooting a
bosh micro deployment, because bosh micro plugin (used to deploy microbosh)
does not perform a regular BOSH deployment. There are no regular bosh tasks
involved (in fact, there is no director owning tasks because you are
deploying it).

I think you may get information from bosh_micro_deploy.log or
bosh-registry.log files (if they exist), generated at the directory from
which you launched bosh micro deploy.




2015-06-17 7:51 GMT+02:00 Dulanjalie Dhanapala <dulanjalie(a)gmail.com>:

Hi Gwenn,
I executed "cfoundry(a)c-foundry:~/micro-deployment$ bosh tasks recent
--no-filter" to get the task number but i get "Please choose target first"
as the output. I am unable to get any logs because of this.

On Tue, Jun 16, 2015 at 10:29 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

bosh task tasknumber --debug


On Wed, Jun 17, 2015 at 2:12 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the
VDC and started all over again. Still the same issue. Is there any ruby/gem
version that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added
the rule you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com>
wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is
there. I brought up a VM manually then I was able to SSH to it. So i
believe key is correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the
VM I run BOSH>Custom TCP RuleTCP25555<IP of the VM I run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh
agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup using
BOSH for the first time.

when i execute bosh micro deploy it got stuck at below
point. I see a Vm got created in AWS. I am not aware of which log file that
i should check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can
save state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP
IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable
OK

Verifying tarball...

Read tarball
OK

Manifest exists
OK

Stemcell image file
OK

Stemcell properties
OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done
(00:00:00)

Started deploy micro bosh > Uploading stemcell. Done
(00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c
light. Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Agree you need more space..

On Thu, Jun 18, 2015 at 9:05 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

It seems that your local machine is running out of space.

On Wed, Jun 17, 2015 at 5:03 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I brought up the VM that I used to issue boch micro command to AWS. I was
able to proceed.

Now i am hitting a different issue

when i execute bosh upload release
~/cf-deployment/cf-release/releases/cf-193.yml it fails with below
highlighted error. I have about 8.2G available space. Do you think this is
due to space issue. I allocate only 15G HD for this VM.

Generated /tmp/d20150617-7220-b7hvs5/d20150617-7220-nqf1mz/release.tgz

Release size: 3.5G

Verifying release...

File exists and readable OK

Extract tarball FAILED

Release is invalid, please fix, verify and upload again
Sincerely,
Dulanjalie





On Wed, Jun 17, 2015 at 8:36 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Thanks Gwenn and Pablo.
I have attached bosh-registry.log and bosh_micro_deploy.log herewith.

Thanks for your time.
Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 12:40 AM, Gwenn Etourneau <getourneau(a)pivotal.io

wrote:

Yes sorry, I forgot that you file a the micro bosh deployment, so you
can use the log file generated by bosh.

On Wed, Jun 17, 2015 at 4:24 PM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

Hi.

You won't get any information from bosh tasks while troubleshooting a
bosh micro deployment, because bosh micro plugin (used to deploy microbosh)
does not perform a regular BOSH deployment. There are no regular bosh tasks
involved (in fact, there is no director owning tasks because you are
deploying it).

I think you may get information from bosh_micro_deploy.log or
bosh-registry.log files (if they exist), generated at the directory from
which you launched bosh micro deploy.




2015-06-17 7:51 GMT+02:00 Dulanjalie Dhanapala <dulanjalie(a)gmail.com>:

Hi Gwenn,
I executed "cfoundry(a)c-foundry:~/micro-deployment$ bosh tasks recent
--no-filter" to get the task number but i get "Please choose target first"
as the output. I am unable to get any logs because of this.

On Tue, Jun 16, 2015 at 10:29 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

bosh task tasknumber --debug


On Wed, Jun 17, 2015 at 2:12 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the
VDC and started all over again. Still the same issue. Is there any ruby/gem
version that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added
the rule you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com>
wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is
there. I brought up a VM manually then I was able to SSH to it. So i
believe key is correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of the
VM I run BOSH>Custom TCP RuleTCP25555<IP of the VM I run
BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh
agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup
using BOSH for the first time.

when i execute bosh micro deploy it got stuck at below
point. I see a Vm got created in AWS. I am not aware of which log file that
i should check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you
can save state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to
`https://<VIP IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable
OK

Verifying tarball...

Read tarball
OK

Manifest exists
OK

Stemcell image file
OK

Stemcell properties
OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done
(00:00:00)

Started deploy micro bosh > Uploading stemcell. Done
(00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c
light. Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Thanks guys. Let me reinstall with a larger VM.

Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 6:10 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Agree you need more space..

On Thu, Jun 18, 2015 at 9:05 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

It seems that your local machine is running out of space.

On Wed, Jun 17, 2015 at 5:03 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I brought up the VM that I used to issue boch micro command to AWS. I
was able to proceed.

Now i am hitting a different issue

when i execute bosh upload release
~/cf-deployment/cf-release/releases/cf-193.yml it fails with below
highlighted error. I have about 8.2G available space. Do you think this is
due to space issue. I allocate only 15G HD for this VM.

Generated /tmp/d20150617-7220-b7hvs5/d20150617-7220-nqf1mz/release.tgz

Release size: 3.5G

Verifying release...

File exists and readable OK

Extract tarball FAILED

Release is invalid, please fix, verify and upload again
Sincerely,
Dulanjalie





On Wed, Jun 17, 2015 at 8:36 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Thanks Gwenn and Pablo.
I have attached bosh-registry.log and bosh_micro_deploy.log herewith.

Thanks for your time.
Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 12:40 AM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Yes sorry, I forgot that you file a the micro bosh deployment, so you
can use the log file generated by bosh.

On Wed, Jun 17, 2015 at 4:24 PM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

Hi.

You won't get any information from bosh tasks while troubleshooting a
bosh micro deployment, because bosh micro plugin (used to deploy microbosh)
does not perform a regular BOSH deployment. There are no regular bosh tasks
involved (in fact, there is no director owning tasks because you are
deploying it).

I think you may get information from bosh_micro_deploy.log or
bosh-registry.log files (if they exist), generated at the directory from
which you launched bosh micro deploy.




2015-06-17 7:51 GMT+02:00 Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
:

Hi Gwenn,
I executed "cfoundry(a)c-foundry:~/micro-deployment$ bosh tasks
recent --no-filter" to get the task number but i get "Please choose target
first" as the output. I am unable to get any logs because of this.

On Tue, Jun 16, 2015 at 10:29 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

bosh task tasknumber --debug


On Wed, Jun 17, 2015 at 2:12 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the
VDC and started all over again. Still the same issue. Is there any ruby/gem
version that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added
the rule you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com>
wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue is
there. I brought up a VM manually then I was able to SSH to it. So i
believe key is correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of
the VM I run BOSH>Custom TCP RuleTCP25555<IP of the VM I
run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the bosh
agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup
using BOSH for the first time.

when i execute bosh micro deploy it got stuck at below
point. I see a Vm got created in AWS. I am not aware of which log file that
i should check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you
can save state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to
`https://<VIP IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable
OK

Verifying tarball...

Read tarball
OK

Manifest exists
OK

Stemcell image file
OK

Stemcell properties
OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done
(00:00:00)

Started deploy micro bosh > Uploading stemcell. Done
(00:00:09)

Started deploy micro bosh > Creating VM from
ami-3742b55c light. Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

Installation went thru fine. thanks again!

Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 8:46 PM, Dulanjalie Dhanapala <dulanjalie(a)gmail.com>
wrote:

Thanks guys. Let me reinstall with a larger VM.

Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 6:10 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Agree you need more space..

On Thu, Jun 18, 2015 at 9:05 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

It seems that your local machine is running out of space.

On Wed, Jun 17, 2015 at 5:03 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I brought up the VM that I used to issue boch micro command to AWS. I
was able to proceed.

Now i am hitting a different issue

when i execute bosh upload release
~/cf-deployment/cf-release/releases/cf-193.yml it fails with below
highlighted error. I have about 8.2G available space. Do you think this is
due to space issue. I allocate only 15G HD for this VM.

Generated /tmp/d20150617-7220-b7hvs5/d20150617-7220-nqf1mz/release.tgz

Release size: 3.5G

Verifying release...

File exists and readable OK

Extract tarball FAILED

Release is invalid, please fix, verify and upload again
Sincerely,
Dulanjalie





On Wed, Jun 17, 2015 at 8:36 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Thanks Gwenn and Pablo.
I have attached bosh-registry.log and bosh_micro_deploy.log herewith.

Thanks for your time.
Sincerely,
Dulanjalie

On Wed, Jun 17, 2015 at 12:40 AM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Yes sorry, I forgot that you file a the micro bosh deployment, so you
can use the log file generated by bosh.

On Wed, Jun 17, 2015 at 4:24 PM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

Hi.

You won't get any information from bosh tasks while troubleshooting
a bosh micro deployment, because bosh micro plugin (used to deploy
microbosh) does not perform a regular BOSH deployment. There are no regular
bosh tasks involved (in fact, there is no director owning tasks because you
are deploying it).

I think you may get information from bosh_micro_deploy.log or
bosh-registry.log files (if they exist), generated at the directory from
which you launched bosh micro deploy.




2015-06-17 7:51 GMT+02:00 Dulanjalie Dhanapala <dulanjalie(a)gmail.com

:

Hi Gwenn,
I executed "cfoundry(a)c-foundry:~/micro-deployment$ bosh tasks
recent --no-filter" to get the task number but i get "Please choose target
first" as the output. I am unable to get any logs because of this.

On Tue, Jun 16, 2015 at 10:29 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

bosh task tasknumber --debug


On Wed, Jun 17, 2015 at 2:12 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

whats the location of the log file?

Sincerely,
DUlanjalie

On Tue, Jun 16, 2015 at 10:11 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you provide the task debug logs please ?


On Wed, Jun 17, 2015 at 2:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the
VDC and started all over again. Still the same issue. Is there any ruby/gem
version that i need to have?

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 6:51 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Can you try using 0.0.0.0/0 as source IP ..
Just want to be sure SG are not the problem


On Wed, Jun 17, 2015 at 3:52 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Ken,
I execute "bosh micro deploy" from outside AWS. Still I added
the rule you suggested. No luck yet :(

Sincerely,
Dulanjalie

On Tue, Jun 16, 2015 at 10:32 AM, Ken Ojiri <ozzozz(a)gmail.com

wrote:

Hi Dulanjalie,

if you run 'bosh micro deploy' on a AWS VM(work VM),
I think you have to add a security group ingress setting
to the work VM as below:

| Custom TCP Rule | TCP | 25889 | bosh SG |

that is because the bosh-agent on MicroBOSH VM connects
to temporal BOSH registry on work VM (listens TCP25889 port).


Regards,
Ken


---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan

On Tue, Jun 16, 2015 at 10:08 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Gwenn,
I do not see any error in my sg settings. Still the issue
is there. I brought up a VM manually then I was able to SSH to it. So i
believe key is correct.

TypeProtocolPort RangeSourceCustom TCP RuleTCP6868<IP of
the VM I run BOSH>Custom TCP RuleTCP25555<IP of the VM I
run BOSH>
SSHTCP22<IP of the VM I run BOSH>
All TCPTCP0-65535SG itselfAll UDPUDP0-65535SG itself

Sincerely,
Dulanjalie


On Mon, Jun 15, 2015 at 6:25 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Please check security groups on AWS
http://bosh.io/docs/init-aws.html#create-security
Can be a communication issue between director and the
bosh agent.

On Tue, Jun 16, 2015 at 8:10 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi all,
I am in the process of bringing up cloud foundry setup
using BOSH for the first time.

when i execute bosh micro deploy it got stuck at below
point. I see a Vm got created in AWS. I am not aware of which log file that
i should check. Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved
in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you
can save state? (type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to
`https://<VIP IP>:25555' (type 'yes' to continue): yes


Verifying stemcell...

File exists and readable
OK

Verifying tarball...

Read tarball
OK

Manifest exists
OK

Stemcell image file
OK

Stemcell properties
OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done
(00:00:00)

Started deploy micro bosh > Uploading stemcell. Done
(00:00:09)

Started deploy micro bosh > Creating VM from
ami-3742b55c light. Done (00:00:35)

Started deploy micro bosh > Waiting for the agent

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

--
Dulanjalie

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

--
Dulanjalie

--
Dulanjalie

Good to know.