# Lost MySQL connections accessing session store **URL:** \ **Category:** Rails\ **Created:** [April 25, 2007, 6:43am UTC](https://www.ruby-forum.com/t/lost-mysql-connections-accessing-session-store/92861 "2007-04-25T06:43:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![DZDZDZ](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f475e1/32.png) [@DZDZDZ](https://www.ruby-forum.com/u/DZDZDZ)\ **Post date:** [April 25, 2007, 6:43am UTC](https://www.ruby-forum.com/t/lost-mysql-connections-accessing-session-store/92861/1 "2007-04-25T06:43:34Z")
Since putting our application into production, I’ve been seeing random lost connections to our MySQL server, always when the application is accessing the session store, and at no other time. Apparently randomly, I get the error: Mysql::Error: Lost connection to MySQL server during query: SELECT \* FROM sessions WHERE (session\_id = ‘xxxxxxxx’) LIMIT 1 I’ve spent quite a bit of time googling around and searching appropriate forums, without finding a definitive answer to tackling this problem. I’ve found several posts that indicate moving to AR session store starts this problem. I’ve investigated the possibility of packet size causing problems, but sessions are typically averaging around 300 bytes, and one error that I was able to track down specifically only had a session store of 322 bytes. I’ve seen many suggestions to use the mysql gem driver to fix the problem, however, we’re already using it, so that isn’t the problem. Setting the Interactive timeout was another common suggestion, but the AR verification timeout is set to 1/2 of the interactive timeout set in MySQL. I’m tempted to just set the max\_allowed\_packet to maybe double the size of the current 16MB and see what happens, but I don’t see how that would help because the session stores seem so small, even with overhead, I don’t see how a session store of 300-400 bytes could add up to a packet that is over 16MB. Further, I’m unsure if all I have to do is set max\_allowed\_packet in MySQL and be done, or if there is some further configuration in Rails that has to be done . Some googling suggest that it is automatically calculated from the server setting, but I’m unsure of that. I’m wondering whether I should just ditch AR session store and go with mem-cached. It seems like a lot of people have run into this, but aside from the standard answers that I’ve already checked, except for the packet size, there doesn’t seem to be a lot of other answers out there. Has anyone else run into this? Can anyone tell me anything else to check? How about the mem-cache option, any thought there? Thanks for any help in this regard DZ ---
**Author:** ![DZDZDZ](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f475e1/32.png) [@DZDZDZ](https://www.ruby-forum.com/u/DZDZDZ)\ **Post date:** [April 25, 2007, 6:11pm UTC](https://www.ruby-forum.com/t/lost-mysql-connections-accessing-session-store/92861/2 "2007-04-25T18:11:36Z")
Bump. ---
**Author:** ![DZDZDZ](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f475e1/32.png) [@DZDZDZ](https://www.ruby-forum.com/u/DZDZDZ)\ **Post date:** [April 26, 2007, 12:12am UTC](https://www.ruby-forum.com/t/lost-mysql-connections-accessing-session-store/92861/3 "2007-04-26T00:12:37Z")
DZ, Have you tried removing/uncommenting your AR verification timeout? This (I think) fixed the same issue for me. Cheers, Rob ---
**Author:** ![DZDZDZ](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f475e1/32.png) [@DZDZDZ](https://www.ruby-forum.com/u/DZDZDZ)\ **Post date:** [May 3, 2007, 1:10am UTC](https://www.ruby-forum.com/t/lost-mysql-connections-accessing-session-store/92861/4 "2007-05-03T01:10:33Z")
I’ve solved this same problem beofre in and outside of rails using a low priority sleeper thread at the bottom of env.rb: Thread.new{ loop{ sleep(60\*60); ActiveRecord::Base.verify\_active\_connections! } }.priority = -10 Cheers- -Ezra On May 2, 2007, at 3:54 PM, DZ wrote: > timeout verification, since our production environment is behind a > On Apr 25, 5:11 pm, “Rob Bevan” [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > > I’ve spent quite a bit of time googling around and searching > > > I was able to track down specifically only had a session store of > > > in MySQL. > > > suggest that it is automatically calculated from the server setting, > > > Has anyone else run into this? Can anyone tell me anything else to > > > check? How about the mem-cache option, any thought there? > > > > > Thanks for any help in this regard > > > > > DZ > > > – Ezra Z. – Lead Rails Evangelist – removed\_email\_address@domain.invalid – Engine Y., Serious Rails Hosting – (866) 518-YARD (9273) ---
**Author:** ![DZDZDZ](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/f475e1/32.png) [@DZDZDZ](https://www.ruby-forum.com/u/DZDZDZ)\ **Post date:** [May 3, 2007, 12:55am UTC](https://www.ruby-forum.com/t/lost-mysql-connections-accessing-session-store/92861/5 "2007-05-03T00:55:32Z")
Rob, After trying several permutations of MySQL server settings and even changing some bits of code without success, I tried your suggestion and removed the verification timeout from our production environment. it seems like this would not have made a difference, but it did. We went from having 5-10 lost connections when looking up session information to zero. It has been like this for several days now, so I’d say that this is now fixed. We probably didn’t even need the timeout verification, since our production environment is behind a load balancer that does health checks every few seconds. In theory, (I haven’t confirmed, bad me) this would mean that the mongrel processes hit the database at least once during the 8 hour timeout period we have set on the MySQL server. Thanks for your suggestion! I don’t think I would have looked in that direction without it. DZ