Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7013301
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T22:22:07+00:00 2026-05-27T22:22:07+00:00

Recently I upgraded my gems and started adding new stuff to my app like

  • 0

Recently I upgraded my gems and started adding new stuff to my app like authentication by third party social websites using omniauth gem. On development environment everything is fine and works like a charm.

I am deploying to staging and production servers using capistrano. Basic deployment is fine and working so far, but I have got really strange problems when I want to do migrations when deploying.

I get the following error messages from capistrano:

    [my.server.com] executing command
*** [err :: my.server.com] rake aborted!
*** [err :: my.server.com] "\xC5" on US-ASCII
*** [err :: my.server.com] 
*** [err :: my.server.com] (See full trace by running task with --trace)
    command finished in 2472ms

I was googling all around and couldn’t find any relevant solution. I also tried to downgrade rake gem back to 0.8.7 but with no success on the end – the same errors.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-27T22:22:08+00:00Added an answer on May 27, 2026 at 10:22 pm

    After hours of googling and digging in I found the solution that (I hope) may by helpful for someone with a similar or the same problem.

    I did bundle exec rake --trace db:migrate on the staging server and got the following error messages:

    rake aborted!
    "\xC5" on US-ASCII
    /var/www/myapp/test.myapp.com/releases/20111230233802/config/application.rb:5:in `read'
    /var/www/myapp/test.myapp.com/releases/20111230233802/config/application.rb:5:in `<top (required)>'
    /var/www/myapp/test.myapp.com/releases/20111230233802/Rakefile:4:in `require'
    /var/www/myapp/test.myapp.com/releases/20111230233802/Rakefile:4:in `<top (required)>'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/rake_module.rb:25:in `load'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/rake_module.rb:25:in `load_rakefile'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:501:in `raw_load_rakefile'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:82:in `block in load_rakefile'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:81:in `load_rakefile'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:65:in `block in run'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/bin/rake:19:in `load'
    /var/www/myapp/test.myapp.com/shared/bundle/ruby/1.9.1/bin/rake:19:in `<main>'
    

    So I jumped in to the config/application.rb file to find out what could rise the error. Line 5 of that file loads an external config file:

    require 'yaml'
    APP_CONFIG = YAML.load(File.read(File.expand_path('../app_config.yml', __FILE__)))
    

    and that external file contains UTF-8 chars, not US-ASCII. So I tried a couple of different solutions to solve that problem.

    The only one which worked for me was to add an extra few lines of code on top of config/application.rb file:

    if RUBY_VERSION =~ /1.9/
      Encoding.default_external = Encoding::UTF_8
      Encoding.default_internal = Encoding::UTF_8
    end
    

    just to tell rake to load external files using utf-8 encoding. After that change everything went smooth and exactly as expected. Problem solved!

    PS.
    I really don’t know why developers of rake 0.9 have changed previous behavior of rake 0.8 which worked fine for me and probably for you as well for a long time. Maybe you have an idea why? I am very curious.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I recently upgraded to Ubuntu 9.04 and I have issues using gems. I installed
I recently upgraded a 1.3.6 application to Grails2. My test cases have started failing
I recently upgraded my Silverlight app from 3 to 4. After a few hours
I recently upgraded my GAE Python app to Python 2.7. Since then, I periodically
Recently upgraded the entire project to .NET 4.0 but when I debug javascript (using
Pair.net recently upgraded our PHP install and afterwards client started see HTML in email
I recently started getting this error while running gems or bundler. The only thing
Recently upgraded to the awesome FireFox 4. However, I would like to disable the
I recently upgraded an ASP.NET app to .NET 3.5 and switched to the newer
I recently upgraded my computer from XP to Windows Seven. I was using IIS

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.