Exception caught: Mysql::Error: query: not connected: SHOW TABLES

337 views
Skip to first unread message

Allan MacGregor

unread,
Jun 5, 2012, 10:39:15 AM6/5/12
to rub...@googlegroups.com
I keep getting this error when trying to run a scan with rubyrep

rubyrep --verbose scan -c testconf in ~
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/table_spec_resolver.rb:91: warning: encoding option is ignored - U
Exception caught: Mysql::Error: query: not connected: SHOW TABLES
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/activerecord-3.2.5/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:243:in `query'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/activerecord-3.2.5/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:243:in `block in execute'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/activerecord-3.2.5/lib/active_record/connection_adapters/abstract_adapter.rb:280:in `block in log'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/activesupport-3.2.5/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/activerecord-3.2.5/lib/active_record/connection_adapters/abstract_adapter.rb:275:in `log'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/activerecord-3.2.5/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:243:in `execute'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/activerecord-3.2.5/lib/active_record/connection_adapters/mysql_adapter.rb:314:in `execute_and_free'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/activerecord-3.2.5/lib/active_record/connection_adapters/abstract_mysql_adapter.rb:381:in `tables'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/table_spec_resolver.rb:14:in `tables'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/table_spec_resolver.rb:91:in `block in expand_table_specs'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/table_spec_resolver.rb:83:in `each'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/table_spec_resolver.rb:83:in `expand_table_specs'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/table_spec_resolver.rb:58:in `resolve'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/session.rb:45:in `manual_primary_keys'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/session.rb:215:in `connect_database'
/home/mbertulli/.rvm/gems/ruby-1.9.2-head/gems/rubyrep-1.2.0/lib/rubyrep/session.rb:179:in `block in refresh_database_connection'

William Jordan

unread,
Sep 11, 2012, 12:40:18 PM9/11/12
to rub...@googlegroups.com
Hi Allan, I ran into a similar problem and realised the left DB was empty and the right DB was my active one with data.  I did run into a few permissions issues along the way as well. But switching the order of my databases helped get past this specific error.

William

Toilem Godwin

unread,
Dec 3, 2014, 7:25:22 AM12/3/14
to rub...@googlegroups.com
Hi Allan,

Didi you get a solution to the problem?

Kindly share if you did
Reply all
Reply to author
Forward
0 new messages