Databases
StackOverflow2013
Postsdbo
PORuby on Rails MySQL #08S01Bad handshake - downgrade MySQL?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORuby on Rails MySQL #08S01Bad handshake - downgrade MySQL?
    primarykey
    data
    text
    <p>We recently upgraded from MySQL 5.1.41 to 5.1.61 on our Ubuntu 10.04LTS server. We have an ancient RoR web app that's now giving a bad handshake error:</p> <pre><code>Mysql::Error in MainController#index #08S01Bad handshake /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/vendor/mysql.rb:523:in `read' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/vendor/mysql.rb:153:in `real_connect' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/connection_adapters/mysql_adapter.rb:389:in `connect' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/connection_adapters/mysql_adapter.rb:152:in `initialize' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/connection_adapters/mysql_adapter.rb:82:in `new' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/connection_adapters/mysql_adapter.rb:82:in `mysql_connection' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/connection_adapters/abstract/connection_specification.rb:262:in `send' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/connection_adapters/abstract/connection_specification.rb:262:in `connection_without_query_cache=' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/query_cache.rb:54:in `connection=' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/connection_adapters/abstract/connection_specification.rb:230:in `retrieve_connection' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/connection_adapters/abstract/connection_specification.rb:78:in `connection' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:763:in `columns' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:2060:in `attributes_from_column_definition_without_lock' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/locking/optimistic.rb:45:in `attributes_from_column_definition' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1502:in `initialize_without_callbacks' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/callbacks.rb:225:in `initialize' #{RAILS_ROOT}/app/controllers/application.rb:48:in `new' #{RAILS_ROOT}/app/controllers/application.rb:48:in `log_info' /usr/local/bin/mongrel_rails:19:in `load' /usr/local/bin/mongrel_rails:19 </code></pre> <p>I googled around and stumbled onto <a href="http://bugs.ruby-lang.org/issues/5017">http://bugs.ruby-lang.org/issues/5017</a> which tells me it's a Ruby MySQL extension bug. We aren't using the MySQL gem. Our web app is incredibly old and fragile (Ruby v1.8.7, Rails v1.2.3, Mongrel 1.1.5). We're in the process of replacing it with a Django rewrite, so we just need to get this functional for the next few weeks until we will replace it with the new site.</p> <p>How can we get past this error? I'm thinking that downgrading to MySQL 5.1.41 is the best way to handle this, and then when we begin using the new site in a few weeks, we can re-upgrade to 5.1.61. However, I'm having an issue downgrading mysql. This is the command I'm using:</p> <p><code>sudo aptitude install mysql-server-5.1=5.1.41-3ubuntu12.10</code></p> <p>However, this tells me <code>Unable to find a version "5.1.41-3ubuntu12.10" for the package "mysql-server-5.1"</code>. I've tried <code>sudo aptitude install mysql-server-5.1=5.1.41</code> also, but that didn't work either. How can I have aptitude install the correct version of MySQL?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGeoff
    1. USGeoff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORuby on Rails MySQL #08S01Bad handshake - downgrade MySQL?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORuby on Rails MySQL #08S01Bad handshake - downgrade MySQL?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORuby on Rails MySQL #08S01Bad handshake - downgrade MySQL?
      1. USedwardsharp
      1. VTFavorite
    1. CO*I'm thinking that downgrading to MySQL 5.1.41 is the best way to handle this* If your database connection code is centralised, perhaps use the workaround in your link? *A workaround to avoid this problem is to not set a database when establishing the connection.*
      singulars
      1. PORuby on Rails MySQL #08S01Bad handshake - downgrade MySQL?
      1. USta.speot.is
    2. COMaybe it's just that I'm not all that familiar with RoR, but I'm not sure how to do this. The database connection settings are in `config/database.yml`, and I'm not sure how else to get the site to interface with MySQL without specifying the database name in that file. I did try commenting out the database name, but I get a new error: `No database specified. Missing argument: database.`
      singulars
      1. PORuby on Rails MySQL #08S01Bad handshake - downgrade MySQL?
      1. USGeoff
    3. COI just encountered the same issue on upgrade from .49 to .61. On Debian Squeeze, downgraded with: `sudo aptitude install mysql-server-5.1=5.1.49-3 mysql-client-5.1=5.1.49-3 mysql-common=5.1.49-3 mysql-server-core-5.1=5.1.49-3 libmysqlclient16=5.1.49-3`.
      singulars
      1. PORuby on Rails MySQL #08S01Bad handshake - downgrade MySQL?
      1. USgsreynolds
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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