[ZODB-Dev] RelStorage gives MySQL error when rebuilding catalog in Plone/ZMI

2012-03-27 Thread J Z
I have a Plone 4.1 site using RelStorage to store the zodb in MySQL 5.5 
server. The site has 700 objects cataloged and the database is less than 300MB 
after packing. I won't consider it's a large site. When I tried to update 
catalog or clear  
rebuild the catalog, I got the following error: 

Traceback (innermost last): Module ZPublisher.Publish, line 134, in publish 
Module Zope2.App.startup, line 301, in commit Module transaction._manager, line 
89, in commit Module transaction._transaction, line 329, in commit Module 
transaction._transaction, line 443, in _commitResources Module ZODB.Connection, 
line 567, in commit Module ZODB.Connection, line 623, in _commit Module 
ZODB.Connection, line 682, in _store_objects Module relstorage.storage, line 
571, in store Module relstorage.adapters.mover, line 484, in mysql_store_temp 
Module relstorage.adapters.batch, line 67, in insert_into Module 
relstorage.adapters.batch, line 74, in flush Module relstorage.adapters.batch, 
line 110, in _do_inserts Module MySQLdb.cursors, line 174, in execute Module 
MySQLdb.connections, line 36, in defaulterrorhandler OperationalError: (2006, 
'MySQL server has gone away') The mysql was installed with most default 
settings. The wait_timeout is 28800 according to phpMyAdmin.
 Can someone give some idea what could be wrong and where I should start 
looking? Thanks! 
___
For more information about ZODB, see http://zodb.org/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev


Re: [ZODB-Dev] RelStorage gives MySQL error when rebuilding catalog in Plone/ZMI

2012-03-27 Thread J Z
Sorry about the terrible format. Please allow me to try it again.

I have a Plone 4.1 site using RelStorage to store the zodb in MySQL 5.5 
server. The site has 700 objects cataloged and the database is less than
300MB  after packing. I won't consider it's a large site. When I tried to 
update catalog or clear  rebuild the catalog, I got the following error: 

Traceback (innermost last):
* Module ZPublisher.Publish, line 134, in publish
* Module Zope2.App.startup, line 301, in commit
* Module transaction._manager, line 89, in commit
* Module transaction._transaction, line 329, in commit
* Module transaction._transaction, line 443, in _commitResources
* Module ZODB.Connection, line 567, in commit
* Module ZODB.Connection, line 623, in _commit
* Module ZODB.Connection, line 682, in _store_objects
* Module relstorage.storage, line 571, in store
* Module relstorage.adapters.mover, line 484, in mysql_store_temp
* Module relstorage.adapters.batch, line 67, in insert_into
* Module relstorage.adapters.batch, line 74, in flush
* Module relstorage.adapters.batch, line 110, in _do_inserts
* Module MySQLdb.cursors, line 174, in execute
* Module MySQLdb.connections, line 36, in defaulterrorhandler
OperationalError: (2006, 'MySQL server has gone away') 

The mysql was installed with most default settings. The wait_timeout is
28800 according to phpMyAdmin. Can someone give some idea what 
could be wrong and where I should start looking? Thanks!
___
For more information about ZODB, see http://zodb.org/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev


Re: [ZODB-Dev] RelStorage gives MySQL error when rebuilding catalog in Plone/ZMI

2012-03-27 Thread Alexandre Garel

Le 27/03/2012 18:50, J Z a écrit :

Sorry about the terrible format. Please allow me to try it again.

I have a Plone 4.1 site using RelStorage to store the zodb in MySQL 5.5
server. The site has 700 objects cataloged and the database is less than
300MB  after packing. I won't consider it's a large site. When I tried to
update catalog or clear  rebuild the catalog, I got the following error:
snip
OperationalError: (2006, 'MySQL server has gone away')

The mysql was installed with most default settings. The wait_timeout is
28800 according to phpMyAdmin. Can someone give some idea what
could be wrong and where I should start looking? Thanks!


DuckDuckGo-ing OperationalError 'MySQL server has gone away'
gives me 
https://rapd.wordpress.com/2008/03/02/sqlalchemy-sqlerror-operationalerror-2006-mysql-server-has-gone-away/
is the pool_recycle parameter set at the right value in your case ?/(I 
will suggest less than the /wait_timeout)


how much time is spent between launch of request and OperationalError ?

Hope it helps,

Alex
___
For more information about ZODB, see http://zodb.org/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev


Re: [ZODB-Dev] RelStorage gives MySQL error when rebuilding catalog in Plone/ZMI

2012-03-27 Thread J Z
The error came out after about 50 seconds. I don't know the pool_recycle 
setting. Since I didn't change it, it would be whatever default by RelStorage 
or SQLAlchemy. But thanks to your comment, I was encouraged to look for more 
general MySQL solutions. Besides the wait_timeout setting, max_allowed_packet 
is another common reason for the 2006 error. It defaults 1MB. After change it 
to 16M, the catalog updated successfully. Hope this will be useful for someone 
too.




 From: Alexandre Garel alex.ga...@tarentis.com
To: zodb-dev@zope.org 
Sent: Tuesday, March 27, 2012 1:31 PM
Subject: Re: [ZODB-Dev] RelStorage gives MySQL error when rebuilding catalog in 
Plone/ZMI
 

Le 27/03/2012 18:50, J Z a écrit : 
Sorry about the terrible format. Please allow me to try it again. I have a 
Plone 4.1 site using RelStorage to store the zodb in MySQL 5.5 
server. The site has 700 objects cataloged and the database is less than
300MB  after packing. I won't consider it's a large site. When I tried to 
update catalog or clear  rebuild the catalog, I got the following error: 
snip
OperationalError: (2006, 'MySQL server has gone away')  The mysql was installed 
with most default settings. The wait_timeout is
28800 according to phpMyAdmin. Can someone give some idea what 
could be wrong and where I should start looking? Thanks! 
DuckDuckGo-ing OperationalError 'MySQL server has gone away'
gives me 
https://rapd.wordpress.com/2008/03/02/sqlalchemy-sqlerror-operationalerror-2006-mysql-server-has-gone-away/
is the pool_recycle parameter set at the right value in your case ?(I will 
suggest less than the wait_timeout)

how much time is spent between launch of request and
OperationalError ?

Hope it helps,

Alex

___
For more information about ZODB, see http://zodb.org/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev___
For more information about ZODB, see http://zodb.org/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev