Deploying a standalone Java APP on CloudFoundry. fails withe exit-status = 127.

[lol...@gmail.com]

Hi all,

 

I am trying to create a standalone application to deploy in Pivotal CF. 

Referred the url,

http://support.run.pivotal.io/entries/24776196-How-to-push-standalone-java-application-to-Cloudfoundry-CF-V2-

 

However, cf push java-console-test shows the following in logs.   Pls suggest.

 

Logs:

 

2015-03-24T14:16:33.60+0530 [DEA]     OUT Starting app instance (index 0) with g
uid 75dad760-e163-4d86-ac8d-d263b0cb603c
2015-03-24T14:16:37.85+0530 [API]     OUT App instance exited with guid 75dad760
-e163-4d86-ac8d-d263b0cb603c payload: {"cc_partition"=>"default", "droplet"=>"75
dad760-e163-4d86-ac8d-d263b0cb603c", "version"=>"cbc74578-69b6-44c2-ac03-4f9a8b4
f0b48", "instance"=>"3530265a4ce44d7fa759ede881899929", "index"=>0, "reason"=>"C
RASHED", "exit_status"=>127, "exit_description"=>"app instance exited", "crash_t
imestamp"=>1427186797}
2015-03-24T14:17:14.11+0530 [DEA]     OUT Starting app instance (index 0) with g
uid 75dad760-e163-4d86-ac8d-d263b0cb603c
2015-03-24T14:17:18.32+0530 [API]     OUT App instance exited with guid 75dad760
-e163-4d86-ac8d-d263b0cb603c payload: {"cc_partition"=>"default", "droplet"=>"75
dad760-e163-4d86-ac8d-d263b0cb603c", "version"=>"cbc74578-69b6-44c2-ac03-4f9a8b4
f0b48", "instance"=>"057456441e88467db3499389302dee0c", "index"=>0, "reason"=>"C
RASHED", "exit_status"=>127, "exit_description"=>"app instance exited", "crash_t
imestamp"=>1427186838}
2015-03-24T14:17:18.39+0530 [API]     OUT Updated app with guid 75dad760-e163-4d
86-ac8d-d263b0cb603c ({"name"=>"java-console-test", "environment_json"=>"PRIVATE
 DATA HIDDEN"})
2015-03-24T14:17:28.29+0530 [API]     OUT Updated app with guid 75dad760-e163-4d
86-ac8d-d263b0cb603c ({"state"=>"STOPPED"})
2015-03-24T14:17:34.24+0530 [DEA]     OUT Got staging request for app with id 75
dad760-e163-4d86-ac8d-d263b0cb603c
2015-03-24T14:17:36.21+0530 [API]     OUT Updated app with guid 75dad760-e163-4d
86-ac8d-d263b0cb603c ({"state"=>"STARTED"})
2015-03-24T14:17:36.32+0530 [STG]     OUT -----> Downloaded app package (8.0K)
2015-03-24T14:17:36.72+0530 [STG]     OUT -----> Downloaded app buildpack cache
(43M)
2015-03-24T14:17:36.81+0530 [STG]     ERR     Cloning into '/tmp/buildpacks/java
-buildpack'...
2015-03-24T14:17:39.99+0530 [STG]     OUT     -----> Java Buildpack Version: 623
c428 | https://github.com/cloudfoundry/java-buildpack/#623c428
2015-03-24T14:17:40.15+0530 [STG]     OUT -----> Downloading Open Jdk JRE 1.8.0_
40 from https://download.run.pivotal.io/openjdk/lucid/x86_64/openjdk-1.8.0_40.ta
r.gz (found in cache)
2015-03-24T14:17:41.23+0530 [STG]     OUT        Expanding Open Jdk JRE to .java
-buildpack/open_jdk_jre (1.0s)
2015-03-24T14:17:47.41+0530 [STG]     OUT -----> Uploading droplet (43M)
2015-03-24T14:17:54.42+0530 [DEA]     OUT Starting app instance (index 0) with g
uid 75dad760-e163-4d86-ac8d-d263b0cb603c
2015-03-24T14:17:58.83+0530 [API]     OUT App instance exited with guid 75dad760
-e163-4d86-ac8d-d263b0cb603c payload: {"cc_partition"=>"default", "droplet"=>"75
dad760-e163-4d86-ac8d-d263b0cb603c", "version"=>"f6385f77-e9ad-4f4b-a09b-28bbe80
74a99", "instance"=>"35b234d10d794b9a9abbe618a1b1c7f3", "index"=>0, "reason"=>"C
RASHED", "exit_status"=>127, "exit_description"=>"app instance exited", "crash_t
imestamp"=>1427186878}
2015-03-24T14:18:02.51+0530 [DEA]     OUT Removing crash for app with id 75dad76
0-e163-4d86-ac8d-d263b0cb603c
2015-03-24T14:18:02.51+0530 [DEA]     OUT Stopping app instance (index 0) with g
uid 75dad760-e163-4d86-ac8d-d263b0cb603c
2015-03-24T14:18:02.51+0530 [DEA]     OUT Stopped app instance (index 0) with gu
id 75dad760-e163-4d86-ac8d-d263b0cb603c

[JT Archie]

Hi,

The java buildpack relies on pushing an artifact.  Can you provide the commands you used to push the application?

Thanks,

JT

[Daniel Mikusa]

On Tuesday, March 24, 2015 at 4:59:25 AM UTC-4, lol...@gmail.com wrote:

The command that is being run after the build pack stages is failing with an exit code of 127, which means "command not found".

1.) What the `cf push` command you're running?

2.) What's in your manifest.yml file?

3.) What's the output of `CF_TRACE=true cf app <app-name> | grep detected_start_command`?  That should show the command that's trying to be run.

Keep in mind you should not be using "cf push -c" or "command" in the manifest with the Java build pack.  

Dan