cf push: App has not finished staging

[Rick Mendes]

I recently worked through the instructions to get CF NG deployed to EC2. I have a simple Java app I wanted to try out as a test.

$ cf push --path=~/myprojects/sample_app.war

Saving to manifest.yml... OK

Uploading sample_app... OK

Starting sample_app... OK

-----> Downloaded app package (5.7M)

Installing java.

Downloading JDK...

Copying openjdk6-jre-u25.tar.gz from the buildpack cache ...

Unpacking JDK to .jdk

Downloading Tomcat: apache-tomcat-7.0.37.tar.gz

Copying apache-tomcat-7.0.37.tar.gz from the buildpack cache ...

Unpacking Tomcat to .tomcat

Copying mysql-connector-java-5.1.12.jar from the buildpack cache ...

Copying postgresql-9.0-801.jdbc4.jar from the buildpack cache ...

-----> Uploading staged droplet (43M)

-----> Uploaded droplet

Checking sample_app...

CFoundry::APIError: 170002: App has not finished staging

For more information, see ~/.cf/crash

Eventually, I want to put MySQL behind this but I wanted to start simple and see if it deployed successfully with no services.

The crash file doesn't tell me much more than the error shown at the end of the output.

Any suggestions on what this might be?

Thanks.

[Gabrielle Sweda]

Rick:

CF and the cf gem are maintained by a different group.  Can you post your question to vcap...@cloudfoundry.com?

gabi

[Rick Mendes]

Hi Gabi,

Makes sense. I will go ahead and do that. I have to learn to remember where the BOSH line stops and the CF line begins.

Thanks.

[Gabrielle Sweda]

Rick:

The line is a lot blurrier in the beginning b/c of the time spent with bosh to get CF running.  If CF fails to deploy then that is often a bosh question.  Once you are running cf (or vmc for v1) commands then typically it is a CF question to direct to vcap-dev.  

Gabi