MySQL has gone away (again)

2010-01-20 Thread grassoalvaro
Hi, i have problem with MySQL (like many others on groups and google). I have tried everything that i found, but nothing helped. This is my SQLAlchemy config: sqlalchemy.convert_unicode = true sqlalchemy.pool_size = 100 sqlalchemy.pool_recycle = 3600 sqlalchemy.url = mysql://user:passw...@127.0.

Re: MySQL has gone away (again)

2010-01-20 Thread Garland, Ken R
There are a few things which might cause this issue. Have a look at the following: *wait_timeout* *connect_timeout* *max_allowed_packet* I have no idea what your apps are trying to do in order to cause this so I'm not able to speak about that. Have a look at them to determine if any of the above

Re: MySQL has gone away (again)

2010-01-20 Thread Diana Clarke
This worked for me (using engine_from_config): from pylons import config from sqlalchemy import engine_from_config from foo.model import init_model engine = engine_from_config(config, 'sqlalchemy.') init_model(engine) Otherwise (using create_engine), make

Re: MySQL has gone away (again)

2010-01-21 Thread grassoalvaro
mysql.config wait_timeout=90 max_allowed_packet=1M connect_timeout=300 I fixed my pylons configurations set pool_size to 60 but didn't help. Application is very simple, just 2 controllers, nothing complicated (this app .I have many others with the same problem. Currently i'm using cron to sending

Re: MySQL has gone away (again)

2010-01-21 Thread Ross Vandegrift
On Thu, Jan 21, 2010 at 12:05:43AM -0800, grassoalvaro wrote: > mysql.config > > wait_timeout=90 > max_allowed_packet=1M > connect_timeout=300 > > I fixed my pylons configurations set pool_size to 60 but didn't help. > Application is very simple, just 2 controllers, nothing complicated > (this ap

Re: MySQL has gone away (again)

2010-01-21 Thread Didip Kerabat
As far as i know, this problem is caused by having sqlalchemy.pool_recycle value larger than my.cnf [mysqld] connect_timeout - Didip - On Thu, Jan 21, 2010 at 8:15 AM, Ross Vandegrift wrote: > On Thu, Jan 21, 2010 at 12:05:43AM -0800, grassoalvaro wrote: > > mysql.config > > > > wait_timeout=90

Re: MySQL has gone away (again)

2010-02-01 Thread Chris Kimm
> As far as i know, this problem is caused by having sqlalchemy.pool_recycle > value larger than my.cnf [mysqld] connect_timeout I wasn't able to verify this in my environment. I set sqlalchemy.pool_recycle to 30 and connect_timeout to 60 in my.cnf and I still was getting 'MySQL server has gone aw