Vulcan build error for memcached example #27

Closed
spyhunter opened this Issue Jul 1, 2012 · 11 comments

Projects

None yet

9 participants

@spyhunter

In following the example with memcached, once I run vulcan build, I get the following:

$ vulcan build
Packaging local directory... done
Uploading source package... !! Unknown error, no build output given

@ddollar
ddollar commented Jul 1, 2012

Could you try updating to the latest version of vulcan, then updating your build server:

$ gem update vulcan
$ vulcan update
@spyhunter

Hi David,

Thank you very much for your response. Unfortunately, the update did not
seem to improve matters. Below is the output. Do you have any advice?

Thank you again,
Brad

$ gem update vulcan
Updating installed gems
Nothing to update
$ vulcan update
Initialized empty Git repository in /private/var/folders/## DELETED
Counting objects: 883, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (803/803), done.
Writing objects: 100% (883/883), 1012.90 KiB ù 466 KiB/s, done.
Total 883 (delta 82), reused 0 (delta 0)

-----> Heroku receiving push
-----> Node.js app detected
-----> Resolving engine versions
Using Node.js version: 0.6.18
Using npm version: 1.1.4
-----> Fetching Node.js binaries
-----> Vendoring node into slug
-----> Installing dependencies with npm
npm WARN coffee-script@1.3.3 package.json: bugsâ'name'ê should
probably be bugsâ'url'ê
npm WARN coffee-script@1.3.3 package.json: bugsâ'name'ê should
probably be bugsâ'url'ê
npm WARN prefer global nodemon@0.6.18 should be installed with -g
coffee-script@1.3.3/tmp/build_1znknbx5tmh4s/node_modules/coffee-script
connect-form@0.2.0 /tmp/build_1znknbx5tmh4s/node_modules/connect-form
formidable@1.0.9/tmp/build_1znknbx5tmh4s/node_modules/connect-form/node_modules/formidable
cradle@0.6.3 /tmp/build_1znknbx5tmh4s/node_modules/cradle
follow@0.7.2/tmp/build_1znknbx5tmh4s/node_modules/cradle/node_modules/follow
request@2.2.9/tmp/build_1znknbx5tmh4s/node_modules/cradle/node_modules/follow/node_modules/request
request@2.9.202/tmp/build_1znknbx5tmh4s/node_modules/cradle/node_modules/request
vargs@0.1.0/tmp/build_1znknbx5tmh4s/node_modules/cradle/node_modules/vargs
express@2.5.9 /tmp/build_1znknbx5tmh4s/node_modules/express
connect@1.8.7/tmp/build_1znknbx5tmh4s/node_modules/express/node_modules/connect
qs@0.4.2/tmp/build_1znknbx5tmh4s/node_modules/express/node_modules/qs
mime@1.2.4/tmp/build_1znknbx5tmh4s/node_modules/express/node_modules/mime
formidable@1.0.9/tmp/build_1znknbx5tmh4s/node_modules/express/node_modules/connect/node_modules/formidable
mkdirp@0.3.0/tmp/build_1znknbx5tmh4s/node_modules/express/node_modules/mkdirp
knox@0.0.9 /tmp/build_1znknbx5tmh4s/node_modules/knox
node-uuid@1.3.3 /tmp/build_1znknbx5tmh4s/node_modules/node-uuid
nodemon@0.6.18 /tmp/build_1znknbx5tmh4s/node_modules/nodemon
restler@2.0.1 /tmp/build_1znknbx5tmh4s/node_modules/restler
Dependencies installed
-----> Discovering process types
Procfile declares types -> web
-----> Compiled slug size is 4.1MB
-----> Launching... done, v5
http://appname.herokuapp.com deployed to Heroku

To git@heroku.com:appname.git

  • cdc1354...12f5c4e master -> master (forced update)
    $
    $ vulcan build --verbose
    Packaging local directory... done
    Uploading source package... <style type="text/css"> html, body, iframe é margin: 0; padding: 0; height: 100%; è iframe é display: block; width: 100%; border: none; è </style> <title>Application Error</title> <iframe src="//s3.amazonaws.com/heroku_pages/error.html">

    Application Error

    </iframe> !! Unknown error, no build output given

On Sun, Jul 1, 2012 at 12:26 PM, David Dollar <
reply@reply.github.com

wrote:

Could you try updating to the latest version of vulcan, then updating your
build server:

$ gem update vulcan
$ vulcan update

Reply to this email directly or view it on GitHub:
#27 (comment)

@GBognar
GBognar commented Jul 13, 2012

Hi Brad,

I had the same issue, however reading the vulcan code I came across some references to Cloudant. After having added the (free) Cloudant add-on to my account on Heroku the build succeeded.
As a side-note: I've never seen to be mentioned Cloudant as a requirement for having a successful build with Vulcan, so either I've overlooked it in the documentation or it is missing. (Or the successful build was a simple side-effect.)

@phuesler

Adding Cloudant fixed the issue for me.

@gyndav
gyndav commented Oct 1, 2012

I have the same issue : is Cloudant a requirement ?

@lookfirst

apparently so... https://github.com/heroku/vulcan/blob/master/server/web.coffee#L35

too bad it isn't documented anywhere and i just banged my head against it for hours. grrr...

@evanstachowiak

I had to add a credit card to my heroku account to add any addons (even free). Perhaps this is why vulcan update is failing for everyone?

@rajlenin

I ran in to this error and spent quite some time on it. Yes cloudant is a requirement. Once added it worked finally

@ddollar
ddollar commented Nov 14, 2012

Vulcan should be attempting to add Cloudant automatically.

https://github.com/heroku/vulcan/blob/master/lib/vulcan/cli.rb#L156

I can't figure out why this is not working for you.

@evanstachowiak

If your account doesn't have an attached credit card it will fail silently.

On Tue, Nov 13, 2012 at 8:56 PM, David Dollar notifications@github.comwrote:

Vulcan should be attempting to add Cloudant automatically.

https://github.com/heroku/vulcan/blob/master/lib/vulcan/cli.rb#L156

I can't figure out why this is not working for you.


Reply to this email directly or view it on GitHubhttps://github.com/heroku/vulcan/issues/27#issuecomment-10352295.

@rajlenin

That might be the issue. I transferred it to a credit account and enabled the addon manually. Didn't get a chance to check if it would have succeeded after using the credit card account.

@wuputah wuputah closed this Dec 11, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment