The problem is that your app is crashing. Fortunately the reason in this case is clear from the exit status. 127 means "command not found". This is a convention in

Hi, It seems too late to be here, but there may be a person coming across by Web search. I'll write my script snippet to get environment variables for such a person. ``` cat /proc/$(cat

more information on this: I am experiencing to deploy APPs using docker image, which means we actually didn't use java buildpack in this case. But I still reproduced this issue, so it seems it's not

I tried it by setting health check as above. Still get the same error. This is the CF Push command I am using: cf push -c 'mysql -u NBoEjIpjUf3D1yI -p3ET8vIGRMlDBJIn rmdsmp <

From the message "failed to accept connections within health check timeout" You can try to disable health check and have another try to see if it works cf set-health-check APP_NAME 'none'

Hi, Am new to CF. Trying to push an app with a mysql service binding fails. Below is the output of cf logs smdapp --recent: Connected, tailing logs for app smdsmp95 in org org1 / space space1 as

Hello, all I tried to push an APP using docker image, but when I restarted the APP, it failed to start because I removed the remote docker image. Is this designed behavior? Don't we save it somewhere

William - Thanks for looking at this. We deleted the old rabbit cluster and deployed this new release of Pivotal. So there would not be any orphan instances. The below command was tried as well and

When trying to register a service against the RabbitMQ broker using cf create-service Example: *cloudfoundry(a)micro-deploy-uspl:~/persis-store/deploy/initial$ cf create-service p-rabbitmq

You can find the relevant code for this at: https://github.com/pivotal-cf/cf-rabbitmq-release/blob/master/src/rabbitmq-broker/src/clojure/io/pivotal/pcf/rabbitmq/server.clj#L140-L165 Is it possible

Hi, We are seeing this error while creating a service instance against a latest RabbitMQ deployment which we just deployed: Server error, status code: 409, error code: 10001, message:

Hi Troy, Appreciate your time putting this proposal together. I believe many of these are addressed in the already in progress v3 cc api work by the CAPI team. I highly recommend attending the talk

Yes, the file is actually stored in database, we don't rely on the FS of the container. Just we want to do virus scan and other checks before we accept it and store it to database.

Using the app container’s file system like this is generally discouraged. See the Cloud Foundry docs <http://docs.cloudfoundry.org/devguide/deploy-apps/prepare-to-deploy.html#filesystem> for an

Stanley, I am curious as to why you would prefer to do scanning of an application after it is pushed rather than before on something like a CI system. -- Danny Rosen <https://goo.gl/eNWhJU>

This narrative proposes adding Heroku-style "releases" for applications: https://docs.google.com/document/d/1sIViZyeCri2URHAt57YW4n482cBav3b5dOgP6D_vr4A/ The feature allows developers to see a list

You don't have root access in application containers. You could bundle the software into a custom build pack. Again, you can't install stuff with root so you have to manually extract the files

Hi cloudfoundry team , we have modified java-buildpack validate input yaml against schema using kwalify gem. we have created offline buidpack for the same. now when we do cf push using this new

Hi cloudfoundry team , we have modified java-buildpack validate input yaml against schema using kwalify gem. we have created offline buidpack for the same. now when we do cf push using this new

Thanks for information. I tried it today and it works well, I didn't see such logs, not sure why I saw that error yesterday :-)