Note that there are some explanatory texts on larger screens.

plurals
  1. POrubyon rails, rake, crontab and encoding
    text
    copied!<p>I have a rails rake task which runs just fine. I want this task to be run periodically by crontab so I added it to crontab as follows :</p> <pre><code>0,30,0 * * * * cd /var/www/html/metajorn &amp;&amp; RAILS_ENV=production /usr/local/bin/rake myraketask --trace &gt;&gt; /var/www/html/metajorn/log/cron_log.log 2&gt;&amp;1 </code></pre> <p>In cron_log.log I'm seeing the following error:</p> <pre><code>rake aborted! invalid byte sequence in US-ASCII /var/www/html/metajorn/config/boot.rb:98:in `parse_gem_version' /var/www/html/metajorn/config/boot.rb:80:in `gem_version' /var/www/html/metajorn/config/boot.rb:59:in `load_rails_gem' /var/www/html/metajorn/config/boot.rb:54:in `load_initializer' /var/www/html/metajorn/config/boot.rb:38:in `run' /var/www/html/metajorn/config/boot.rb:11:in `boot!' /var/www/html/metajorn/config/boot.rb:110:in `&lt;top (required)&gt;' /var/www/html/metajorn/Rakefile:4:in `require' /var/www/html/metajorn/Rakefile:4:in `&lt;top (required)&gt;' /usr/local/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in `load' /usr/local/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2383:in `raw_load_rakefile' /usr/local/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2017:in `block in load_rakefile' /usr/local/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile' /usr/local/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2000:in `block in run' /usr/local/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/local/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/local/bin/rake:31:in `&lt;main&gt;' </code></pre> <p>It is noteworthy that the task is working fine if I run it manually. </p> <p>Thanks,</p> <p>M</p>
 

Querying!

 
Guidance

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