Capistrano integration failing with undefined method `_cset' error #797

Closed
minter opened this Issue Mar 27, 2013 · 4 comments

Comments

4 participants

minter commented Mar 27, 2013

Hi folks,

I've integrated sidekiq into an application, but am having trouble with the capistrano deployment part of things. I'm running Rails 3.2.13 and Capistrano 2.14.2

In my Capfile, if I add the line require 'sidekiq/capistrano', the cap deploy fails with the following error. Removing that line allows the deploy to work successfully.

Any ideas?

minter:(git)tourney[master]/$ bundle exec cap deploy
/Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/variables.rb:122:in `method_missing_with_variables': undefined method `_cset' for #<Capistrano::Configuration:0x007ffce2359f80> (NoMethodError)
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/sidekiq-2.8.0/lib/sidekiq/capistrano.rb:7:in `block in <top (required)>'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:97:in `instance_eval'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:97:in `load'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:83:in `load'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/sidekiq-2.8.0/lib/sidekiq/capistrano.rb:1:in `<top (required)>'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:152:in `require'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:152:in `require'
    from Capfile:2:in `load'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:93:in `instance_eval'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:93:in `load'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:172:in `load_from_file'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:89:in `load'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:86:in `block in load'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:86:in `each'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/configuration/loading.rb:86:in `load'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/cli/execute.rb:65:in `block in load_recipes'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/cli/execute.rb:65:in `each'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/cli/execute.rb:65:in `load_recipes'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/cli/execute.rb:31:in `execute!'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/lib/capistrano/cli/execute.rb:14:in `execute'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/gems/capistrano-2.14.2/bin/cap:4:in `<top (required)>'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/bin/cap:19:in `load'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/bin/cap:19:in `<main>'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/bin/ruby_noexec_wrapper:14:in `eval'
    from /Users/minter/.rvm/gems/ruby-1.9.3-p385@tourney/bin/ruby_noexec_wrapper:14:in `<main>'

minter closed this Mar 28, 2013

What was the resolution?

Contributor

guiceolin commented Jun 28, 2013

I would like to know, too.
can you help us, @minter ?

minter commented Jun 29, 2013

I think I had an old cap setup originally - I'm pretty sure the fix was that I had to do a "Capify ." in the app root directory, and move some stuff that was in other files into a more standard configuration.

bricker commented Jul 6, 2014

For googlers: Capistrano expects your deploy.rb file to be in a config directory. The directory structure should be:

- Capfile
- config/
  - deploy.rb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment