# Mysql errors in production after upgrading to rails 2 **URL:** \ **Category:** Rails\ **Created:** [May 16, 2008, 12:23am UTC](https://www.ruby-forum.com/t/mysql-errors-in-production-after-upgrading-to-rails-2/137756 "2008-05-16T00:23:37Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![phil](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/e95f7d/32.png) [@phil](https://www.ruby-forum.com/u/phil)\ **Post date:** [May 16, 2008, 12:23am UTC](https://www.ruby-forum.com/t/mysql-errors-in-production-after-upgrading-to-rails-2/137756/1 "2008-05-16T00:23:37Z")
I’m trying to upgrade our production server to rails 2. I’ve already done this on my dev machine (osx) and it worked fine. But now, with everything at the same version, but running in production mode, the production machine - a CentOS5 box - is getting loads of: ActiveRecord::StatementInvalid (Mysql::Error: Lost connection to MySQL server during query errors. i"ve looked around but not found any valid reason why this should be happening. the mysql is version 5.0.22. Ruby 1.8.6 rails 2.0.2. Without solving this I guess we are going back to Rails 1.2.6, but the real problem is that it is causing my boss and team to question the entire stability of Rails! I’ve just set the server to run in development mode and it works a treat!!! What is up with that? ---
**Author:** ![phil](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/e95f7d/32.png) [@phil](https://www.ruby-forum.com/u/phil)\ **Post date:** [May 16, 2008, 12:31am UTC](https://www.ruby-forum.com/t/mysql-errors-in-production-after-upgrading-to-rails-2/137756/2 "2008-05-16T00:31:35Z")
phil wrote: > I’m trying to upgrade our production server to rails 2. I’ve already > done this on my dev machine (osx) and it worked fine. But now, with > everything at the same version, but running in production mode, the > production machine - a CentOS5 box - is getting loads of: > ActiveRecord::StatementInvalid (Mysql::Error: Lost connection to MySQL > server during query > errors. > > i"ve looked around but not found any valid reason why this should be > happening. the mysql is version 5.0.22. Ruby 1.8.6 rails 2.0.2. > > Without solving this I guess we are going back to Rails 1.2.6, but the > real problem is that it is causing my boss and team to question the > entire stability of Rails! > > I’ve just set the server to run in development mode and it works a > treat!!! What is up with that? what else have you tried? you tried running in production mode locally? you tried “ruby script/console production” on the box? is this mongrel and apache? or what? is it every query? or just some special long queries? ---
**Author:** ![phil](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/e95f7d/32.png) [@phil](https://www.ruby-forum.com/u/phil)\ **Post date:** [May 16, 2008, 8:28am UTC](https://www.ruby-forum.com/t/mysql-errors-in-production-after-upgrading-to-rails-2/137756/3 "2008-05-16T08:28:02Z")
Correct, I perhaps did not give enough details. From the console in production mode on that machine it works fine. It is from the mongrel that it doesn’t. It is essentially every query from the mongrel, as far as I can tell. Just trying something now, it is actually failing on occasion, in mongrel, even in development. I’ve never seen these errors before: !\ FAILSAFE /!\ Fri May 16 08:22:19 +0200 2008 Status: 500 Internal Server Error You have a nil object when you didn’t expect it! The error occurred while evaluating nil.all\_hashes /usr/local/lib/ ruby/gems/1.8/gems/activerecord-2.0.2/lib/active\_record/ connection\_adapters/mysql\_adapter.rb:482:in `select’ And the same query that I get this on: ActiveRecord::StatementInvalid (Mysql::Error: Lost connection to MySQL server during query: I can run from the console. So it definitely seem to be how mongrel is connecting to mysql. I am not using the mysql gem (I wasn’t before under 1.2.6 either) I am connecting with the builtin mysql adaptor. On May 16, 12:31 am, Matthew R. Jacobs \ **Author:** ![phil](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/e95f7d/32.png) [@phil](https://www.ruby-forum.com/u/phil)\ **Post date:** [May 16, 2008, 8:30am UTC](https://www.ruby-forum.com/t/mysql-errors-in-production-after-upgrading-to-rails-2/137756/4 "2008-05-16T08:30:22Z") I get the all\_hashes error too! nfi what’s causing it, might fire up my irc bot when I get home and try it then. ---
**Author:** ![phil](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/e95f7d/32.png) [@phil](https://www.ruby-forum.com/u/phil)\ **Post date:** [May 16, 2008, 3:08am UTC](https://www.ruby-forum.com/t/mysql-errors-in-production-after-upgrading-to-rails-2/137756/5 "2008-05-16T03:08:03Z")
I think this is more of an ActiveRecord problem, because I was getting the same thing when I was using my IRC bot to log channels into a database through ActiveRecord. It usually happened for no apparent reason, but every few mintues it would drop a query, very annoying. Switched over to sqlite3 which seemed to work fine, but I’m guessing you don’t want to do this. The only thing I can suggest is changing database servers, perhaps to postgres? On Fri, May 16, 2008 at 8:01 AM, Matthew R. Jacobs \< removed\_email\_address@domain.invalid\> wrote: > > i"ve looked around but not found any valid reason why this should be > > > – Ryan B. > **[frozenplague.net](http://www.frozenplague.net)** > > This domain may be for sale! Feel free to add me to MSN and/or GTalk as this email. ---
**Author:** ![phil](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/e95f7d/32.png) [@phil](https://www.ruby-forum.com/u/phil)\ **Post date:** [May 16, 2008, 11:28am UTC](https://www.ruby-forum.com/t/mysql-errors-in-production-after-upgrading-to-rails-2/137756/6 "2008-05-16T11:28:15Z")
On 16 May 2008, at 07:27, phil wrote: > The pure ruby mysql stuff is completely obsolete. Give the gem ago. Fred ---
**Author:** ![phil](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/e95f7d/32.png) [@phil](https://www.ruby-forum.com/u/phil)\ **Post date:** [May 16, 2008, 5:00pm UTC](https://www.ruby-forum.com/t/mysql-errors-in-production-after-upgrading-to-rails-2/137756/7 "2008-05-16T17:00:09Z")
I fixed it by installing the gem using this command: gem install mysql – --with-mysql-conf=/usr/bin/mysql --with-mysql- lib=/usr/lib/mysql Thanks! On May 16, 11:25 am, Frederick C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)