Databases
StackOverflow2013
Postsdbo
PORails cron whenever, bundle: command not found
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails cron whenever, bundle: command not found
    text
    copied!<p>I am trying to use whenever to execute a rake task onces a day. Im getting this error</p> <pre><code>/bin/bash: bundle: command not found /home/app/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find bundler (&gt;= 0) amongst [minitest-1.6.0, rake-0.8.7, rdoc-2.5.8] (Gem::LoadError) from /home/app/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in `to_spec' from /home/app/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems.rb:1210:in `gem' from /home/app/.rvm/gems/ruby-1.9.2-p180/bin/bundle:18:in `&lt;main&gt;' </code></pre> <p>Here is my crontab</p> <pre><code># Begin Whenever generated tasks for: /home/af/www/app/releases/20120216172204/config/schedule.rb PATH=/home/af/.rvm/gems/ruby-1.9.2-p180@global/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games 0 0 * * * /bin/bash -l -c 'cd /home/af/www/app/releases/20120216172204 &amp;&amp; rvm 1.9.1-p180; RAILS_ENV=production /home/af/.rvm/gems/ruby-1.9.2-p180/bin/bundle exec rake daily:stats --silent &gt;&gt; /home/af/www/app/releases/20120216172204/log/cron.log 2&gt;&amp;1' # End Whenever generated tasks for: /home/af/www/app/releases/20120216172204/config/schedule.rb </code></pre> <p>I'm at a loss as to why it isn't working. If I run the command:</p> <pre><code>cd /home/af/www/app/releases/20120216172204 &amp;&amp; rvm 1.9.1-p180; RAILS_ENV=production /home/af/.rvm/gems/ruby-1.9.2-p180/bin/bundle exec rake daily:stats --silent &gt;&gt; /home/af/www/app/releases/20120216172204/log/cron.log 2&gt;&amp;1 </code></pre> <p>It works fine, not sure whats going on here.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload