Date
1 - 7 of 7
how to debug "BuildpackCompileFailed" issue?
|
Ning Fu
Hi,
Does anyone know how to debug "BuildpackCompileFailed" issue? When I push a ruby app: ======================== ... Done uploadingOK Starting app happy in org funorg / space development as funcloud... FAILEDBuildpackCompileFailed TIP: use 'cf logs happy --recent' for more informationPivotals-iMac:happy-root-route-app pivotal$ cf logs happy --recent Connected, dumping recent logs for app happy in org funorg / space development as funcloud... ======================== But I got nothing from "cf logs happy --recent". It is "ruby '2.2.2'" in Gemfile, and my ruby build back is cached-1.6.11. I've also tried "bundle package --all" before I push. Any suggestions? Doesn't ruby build pack provide any logs? Thanks, Ning |
|
|
|
JT Archie <jarchie@...>
Ning,
toggle quoted message
Show quoted text
What is the output of `cf buildpacks`? JT On Tue, Mar 8, 2016 at 1:27 AM, Ning Fu <nfu(a)pivotal.io> wrote:
Hi, |
|
|
|
Jesse T. Alford
Are your Gemfile and Gemfile.lock files literally named Gemfile and
toggle quoted message
Show quoted text
Gemfile.lock, and both checked present at the top level of the directory you're pushing from, on the machine you're pushing from? The Ruby Buildpack looks for (and requires) the presence of these to identify a Ruby app. If you've got some other setup, you can put empty files with the appropriate names in the top level dir. This might not be your problem, but I've seen it cause the error you report many times. On Tue, Mar 8, 2016, 7:12 AM JT Archie <jarchie(a)pivotal.io> wrote:
Ning, |
|
|
|
Ning Fu
Here is the output of "cf buildpacks":
toggle quoted message
Show quoted text
cf buildpacks Getting buildpacks... buildpack position enabled locked filename staticfile_buildpack 1 true false staticfile_buildpack-cached-v1.2.3.zip java_buildpack_offline 2 true false java-buildpack-offline-v3.6.zip ruby_buildpack 3 true false ruby_buildpack-cached-v1.6.11.zip nodejs_buildpack 4 true false nodejs_buildpack-cached-v1.5.4.zip go_buildpack 5 true false go_buildpack-cached-v1.7.1.zip python_buildpack 6 true false python_buildpack-cached-v1.5.3.zip php_buildpack 7 true false php_buildpack-cached-v4.3.1.zip binary_buildpack 8 true false binary_buildpack-cached-v1.0.1.zip java_buildpack 9 true false java-buildpack-v3.3.1.zip On Wed, Mar 9, 2016 at 12:45 AM, Jesse Alford <jalford(a)pivotal.io> wrote:
Are your Gemfile and Gemfile.lock files literally named Gemfile and |
|
|
|
Ning Fu
Yes, Gemfile and Gemfile.lock files are present at the top level.
toggle quoted message
Show quoted text
I can get "cf logs" output for other apps I pushed. So I think the reason that I don't see anything from "cf logs --recent" is that there are no logs produced at all. Anyway, whatever the root cause it may be, I think the key point is not the root cause itself, it is the utilities that we provide to developers to investigate when such an error occurs. I think it is really a bad user experience for developers when such an error occurs but they can only guess the root cause and try the solutions, rather than find clues from logs. PHP build pack has a BP_DEBUG environment variable that helps debugging. But it seems Ruby build pack doesn't support it. Thanks, Ning On Wed, Mar 9, 2016 at 12:45 AM, Jesse Alford <jalford(a)pivotal.io> wrote:
Are your Gemfile and Gemfile.lock files literally named Gemfile and |
|
|
|
Mike Dalessio
Hi Ning,
toggle quoted message
Show quoted text
If you generate an application manifest based on the current state of the app, you'll have more information with which to try to diagnose the issue. The command is `cf create-app-manifest APP_NAME [-p /path/to/<app-name>-manifest.yml ]` Can you share the contents of that manifest file? -m On Tue, Mar 8, 2016 at 10:29 PM, Ning Fu <nfu(a)pivotal.io> wrote:
Yes, Gemfile and Gemfile.lock files are present at the top level. |
|
|
|
Noburou TANIGUCHI
Hi Ning,
Does anyone know how to debug "BuildpackCompileFailed" issue?1) I think you'd better open another terminal and run `cf logs (appname)` while pushing your app. 2) If you know something about buildpacks (especially about the 3 major steps -- detect, compile, and release), I think this Anynines blog might help: http://blog.anynines.com/debug-cloud-foundry-java-buildpack/ However it is old and dealing with java-buildpack, it is still useful and you can use it almost only by replacing "java" to "ruby". *NOTE* There is no file `.java-buildpack.log` and no environment variable `JBP_LOG_LEVEL` for ruby-buildpack. *NOTE 2* The section "Start the server" is in app starting process, not in app staging process. So you can't apply the process in the blog post. Ning Fu wrote Hi, ----- I'm not a ... noburou taniguchi -- View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-how-to-debug-BuildpackCompileFailed-issue-tp4079p4119.html Sent from the CF Dev mailing list archive at Nabble.com. |
|
|