Re: Staging error: no available stagers (status code: 400, error code: 170001)


From the source code
it seems there is no enough for memory or disk.

def stage(&completion_callback)
@stager_id = @stager_pool.find_stager(,
staging_task_memory_mb, staging_task_disk_mb)
raise Errors::ApiError.new_from_details('StagingError', 'no
available stagers') unless @stager_id

However, this is my first app. It should be light. The DEA is using
m1.large which is
m1.large | 4096 | 20

Anyone has the same error? and any suggestion on manifest or debug tips?

Another question, I want to add more debug information in
cloud_controller_ng.log. I tried to add some code in
but it did not show in the log. How to do?

On Thu, Jun 4, 2015 at 10:14 AM, Guangcai Wang <>

attached the deployment manifest. This is generated by spiff and then I
modified it.

On Thu, Jun 4, 2015 at 12:47 AM, Takeshi Morikawa <moog0814(a)>

Please check the 'staging.advertise' of nats message

sample command:
bundle exec nats-sub -s

I have one additional request
Can you share your bosh deployment manifest?

cf-dev mailing list

Join to automatically receive all group messages.