Got the same error while deploying cloudfoundry on top vsphere. A quick was
delete the deployment and re-deploy

bosh delete deployment cloudfoundry --force
bosh -n deploy


On Sunday, May 13, 2012 11:10:15 AM UTC+5:30, Vadim Spivak wrote:

Nope, can you ssh the listed IP? Probably from another AWS instance since
its an internal IP.

-Vadim

On May 12, 2012, at 9:37 PM, Dr Nic Williams wrote:

The VM shows in the vms list (during compilation), but doesn't have a
"job/number" label. Can it be accessed via "bosh ssh"?

Dr Nic Williams - VP Developer Evangelism
Engine Yard
The Leading Platform as a Service
Mobile: +1 415 860 2185
Skype: nicwilliams
Twitter: @drnic

On Saturday, May 12, 2012 at 9:32 PM, Vadim Spivak wrote:

We're going to improve this soon, for now you have to patch the
package_compiler.rb to keep the VM around.

It should show up under bosh vms or in the debug log for the task.

-Vadim

On May 12, 2012, at 8:58 PM, Dr Nic Williams wrote:

Failed again.

I pushed up the latest bosh code, I checked that the director process is
using the latest code and has been restarted.

How do you debug compilation VMs when they are deleted? Also, how do you
ssh into them during compilation?

Nic

Dr Nic Williams - VP Developer Evangelism
Engine Yard
The Leading Platform as a Service
Mobile: +1 415 860 2185
Skype: nicwilliams
Twitter: @drnic

On Saturday, May 12, 2012 at 8:06 PM, Dr Nic Williams wrote:

Ok, fantastic, thanks.

Dr Nic Williams - VP Developer Evangelism
Engine Yard
The Leading Platform as a Service
Mobile: +1 415 860 2185
Skype: nicwilliams
Twitter: @drnic

On Saturday, May 12, 2012 at 7:54 PM, Vadim Spivak wrote:

I think it's a known issue with compilation logs greater than 1MB. I think
it has been fixed on HEAD.

-Vadim

On May 12, 2012, at 7:50 PM, Dr Nic Williams wrote:

I'm attempting to compile erlang for the first time, and my deployment is
throwing the following error just after the VM is deleted and it is
releasing the connection:

Worker thread raised exception: unknown agent_task_id -
/var/vcap/deploy/bosh/director/current/director/lib/director/client.rb:101

The full log is at https://gist.github.com/2671295

Oddly perhaps, even though the compilation of erlang is complete, before
the error, I have to keep re-compiling erlang each time. I guess because
the release is never completed.

Suggestions for where to look for debugging?

Nic

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

Dr Nic Williams - VP Developer Evangelism

[image: Engine Yard]

The Leading Platform as a Service

Mobile: 415 860 2185

Skype: nicwilliams

Twitter: @drnic
------------------------------



Search Discussions

  • Aneesh Kumar E P at Oct 12, 2012 at 7:08 am
    Got the same error while deploying cloudfoundry on top of vsphere a quick
    fix was delete the deployment and re-deploy.

    bosh delete deployment cloudfoundry --force
    bosh -n deploy

    On Sunday, May 13, 2012 11:10:15 AM UTC+5:30, Vadim Spivak wrote:

    Nope, can you ssh the listed IP? Probably from another AWS instance since
    its an internal IP.

    -Vadim

    On May 12, 2012, at 9:37 PM, Dr Nic Williams wrote:

    The VM shows in the vms list (during compilation), but doesn't have a
    "job/number" label. Can it be accessed via "bosh ssh"?

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 9:32 PM, Vadim Spivak wrote:

    We're going to improve this soon, for now you have to patch the
    package_compiler.rb to keep the VM around.

    It should show up under bosh vms or in the debug log for the task.

    -Vadim

    On May 12, 2012, at 8:58 PM, Dr Nic Williams wrote:

    Failed again.

    I pushed up the latest bosh code, I checked that the director process is
    using the latest code and has been restarted.

    How do you debug compilation VMs when they are deleted? Also, how do you
    ssh into them during compilation?

    Nic

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 8:06 PM, Dr Nic Williams wrote:

    Ok, fantastic, thanks.

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 7:54 PM, Vadim Spivak wrote:

    I think it's a known issue with compilation logs greater than 1MB. I think
    it has been fixed on HEAD.

    -Vadim

    On May 12, 2012, at 7:50 PM, Dr Nic Williams wrote:

    I'm attempting to compile erlang for the first time, and my deployment is
    throwing the following error just after the VM is deleted and it is
    releasing the connection:

    Worker thread raised exception: unknown agent_task_id -
    /var/vcap/deploy/bosh/director/current/director/lib/director/client.rb:101

    The full log is at https://gist.github.com/2671295

    Oddly perhaps, even though the compilation of erlang is complete, before
    the error, I have to keep re-compiling erlang each time. I guess because
    the release is never completed.

    Suggestions for where to look for debugging?

    Nic

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

    Dr Nic Williams - VP Developer Evangelism

    [image: Engine Yard]

    The Leading Platform as a Service

    Mobile: 415 860 2185

    Skype: nicwilliams

    Twitter: @drnic
    ------------------------------



  • Jason Anderson at Oct 31, 2013 at 6:20 pm
    I am also receiving this error while compiling packages on OpenStack
    Grizzly but deleting and redeploying the deployment does not seem to fix
    this. I have tried with both BOSH version 1141 and 1193 to no avail. The
    packages it has been specifically failing on it:

    mysql/0.1-dev: unknown agent_task_id (00:10:07)
    mysql55/0.1-dev: unknown agent_task_id (00:13:52)
    golang/4: unknown agent_task_id (00:15:55)
    ruby/0.1-dev: unknown agent_task_id (00:16:37)


    Could this be a problem with the log size as noted above? Any thoughts on
    fixes.

      - Jason Anderson
    On Friday, October 12, 2012 12:08:30 AM UTC-7, Aneesh Kumar E P wrote:

    Got the same error while deploying cloudfoundry on top of vsphere a quick
    fix was delete the deployment and re-deploy.

    bosh delete deployment cloudfoundry --force
    bosh -n deploy

    On Sunday, May 13, 2012 11:10:15 AM UTC+5:30, Vadim Spivak wrote:

    Nope, can you ssh the listed IP? Probably from another AWS instance since
    its an internal IP.

    -Vadim

    On May 12, 2012, at 9:37 PM, Dr Nic Williams wrote:

    The VM shows in the vms list (during compilation), but doesn't have a
    "job/number" label. Can it be accessed via "bosh ssh"?

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 9:32 PM, Vadim Spivak wrote:

    We're going to improve this soon, for now you have to patch the
    package_compiler.rb to keep the VM around.

    It should show up under bosh vms or in the debug log for the task.

    -Vadim

    On May 12, 2012, at 8:58 PM, Dr Nic Williams wrote:

    Failed again.

    I pushed up the latest bosh code, I checked that the director process is
    using the latest code and has been restarted.

    How do you debug compilation VMs when they are deleted? Also, how do you
    ssh into them during compilation?

    Nic

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 8:06 PM, Dr Nic Williams wrote:

    Ok, fantastic, thanks.

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 7:54 PM, Vadim Spivak wrote:

    I think it's a known issue with compilation logs greater than 1MB. I
    think it has been fixed on HEAD.

    -Vadim

    On May 12, 2012, at 7:50 PM, Dr Nic Williams <nwil...@engineyard.com>
    wrote:

    I'm attempting to compile erlang for the first time, and my deployment
    is throwing the following error just after the VM is deleted and it is
    releasing the connection:

    Worker thread raised exception: unknown agent_task_id -
    /var/vcap/deploy/bosh/director/current/director/lib/director/client.rb:101

    The full log is at https://gist.github.com/2671295

    Oddly perhaps, even though the compilation of erlang is complete, before
    the error, I have to keep re-compiling erlang each time. I guess because
    the release is never completed.

    Suggestions for where to look for debugging?

    Nic

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

    Dr Nic Williams - VP Developer Evangelism

    [image: Engine Yard]

    The Leading Platform as a Service

    Mobile: 415 860 2185

    Skype: nicwilliams

    Twitter: @drnic
    ------------------------------



    To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+unsubscribe@cloudfoundry.org.
  • Ferran Rodenas at Nov 1, 2013 at 6:34 am
    Can you please try increasing the nats.ping_interval and
    nats.ping_max_outstanding at your Bosh or microBosh deployment (not the CF
    deployment)? Several users have reported a similar issue, and the by-pass
    that worked for them was to increase those properties. Sometimes (generaly
    during network glitchs) NATS declares clients unresponsive and the Bosh
    agent doesn't reconnect by default, it's restarted and looses the task_id
    that's running.

    - Ferdy


    2013/10/31 Jason Anderson <anderson.l.jason@gmail.com>
    I am also receiving this error while compiling packages on OpenStack
    Grizzly but deleting and redeploying the deployment does not seem to fix
    this. I have tried with both BOSH version 1141 and 1193 to no avail. The
    packages it has been specifically failing on it:

    mysql/0.1-dev: unknown agent_task_id (00:10:07)
    mysql55/0.1-dev: unknown agent_task_id (00:13:52)
    golang/4: unknown agent_task_id (00:15:55)
    ruby/0.1-dev: unknown agent_task_id (00:16:37)


    Could this be a problem with the log size as noted above? Any thoughts on
    fixes.

    - Jason Anderson
    On Friday, October 12, 2012 12:08:30 AM UTC-7, Aneesh Kumar E P wrote:

    Got the same error while deploying cloudfoundry on top of vsphere a quick
    fix was delete the deployment and re-deploy.

    bosh delete deployment cloudfoundry --force
    bosh -n deploy

    On Sunday, May 13, 2012 11:10:15 AM UTC+5:30, Vadim Spivak wrote:

    Nope, can you ssh the listed IP? Probably from another AWS instance
    since its an internal IP.

    -Vadim

    On May 12, 2012, at 9:37 PM, Dr Nic Williams <drnicw...@gmail.com>
    wrote:

    The VM shows in the vms list (during compilation), but doesn't have a
    "job/number" label. Can it be accessed via "bosh ssh"?

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 9:32 PM, Vadim Spivak wrote:

    We're going to improve this soon, for now you have to patch the
    package_compiler.rb to keep the VM around.

    It should show up under bosh vms or in the debug log for the task.

    -Vadim

    On May 12, 2012, at 8:58 PM, Dr Nic Williams <drnicw...@gmail.com>
    wrote:

    Failed again.

    I pushed up the latest bosh code, I checked that the director process is
    using the latest code and has been restarted.

    How do you debug compilation VMs when they are deleted? Also, how do you
    ssh into them during compilation?

    Nic

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 8:06 PM, Dr Nic Williams wrote:

    Ok, fantastic, thanks.

    Dr Nic Williams - VP Developer Evangelism
    Engine Yard
    The Leading Platform as a Service
    Mobile: +1 415 860 2185
    Skype: nicwilliams
    Twitter: @drnic

    On Saturday, May 12, 2012 at 7:54 PM, Vadim Spivak wrote:

    I think it's a known issue with compilation logs greater than 1MB. I
    think it has been fixed on HEAD.

    -Vadim

    On May 12, 2012, at 7:50 PM, Dr Nic Williams <nwil...@engineyard.com>
    wrote:

    I'm attempting to compile erlang for the first time, and my deployment
    is throwing the following error just after the VM is deleted and it is
    releasing the connection:

    Worker thread raised exception: unknown agent_task_id -
    /var/vcap/deploy/bosh/**director/current/director/lib/**
    director/client.rb:101

    The full log is at https://gist.github.com/**2671295<https://gist.github.com/2671295>

    Oddly perhaps, even though the compilation of erlang is complete, before
    the error, I have to keep re-compiling erlang each time. I guess because
    the release is never completed.

    Suggestions for where to look for debugging?

    Nic

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

    Dr Nic Williams - VP Developer Evangelism

    [image: Engine Yard]

    The Leading Platform as a Service

    Mobile: 415 860 2185

    Skype: nicwilliams

    Twitter: @drnic
    ------------------------------




    To unsubscribe from this group and stop receiving emails from it,
    send an email to bosh-users+unsubscribe@cloudfoundry.org.
    To unsubscribe from this group and stop receiving emails from it, send an email to bosh-users+unsubscribe@cloudfoundry.org.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupbosh-users @
postedOct 12, '12 at 7:07a
activeNov 1, '13 at 6:34a
posts4
users3

People

Translate

site design / logo © 2021 Grokbase