Re: bosh micro deploy stuck at Started deploy micro bosh > Waiting for the agent


Pablo Alonso Rodriguez <palonsoro@...>
 

Buf. It is getting hard.

Are you using the same password for users ccadmin and uaadmin at roles
subsection of ccdb section, uuadb section and databases section of the
global properties?

I mean, in the following snippets

ccdb:
address: 10.0.16.101
databases:
- {name: ccdb, tag: cc}
db_scheme: postgres
port: 5524
roles:
- {name: ccadmin, password: PASSWORD1, tag: admin}
...
databases:
databases:
- {name: ccdb, tag: cc, citext: true}
- {name: uaadb, tag: uaa, citext: true}
port: 5524
roles:
- {name: ccadmin, password: PASSWORD1, tag: admin}
- {name: uaaadmin, password: PASSWORD2, tag: admin}
...
uaadb:
address: 10.0.16.101
databases:
- {name: uaadb, tag: uaa}
db_scheme: postgresql
port: 5524
roles:
- {name: uaaadmin, password: PASSWORD2, tag: admin}
...

Are PASSWORD1 and PASSWORD2 the same actual passwords in your actual
manifest in the places I have shown?
El 24/06/2015 19:13, "Dulanjalie Dhanapala" <dulanjalie(a)gmail.com>
escribi├│:

Hi all,
I deleted my "cf" deployment
git cloned the latest https://github.com/cloudfoundry/cf-release.git

I am using the latest stemcells 2999

+-----------------------------------------+---------+--------------------+

| Name | Version | CID |

+-----------------------------------------+---------+--------------------+

| bosh-aws-xen-hvm-ubuntu-trusty-go_agent | 2989 | ami-8bc83be0 light |

| bosh-aws-xen-hvm-ubuntu-trusty-go_agent | 2999* | ami-4dcc3526 light |

+-----------------------------------------+---------+--------------------+

(*) Currently in-use

Finally, i am using 212 release

bosh releases

+------+----------+-------------+

| Name | Versions | Commit Hash |

+------+----------+-------------+

| cf | 193 | 54613ebb+ |

| | 212* | ae2ec7a5+ |

+------+----------+-------------+

(*) Currently deployed

(+) Uncommitted changes

Still fails with

Failed updating job api_z1 > api_z1/0 (canary): `api_z1/0' is not
running after update (00:12:18)

Error 400007: `api_z1/0' is not running after update


But error logs are different:
http://fpaste.org/236236/65314143/
http://fpaste.org/236241/16579314/

Still "Buildpacks installation failed"

Sincerely,
Dulanjalie



On Wed, Jun 24, 2015 at 6:34 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Thanks a lot Pablo, Lev and Nic. I will give this a try ...

Sincerely,
Dulanjalie

On Wed, Jun 24, 2015 at 6:32 AM, Dr Nic Williams <drnicwilliams(a)gmail.com
wrote:
It's not necessary to change tag to recreate a final release or upload
it. The cf-212.yml is permanent in the repo (unless someone removes it) and
can be used from any commit.

You will want to change git tags to get the correct spiff templates or
example manifests at the time of the release.




On Wed, Jun 24, 2015 at 6:28 AM, Lev Berman <lev.berman(a)altoros.com>
wrote:

The newest stable release (as well as any other production release)
has to be built not from the master branch but from the corresponding tag -
for the release 212 it is v212:

git checkout v212
./update
bosh upload release $CF_RELEASE_DIR/releases/cf-212.yml

Or, alternatively, it can be uploaded from bosh.io -
http://bosh.io/releases/github.com/cloudfoundry/cf-release

On Wed, Jun 24, 2015 at 10:04 AM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

I see two possibilities here: A Cloud Controller database corruption
(due to previous errors) or a version mismatch. I think more of the latter
because staticfiles_buildpack and binary_buildpack have been added in
recent versions of cf-release (if I am not wrong).

Please try the following: Start by deleting your deployment via 'bosh
delete deployment cf' (if your deployment name is not cf, put the actual
name).

Then, be 100% sure that your cf-release is up-to-date. To do so, be
sure to check out the most recent commit of the master branch of the
cf-release repo (clone it again, run git pull...). Then, launch the
'./update' script (from the cf_release folder) to update all the submodules
(not doing so would lead you to serious problems).

Then, you should delete the previous release via: bosh delete release
cf

After that, upload the newest release via: bosh upload release
$CF_RELEASE_DIR/releases/cf-212.yml

Once done, try deploying again.

If this does not solve the problem, I am not sure about what more to
do.

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

I see this error too

/var/vcap/sys/log/cloud_controller_worker_ctl.log

{"timestamp":1435092330.8114371,"message":"No file found for the
buildpack: {\"name\"=>\"staticfile_buildpack\",
\"package\"=>\"buildpack_staticfile\"}","log_level":"error","source":"cc.install_buildpacks","data":{},"thread_id":70024832586540,"fiber_id":70024862640480,"process_id":9076,"file":"/var/vcap/data/packages/cloud_controller_ng/27a4f1b135a8415d623996c6f3a7c668801d1ea3.1-2c0961678c940361c8069ddcac42449d59c222c9/cloud_controller_ng/lib/cloud_controller/install_buildpacks.rb","lineno":31,"method":"block
in install"}

{"timestamp":1435092330.8116693,"message":"No file found for the
buildpack: {\"name\"=>\"binary_buildpack\",
\"package\"=>\"buildpack_binary\"}","log_level":"error","source":"cc.install_buildpacks","data":{},"thread_id":70024832586540,"fiber_id":70024862640480,"process_id":9076,"file":"/var/vcap/data/packages/cloud_controller_ng/27a4f1b135a8415d623996c6f3a7c668801d1ea3.1-2c0961678c940361c8069ddcac42449d59c222c9/cloud_controller_ng/lib/cloud_controller/install_buildpacks.rb","lineno":31,"method":"block
in install"}


Sincerely,

Dulanjalie

On Tue, Jun 23, 2015 at 1:42 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

no luck yet. Below are the logs i found which seems be errors. You
can find my minimal-aws.yml @ http://fpaste.org/235921/14350920/

------------ STARTING cloud_controller_ng_ctl at Tue Jun 23
20:31:59 UTC 2015 --------------

Deprecated: Use -s or --insert-seed flag

Killing
/var/vcap/sys/run/cloud_controller_ng/cloud_controller_ng.pid: 27490

.Stopped

------------ STARTING cloud_controller_ng_ctl at Tue Jun 23 20:23:37
UTC 2015 --------------

/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/steno-1.2.4/lib/steno/logger.rb:107:in
`synchronize': can't be called from trap context (ThreadError)

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/steno-1.2.4/lib/steno/logger.rb:107:in
`level_active?'

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/steno-1.2.4/lib/steno/logger.rb:127:in
`log'

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/steno-1.2.4/lib/steno/logger.rb:27:in
`block in define_log_method'

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/lib/cloud_controller/runner.rb:126:in
`block in trap_signals'

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`call'

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`run_machine'

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`run'

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/lib/cloud_controller/runner.rb:84:in
`run!'

from
/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/bin/cloud_controller:12:in
`<main>'



1.
=====================cloud_controller_clock_ctl.log===========================

{"timestamp":1435090093.8208199,"message":"PG::UndefinedTable:
ERROR: relation \"billing_events\" does not exist\nLINE 1: SELECT * FROM
\"billing_events\" LIMIT 1\n ^: SELECT * FROM
\"billing_events\" LIMIT
1","log_level":"error","source":"cc.background","data":{},"thread_id":69901722751800,"fiber_id":69901752205980,"process_id":2568,"file":"/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/sequel-4.15.0/lib/sequel/database/logging.rb","lineno":70,"method":"block
in log_each"}

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

Thanks a million Pablo for the response. Let me give this a try.

Sincerely,
Dulanjalie

On Tue, Jun 23, 2015 at 10:23 AM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

Having a look at your cloud_controller_worker_ctl.log file, the
error seems to happen at the default buildpacks installation process. This
typically comes from an issue with the cloud controller blobstore.

The cloud controller blobstore can be any storage backend
supported by Fog ruby library. By default, an NFS server is deployed within
the CF deployment (the nfs_z1) and used (this is also your case). However,
NFS is quite unstable and leads to issues like this.

As you are deploying CF at Amazon, the best solution would be to
set up the blobstore to use a S3 bucket. To do so, first setup a new bucket
on your S3 account. Then, go to the cc: subsection of the properties: main
section of your manifest and put the following properties into it:

cc:
buildpacks:
buildpack_directory_key: cfBucket
cdn: null
fog_connection:
provider: 'AWS'
aws_access_key_id: ACCESS_KEY
aws_secret_access_key: SECRET
droplets:
cdn: null
droplet_directory_key: cfBucket
fog_connection:
provider: 'AWS'
aws_access_key_id: ACCESS_KEY
aws_secret_access_key: SECRET
packages:
app_package_directory_key: cfBucket
cdn: null
fog_connection:
provider: 'AWS'
aws_access_key_id: ACCESS_KEY
aws_secret_access_key: SECRET
resource_pool:
cdn: null
resource_directory_key: cfBucket
fog_connection:
provider: 'AWS'
aws_access_key_id: ACCESS_KEY
aws_secret_access_key: SECRET

Where

- cfBucket is the name of your bucket
- ACCESS_KEY is the S3 access key id
- SECRET is the secret access key

Please be sure that your credentials have writing permissions.

If you have issues deploying this, try deleting the deployment and
deploying again.

Once everything works fine, you can remove the NFS VM. To do so,
replace this

- name: nfs_z1
instances: 1
persistent_disk: 102400
resource_pool: small_z1
templates:
- {name: debian_nfs_server, release: cf}
- {name: metron_agent, release: cf}
networks:
- name: cf_private
static_ips: [10.0.16.105]

With this:

- name: nfs_z1
instances: 0
persistent_disk: 102400
resource_pool: small_z1
templates:
- {name: debian_nfs_server, release: cf}
- {name: metron_agent, release: cf}
networks:
- name: cf_private
#static_ips: [10.0.16.105]



I see this error related to api_z1 in
the ./cloud_controller_worker_ctl.log

./cloud_controller_worker_ctl.log:{"timestamp":1434996874.6546366,"message":"(0.003843s)
UPDATE \"delayed_jobs\" SET \"guid\" =
'a3af8feb-30b7-4b4d-91fd-112045501a0d', \"created_at\" = '2015-06-22
18:14:32.651086+0000', \"updated_at\" = CURRENT_TIMESTAMP, \"priority\" =
0, \"attempts\" = 0, \"handler\" = '---
!ruby/struct:VCAP::CloudController::Jobs::ExceptionCatchingJob\nhandler:
!ruby/struct:VCAP::CloudController::Jobs::RequestJob\n job:
!ruby/struct:VCAP::CloudController::Jobs::TimeoutJob\n job:
!ruby/struct:VCAP::CloudController::Jobs::Runtime::BuildpackInstaller\n
name: java_buildpack\n file:
\"/var/vcap/packages/buildpack_java/java-buildpack-v2.5.zip\"\n opts:
{}\n config: \n request_id: \n', \"last_error\" = NULL, \"run_at\" =
'2015-06-22 18:14:32.660520+0000', \"locked_at\" = '2015-06-22
18:14:34.649651+0000', \"failed_at\" = NULL, \"locked_by\" = 'cc_api_worker.
*api_z1*.0.2', \"queue\" = 'cc-*api_z1*-0', \"cf_api_error\" =
NULL WHERE (\"id\" =
1)","log_level":"debug2","source":"cc.background","data":{},"thread_id":69964119192340,"fiber_id":69964148702360,"process_id":2727,"file":"/var/vcap/packages/cloud_controller_ng/cloud_controller_ng/vendor/bundle/ruby/2.1.0/gems/sequel-4.15.0/lib/sequel/database/logging.rb","lineno":70,"method":"block
in log_each"}


I searched online but it seems like there are some others hitting
the same issue. I could not find a proper solution. One suggestion was to
increase the VM size so i changed it to m3.large. It didnt help.


Please help


Sincerely

Dulanjalie

On Sun, Jun 21, 2015 at 4:11 PM, James Bayer <jbayer(a)pivotal.io>
wrote:

typically you need to log into with "bosh ssh api_z1/0" and look
at the logs to see why the job did not start.

there are usually logs relating to what went wrong in
/var/vcap/sys/log

On Sun, Jun 21, 2015 at 2:59 PM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Hi Pablo,
Thanks a lot for the detailed response. Yes I am using
minimal_aws.yaml. Now i am hitting a different issue

Failed updating job api_z1 > api_z1/0 (canary): `api_z1/0'
is not running after update (00:12:11)

Error 400007: `api_z1/0' is not running after update


Any suggestions to resolve this?


Sincerely,

Dulanjalie

On Sun, Jun 21, 2015 at 4:42 AM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

This means that another property, 'cc.internal_api_user',
is missing on your deployment manifest. In short, properties are
configuration values used to configure deployed jobs (they are used to fill
templates passed to actual VMs). You can learn more about this here (
http://bosh.io/docs/deployment-manifest.html).
You have been following the minimal-aws example of cf-release,
right? Then, the file you have to modify is minimal-aws.yml (the deployment
manifest), because it seems not to be setting the property although it is
required.

To do so, go to the 'properties:' root section of the manifest
(where properties are globally set) and look for the following:

cc:
allow_app_ssh_access: false
...

And replace it with:

cc:
allow_app_ssh_access: false
internal_api_user: internal_user
...

What have we done here? We have globally set '
cc.internal_api_user' property to a valid value. Properties
are organized as a tree, so 'cc.internal_api_user' property is
the 'internal_api_user' leaf hanging from the 'cc' node (and all of this is
reflected on the manifest as a YAML hash containing other hashes).

I hope this helps (and I am sorry if it has been too long).
Anyway, it seems that minimal-aws example of cf-release should
be fixed, so that it includes these missing properties you are having
problems with.

Regards


El 21/06/2015 07:37, "Dulanjalie Dhanapala" <
dulanjalie(a)gmail.com> escribi├│:

Thanks Pablo,
the router related issue is resolved. Now i am hitting

Started preparing configuration > Binding configuration.
Failed: Error filling in template `hm9000.json.erb' for
`hm9000_z1/0' (line 22: Can't find property `["cc.internal_api_user"]')
(00:00:01)


Error 100: Error filling in template `hm9000.json.erb' for
`hm9000_z1/0' (line 22: Can't find property `["cc.internal_api_user"]')


Do you know wha and which file that i should change for this...


Sincerely,

Dulanjalie

On Sat, Jun 20, 2015 at 5:12 AM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

If you add another router, you would have to set its
static IP and configure it at haproxy in the section where your last
snippet comes from, so it balances load between them. I think that I am not
missing anything else.

However, it is not mandatory to have more than one router. If
you want to continue with one single router and bypass the "Can't
find property `["router.servers.z2"]" problem, you can try
replacing the snippet from your last mail with the following:

routers:
servers:
z1:
- IP # This is a single-element array with the
IP of your router
z2: [] # This is an empty array, because there
are no more routers.

I hope this helps.

2015-06-19 20:58 GMT+02:00 Dulanjalie Dhanapala <
dulanjalie(a)gmail.com>:

Seems like minimal-aws.yml contains the information required
by haproxy.config.erb. In my minimal-aws.yml i have single route config ( i
am used the sample, i didnt add/delete anything)
router: servers: z1: IP

I do not know if I add another router (z2) what are the
configs need to be done. Also I do not know what is the job of each
component if i add/delete it. Is there a doc which i can use?

Sincerely,
Dulanjalie


On Fri, Jun 19, 2015 at 10:00 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

Now, i hit this error

Started preparing configuration > Binding configuration.
Failed: Error filling in template `haproxy.config.erb' for
`ha_proxy_z1/0' (line 47: Can't find property `["router.servers.z2"]')
(00:00:01)


Error 100: Error filling in template `haproxy.config.erb'
for `ha_proxy_z1/0' (line 47: Can't find property `["router.servers.z2"]')


Can you guide me how to fix it?


Sincerely,

DUlanjalie

On Fri, Jun 19, 2015 at 9:01 AM, Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I did that already this this i think.
bosh micro deploy
*light-bosh-stemcell-2989-aws-xen-hvm-ubuntu-trusty-go_agent.tgz*

I followed the steps in
http://bosh.io/docs/deploy-microbosh-to-aws.html#deploy
DO i need to do it again.

Sincerely,
Dulanjalie

On Thu, Jun 18, 2015 at 10:56 PM, Jim Park <
spark(a)pivotal.io> wrote:

Looks like you need to do a bosh upload stemcell <URI>.
You can find the URI at http://bosh.io/stemcells

On Fri, Jun 19, 2015 at 5:22 AM Dulanjalie Dhanapala <
dulanjalie(a)gmail.com> wrote:

I am in the final step which is deployment of
minimal-aws.yml
I am hitting this error

Started preparing deployment > Binding stemcells.
Failed: Stemcell
`bosh-aws-xen-hvm-ubuntu-trusty-go_agent/2989' doesn't exist
(00:00:00)


Error 50003: Stemcell
`bosh-aws-xen-hvm-ubuntu-trusty-go_agent/2989' doesn't exist

Please find the logs @
http://fpaste.org/233861/34691074/

Can you help me ti find out the mistake i am making?

Sincerely,
Dulanjalie

On Thu, Jun 18, 2015 at 6:42 PM, Gwenn Etourneau <
getourneau(a)pivotal.io> wrote:

Good to know.

On Thu, Jun 18, 2015 at 10:58 PM, Dulanjalie Dhanapala
<dulanjalie(a)gmail.com> wrote:

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.

Type Protocol Port Range Source Custom
TCP Rule TCP 6868 <IP of the VM I run
BOSH> Custom TCP Rule TCP 25555 <IP
of the VM I run BOSH>
SSH TCP 22 <IP of the VM I run BOSH>
All TCP TCP 0-65535 SG itself All UDP
UDP 0-65535 SG 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

_______________________________________________
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


--
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


--
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


--
Thank you,

James Bayer

_______________________________________________
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


--
Dulanjalie


--
Dulanjalie

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


--
Lev Berman

Altoros - Cloud Foundry deployment, training and integration

Github
*: https://github.com/ldmberman <https://github.com/ldmberman>*

_______________________________________________
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

Join {cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.