# ActiveRecord::StatementInvalid Mysql::Error: MySQL server has gone away

**URL:** <https://www.ruby-forum.com/t/activerecord-statementinvalid-mysql-mysql-server-has-gone-away/193734>\
**Category:** Rails\
**Created:** [August 23, 2010, 6:53pm UTC](https://www.ruby-forum.com/t/activerecord-statementinvalid-mysql-mysql-server-has-gone-away/193734 "2010-08-23T18:53:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![anywho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/82dd89/32.png) [@anywho](https://www.ruby-forum.com/u/anywho)\
**Post date:** [August 23, 2010, 6:53pm UTC](https://www.ruby-forum.com/t/activerecord-statementinvalid-mysql-mysql-server-has-gone-away/193734/1 "2010-08-23T18:53:37Z")

</div>

Suddenly exceptional is sending emails about Mysql having gone away in  
production. This had not been an issue until, well, today. No changes  
have even been made. We see this with an internal product as well.  
Does anyone know how to prevent this from happening? Why isn’t rails  
handling this more gracefully? Or can I help it to.