Hi, Daya, Thanks for the log entries and the state response from the cell. It does look like that cell should have sufficient capacity to take on the staging task. From the BBS logs for the

Hi, Eric, I further checked the logs you mentioned and can't see what could be the problem. I only have one instance of cell running and here is the state info: curl

Not very nice removing the v1 service migration endpoint before actually removing v1 service support. Do you see any issue with my reverting that commit on the CC that went into

Hi, Eric, FYI.. staging a buildpack-based app against the Diego backend also gave me the same Failure (InsufficientResources) but I was able to deploy and start the same buildpack based app using the

Hi, Eric, FYI.. staging a buildpack-based app against the Diego backend also gave me the same Failure (InsufficientResources) but I was able to deploy and start the same buildpack based app using the

That looks off. This is the code in the etcd startup script that would be running in that version of

Hi James, That sounds like you might be using a self signed cert and CC is failing trying to do cert verification. You can try specifying in your manifest

A bug with AUFS [1] was introduced in version 3.19.0-40 of the linux kernel. This bug can cause containers to end up with unkillable zombie processes with high CPU usage. This can happen any time a

What bosh instances --ps give to you ?

Hi there I'm trying to deploy a CF release with Diego but I'm getting: Started updating job etcd_z2 > etcd_z2/0 (canary). Failed: `etcd_z2/0' is not running after update (00:10:46) Error 400007:

Got your point,Dan Thanks Sent from my iPhone Loris:leverage cloud foundry for @Scale DevOps 在 2016年1月27日，下午10:06，Daniel Mikusa <dmikusa(a)pivotal.io<mailto:dmikusa(a)pivotal.io>>

Yu, The environment variable HTTP_PROXY needs to be attached to the app, not just the box. On your app set the environment variable with `cf set-env <app_name> HTTP_PROXY <proxy_server>`. Then try

Correct. There's a couple ways you could do it. - You can package the installer and run that before your app starts (assuming the installer can be run as a non-root user). You can use

Thanks Dan Before I check if we need root access,we not only package the binary but also its all dependency,correct? Sent from my iPhone Loris:leverage cloud foundry for @Scale DevOps 在

Apps don't have root access, so you can't `sudo` or `su`. Can you run this not as root? If so, you could package the binaries you need with the app. Dan

Hi, I have just set up a fresh v229 install to do some testing with - the bosh deployment appeared to complete successfully and all the VMs are running, however anything after initial authentication

Hi Eric, Thanks a lot for the detailed response to my query. I used the minimal-aws.yml configuration ( https://github.com/cloudfoundry/cf-release/tree/v226/example_manifests) to create my

Hi, I merged the new client as "mongoclient" module. For now the only way to try it out is to rename it to dbclient and replace the existing CouchDB client with it. Regards, Hristo Iliev

Good morning Danny, "This is interesting and I'd like to obtain a better understanding of the use cases this library supports that drove you to publish it" Can you describe in detail the question? I

Hello CF-dev community members! I deployed CF on a PC with cf_nise_installer. When pushing a app with a online buildpack as following, it's