Rails cron whenever, bundle: command not found

Question

I am trying to use whenever to execute a rake task onces a day. Im getting this error

/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 (>= 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 `<main>'

Here is my crontab

# 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 && rvm 1.9.1-p180; RAILS_ENV=production /home/af/.rvm/gems/ruby-1.9.2-p180/bin/bundle exec rake daily:stats --silent >> /home/af/www/app/releases/20120216172204/log/cron.log 2>&1'

# End Whenever generated tasks for: /home/af/www/app/releases/20120216172204/config/schedule.rb

I'm at a loss as to why it isn't working. If I run the command:

cd /home/af/www/app/releases/20120216172204 && rvm 1.9.1-p180; RAILS_ENV=production /home/af/.rvm/gems/ruby-1.9.2-p180/bin/bundle exec rake daily:stats --silent >> /home/af/www/app/releases/20120216172204/log/cron.log 2>&1

It works fine, not sure whats going on here.

If you don't get an answer to this, please bug me and I'll tell you what works for me. I'd love for somebody else to answer this question though, as I've never liked my solution. — cailinanne, Feb 28 '12 at 14:38
I've been trying to solve this for the last couple of weeks. Really at a loss as to what is causing it. What is your solution? — Josh Crowder, Feb 28 '12 at 15:28

score 71 · Answer 1 · edited Oct 22 '14 at 10:18

71

You can also ensure your PATH ends up in the crontab, by putting the following at the top of the schedule.rb file:

env :PATH, ENV['PATH']

https://groups.google.com/forum/#!msg/whenever-gem/yRLt3f2jrfU/Exu3xfCo8DAJ

If above solution don't work for you, try:

env :GEM_PATH, ENV['GEM_PATH']

edited Oct 22 '14 at 10:18

RAJ

9,697
1
33
63

answered Jun 15 '12 at 20:11

Dennis Kuczynski

790
5
4

7

Just in case. This worked for me but then coudln't find my gemfiles. I fixed it with `env :GEM_PATH, ENV['GEM_PATH']` – digitalWestie Feb 19 '13 at 16:32
2

This did not work for me - could you try removing the env :PATH, ENV['PATH'] and confirm that this is actually a fix? – vanboom Dec 26 '14 at 01:58
This env :GEM_PATH, ENV['GEM_PATH'] works for me. Thanks – jmetran Apr 15 '15 at 11:51
This worked for me even more than 10 years later... – Tintin81 Jan 25 '23 at 16:58

score 6 · Answer 2 · answered Oct 22 '15 at 01:32

In my case I just ran :

rvm env --path -- ruby-version[@gemset-name]

Referring to cron job setup doc

Added new source line to the command for ruby path before bundle command in the crontab -e

source /usr/local/rvm/environments/ruby-1.9.3-p392;

Now the commands like as below:

Before:

0 4 * * * cd /home/current && bundle exec rake my_rake RAILS_ENV=production

After:

0 4 * * * cd /home/current && source /usr/local/rvm/environments/ruby-1.9.3-p392; bundle exec rake my_rake RAILS_ENV=production

Cheers!!!

score 4 · Answer 3 · answered Sep 12 '12 at 11:17

After so many try outs the following seems to work

Type the following from terminal

Type crontab -e This opens the crontab for editing. You will see two lines as below:

# cron clears out environment variables, but Rubber.root/script/rubber uses
# "rvm do default" to run, so no longer any need to setup ruby env vars here,
# all we need is PATH
PATH=/<path to bundle>/bundle/ruby/1.9.1/bin:/usr/local/rvm/gems

AND

# Begin Whenever generated tasks for: /mnt/wamjoke-production/releases/20120912$
PATH=/<path to bundle>/shared/bundle/ruby/1.9.1/bin:/usr/local/rvm/gems

Comment out both lines beginning with PATH.

Do the above step whenever you run "bundle exec whenever" command. And it works.

No idea why PATH is misleading the environment.

score 3 · Answer 4 · answered Feb 28 '12 at 18:20

3

I hate this problem - I've spent hours trying to solve it too.

What works for me is to add

RAILS_ENV=production; source /usr/local/rvm/scripts/rvm;

before the bundle command.

answered Feb 28 '12 at 18:20

cailinanne

8,332
5
41
49

2

I think I've got it. When you're not an RVM user there's no problem, But If you're, you better stick to these guidelines: https://rvm.io/integration/cron/ So, By using the RVM generated wrappers I managed to come with a clean syntax to place in crontab that actually works... 1 0 * * * cd ~/Desktop/cellar/ && /home/jose/.rvm/bin/rake-ruby-1.9.3-p0 wines:destroy_from_1969 >> ~/Desktop/cron_log.log 2>&1 that's for a Rails app located at ~/Desktop/cellar/ – jlstr Jul 13 '12 at 18:11

score 2 · Answer 5 · edited Aug 24 '23 at 02:01

2

Forget about PATH settings in cron files. Setting the PATH does not work.

Set the path to bundle explicitly in your config/schedule.rb

set :bundle_command, "/usr/local/bin/bundle"

edited Aug 24 '23 at 02:01

Sara Fuerst

5,688
8
43
86

answered Dec 28 '14 at 18:38

vanboom

1,274
12
20

score 2 · Answer 6 · answered Mar 16 '16 at 13:52

You can try below solution which I found while googling and that works for me finally....hope that should work with you.

I implemented and tested the same on production make sure that to change environment accordingly -

set :output, "{your path on the server}/log/cron_log.log"
 set :environment, :production
 env :PATH, ENV['PATH']
 job_type :rbenv_rake, %q!eval "$(rbenv init -)"; cd :path && :environment_variable=:environment bundle exec rake :task --silent :output!

Best luck, This issue occurred after 3 years as I was using before just simple what given on the gem documentation on production.

I'm using Ruby 2.x and Rails 4.2 with whenever 0.9.4 latest version. It should work with earlier version as well, if the nature of the issue is same.

thank you.

score 1 · Answer 7 · edited Jan 15 '18 at 18:47

By executing a command that way: /bin/bash -l -c

You are launching a bash command as a login shell which is going to source (execute) /etc/profile bash file as a setup file. By doing so, if you check this file, it might have bash command lines that erase your previous $PATH which you do not want to since it contains your path to your bundle and all your other commands in the first place.

To fix this issue you just have to remove the lines related to set up the $PATH variable in your /etc/profile file.

score 1 · Answer 8 · answered Feb 28 '12 at 15:57

1

I think you should try explicitly setting the GEM_HOME and GEM_PATH environment variables in your crontab. You could also try running something like gem list --local or gem environment through cron and checking the output.

answered Feb 28 '12 at 15:57

Sebi

669
5
6

score 1 · Accepted Answer · answered Feb 28 '12 at 17:51

1

I played around with this all afternoon and couldn't find a better solution. Here is what I have come up with

bundle install --binstubs

and then run

bin/rake daily:stats

answered Feb 28 '12 at 17:51

Josh Crowder

1,041
1
10
30

2

Did you try Dennis's suggestion of adding env :PATH, ENV['PATH'] to your schedule.rb? That worked for me. – Fudgie Sep 25 '12 at 21:44

score 0 · Answer 10 · answered Jul 25 '13 at 12:31

This is a ENV['PATH'] not set issue. The most elegant way to fix this is to append the rvm related scripts to the path right after the install. Add the following lines to beginning of .bashrc ( beginning and not end as when .bashrc is accessed by a non-interactive shell, the line [ -z "$PS1" ] && return throws error and the subsequent lines are not executed.

PATH=$PATH:$HOME/.rvm/bin # Add RVM to PATH for scripting
[[ -s "$HOME/.rvm/scripts/rvm" ]] && source "$HOME/.rvm/scripts/rvm"

and not try to explicitly set PATH and sully environment variables.

score 0 · Answer 11 · answered Oct 18 '20 at 09:46

For those using rbenv you can use the included shim /home/username/.rbenv/shims/bundle

0 0 * * * /bin/bash -l -c 'cd /home/af/www/app/releases/20120216172204 && RAILS_ENV=production /home/af/.rbenv/shims/bundle exec rake daily:stats --silent >> /home/af/www/app/releases/20120216172204/log/cron.log 2>&1'

score 0 · Answer 12 · edited Jan 11 '21 at 14:08

0

in 2021, I found a basic solution, just add on top of schedule.rb

 env :PATH, ENV['PATH']
 set :output, "log/cron_log.log"
 set :runner_command, "rails runner"

from:

https://github.com/javan/whenever/issues/665

edited Jan 11 '21 at 14:08

katalin_2003

787
1
16
30

answered Jan 11 '21 at 12:47

AnnABlue

121
3
12

score 0 · Answer 13 · answered Feb 03 '21 at 05:14

I solved this problem by printing out my environmental variables

printenv

finding the ones that look related to Rails. One was a path to gems, the other was GEM_HOME and prepending the command in cron with these two:

PATH=$PATH:/home/petr/gems/bin GEM_HOME=/home/petr/gems program_executable

score 0 · Answer 14 · answered Mar 24 '21 at 22:24

Also in 2021, adding this in schedule.rb worked for me:

set :job_template, "bash -l -c 'PATH=#{ENV['PATH']} && :job'"

All jobs are by default run with bash -l -c 'command...' (https://github.com/javan/whenever)

So I made bash include ENV['PATH'] in PATH at the beginning and now rails are called from the proper rbenv.

score 0 · Answer 15 · answered Jul 24 '23 at 11:10

0

2023, still having this issue. What worked for me in development. Adjust these to production paths/settings.

set :bundle_command, "/Users/$username/.rbenv/shims/bundler exec"
set :environment, :development
set :output, {:error => "log/cron_error_log.log", :standard => "log/cron_log.log"}

answered Jul 24 '23 at 11:10

stjamesfr

11
2

The issue is about bundle being accessible meaning PATH variable including it. The solution lies within that instead of setting a custom bundle command. Something needs to be `source`d. – Mengu Jul 25 '23 at 22:30

score -1 · Answer 16 · answered Aug 08 '13 at 08:41

-1

For modern fix, add this line in capistrano deploy.rb,

set :whenever_command, "bundle exec whenever"

answered Aug 08 '13 at 08:41

chagel

495
6
17

Instead, set the :bundle_command, "/usr/local/bin/bundle" per my answer. Forget about trying to get the PATH to work. – vanboom Dec 28 '14 at 18:39

score -5 · Answer 17 · answered Jul 11 '13 at 04:11

-5

[root@smbserver current]# crontab -e

02 22 * * 1-5 /bin/bash -l -c  /shell/day.sh 
30 14 * * 0 /bin/bash -l -c  /shell/week.sh

answered Jul 11 '13 at 04:11

iceskysl

217
3
7

Rails cron whenever, bundle: command not found

17 Answers17

Linked