FAQ
Hello everyone ....

I'm seeing the following when uploading the 0.6.3 public stemcell. Previous
versions uploaded just fine.

lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
$ bosh upload stemcell ~/stemcells/bosh-stemcell-vsphere-0.6.3.tgz

Verifying stemcell...
File exists and readable OK
Using cached manifest...
Stemcell properties OK

Stemcell info
-------------
Name: bosh-stemcell
Version: 0.6.3

Checking if stemcell already exists...
No

Uploading stemcell...
bosh-stemcell: 100%
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo|
401.9MB 36.7MB/s Time: 00:00:10
Error 103: cannot access director (Connection refused - connect(2)
(http://172.21.10.181:25555))
lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
$ bosh tasks recent
Error 103: cannot access director (Connection refused - connect(2)
(http://172.21.10.181:25555))
lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
$ bosh status
Updating director data... error

Target micro (http://172.21.10.181:25555) Ver: 0.4 (00000000)
UUID 8b408fa2-ebf9-452c-89e0-0d5829d82091
User admin
Deployment /home/lbakken/releases/bosh-sample-release/wordpress.yml

Rebooting the director VM works, as well as just killing the director PID
and waiting for monit to restart it. Any ideas? Thanks!

Search Discussions

  • Martin Englund at Jul 31, 2012 at 3:41 pm
    Luke,

    you need to look in the director logfile - the location depends on
    wether you used chef_deployer or micro bosh to install.

    Cheers,
    /Martin
    On Tue, Jul 31, 2012 at 8:21 AM, Luke Bakken wrote:
    Hello everyone ....

    I'm seeing the following when uploading the 0.6.3 public stemcell. Previous
    versions uploaded just fine.

    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh upload stemcell ~/stemcells/bosh-stemcell-vsphere-0.6.3.tgz

    Verifying stemcell...
    File exists and readable OK
    Using cached manifest...
    Stemcell properties OK

    Stemcell info
    -------------
    Name: bosh-stemcell
    Version: 0.6.3

    Checking if stemcell already exists...
    No

    Uploading stemcell...
    bosh-stemcell: 100%
    oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo|
    401.9MB 36.7MB/s Time: 00:00:10
    Error 103: cannot access director (Connection refused - connect(2)
    (http://172.21.10.181:25555))
    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh tasks recent
    Error 103: cannot access director (Connection refused - connect(2)
    (http://172.21.10.181:25555))
    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh status
    Updating director data... error

    Target micro (http://172.21.10.181:25555) Ver: 0.4 (00000000)
    UUID 8b408fa2-ebf9-452c-89e0-0d5829d82091
    User admin
    Deployment /home/lbakken/releases/bosh-sample-release/wordpress.yml

    Rebooting the director VM works, as well as just killing the director PID
    and waiting for monit to restart it. Any ideas? Thanks!


    --
    cheers,
    /Martin
    --
    Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
    "The question is not if you are paranoid, it is if you are paranoid enough."
  • Luke Bakken at Jul 31, 2012 at 3:46 pm
    Martin -

    I just found the log file when you wrote back on the micro VM. The error
    (which I kind of suspected) was disk space related.

    Is there a way to get director logs other than just ssh-ing to the director
    VM?

    Thanks for the reply -
    Luke
    On Tuesday, July 31, 2012 8:41:55 AM UTC-7, Martin Englund wrote:

    Luke,

    you need to look in the director logfile - the location depends on
    wether you used chef_deployer or micro bosh to install.

    Cheers,
    /Martin
    On Tue, Jul 31, 2012 at 8:21 AM, Luke Bakken wrote:
    Hello everyone ....

    I'm seeing the following when uploading the 0.6.3 public stemcell. Previous
    versions uploaded just fine.

    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh upload stemcell ~/stemcells/bosh-stemcell-vsphere-0.6.3.tgz

    Verifying stemcell...
    File exists and readable OK
    Using cached manifest...
    Stemcell properties OK

    Stemcell info
    -------------
    Name: bosh-stemcell
    Version: 0.6.3

    Checking if stemcell already exists...
    No

    Uploading stemcell...
    bosh-stemcell: 100%

    oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo|
    401.9MB 36.7MB/s Time: 00:00:10
    Error 103: cannot access director (Connection refused - connect(2)
    (http://172.21.10.181:25555))
    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh tasks recent
    Error 103: cannot access director (Connection refused - connect(2)
    (http://172.21.10.181:25555))
    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh status
    Updating director data... error

    Target micro (http://172.21.10.181:25555) Ver: 0.4 (00000000)
    UUID 8b408fa2-ebf9-452c-89e0-0d5829d82091
    User admin
    Deployment /home/lbakken/releases/bosh-sample-release/wordpress.yml

    Rebooting the director VM works, as well as just killing the director PID
    and waiting for monit to restart it. Any ideas? Thanks!


    --
    cheers,
    /Martin
    --
    Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
    "The question is not if you are paranoid, it is if you are paranoid
    enough."
  • Martin Englund at Jul 31, 2012 at 4:08 pm
    No, not unless you have deployed bosh using micro bosh, then you would
    be able to use:
    bosh logs director 0 --all

    /M
    On Tue, Jul 31, 2012 at 8:46 AM, Luke Bakken wrote:
    Martin -

    I just found the log file when you wrote back on the micro VM. The error
    (which I kind of suspected) was disk space related.

    Is there a way to get director logs other than just ssh-ing to the director
    VM?

    Thanks for the reply -
    Luke

    On Tuesday, July 31, 2012 8:41:55 AM UTC-7, Martin Englund wrote:

    Luke,

    you need to look in the director logfile - the location depends on
    wether you used chef_deployer or micro bosh to install.

    Cheers,
    /Martin
    On Tue, Jul 31, 2012 at 8:21 AM, Luke Bakken wrote:
    Hello everyone ....

    I'm seeing the following when uploading the 0.6.3 public stemcell.
    Previous
    versions uploaded just fine.

    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh upload stemcell ~/stemcells/bosh-stemcell-vsphere-0.6.3.tgz

    Verifying stemcell...
    File exists and readable OK
    Using cached manifest...
    Stemcell properties OK

    Stemcell info
    -------------
    Name: bosh-stemcell
    Version: 0.6.3

    Checking if stemcell already exists...
    No

    Uploading stemcell...
    bosh-stemcell: 100%
    oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo|
    401.9MB 36.7MB/s Time: 00:00:10
    Error 103: cannot access director (Connection refused - connect(2)
    (http://172.21.10.181:25555))
    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh tasks recent
    Error 103: cannot access director (Connection refused - connect(2)
    (http://172.21.10.181:25555))
    lbakken@bosh-deployer ~/releases/bosh-sample-release (master)
    $ bosh status
    Updating director data... error

    Target micro (http://172.21.10.181:25555) Ver: 0.4 (00000000)
    UUID 8b408fa2-ebf9-452c-89e0-0d5829d82091
    User admin
    Deployment /home/lbakken/releases/bosh-sample-release/wordpress.yml

    Rebooting the director VM works, as well as just killing the director
    PID
    and waiting for monit to restart it. Any ideas? Thanks!


    --
    cheers,
    /Martin
    --
    Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
    "The question is not if you are paranoid, it is if you are paranoid
    enough."


    --
    cheers,
    /Martin
    --
    Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
    "The question is not if you are paranoid, it is if you are paranoid enough."

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupbosh-users @
postedJul 31, '12 at 3:21p
activeJul 31, '12 at 4:08p
posts4
users2

2 users in discussion

Martin Englund: 2 posts Luke Bakken: 2 posts

People

Translate

site design / logo © 2022 Grokbase