[rt-users] mysql database copy fails with packet bigger than allowed

[Sparhawk, Mark]

I just ran into this problem yesterday. It is my understanding that this
problem occurs when mysqldump has a max_allowed_packet that is larger than
the mysqld's max_allowed packet here's a couple snippets from my my.cnf.



[mysqld]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock
log             = /var/log/mysql/mysql.log
skip-locking
key_buffer = 256M
max_allowed_packet = 16M
...
...
...
[mysqldump]
quick
max_allowed_packet = 16M


I set the max_allowed_packet under the mysqld section to be equal to the
mysqldump section and everything worked like a champ. Good Luck.

-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com
[mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Harald
Wagener
Sent: Tuesday, August 30, 2005 9:15 AM
To: Les Mikesell
Cc: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] mysql database copy fails with packet bigger than
allowed

Hello,
I had this a few days ago and retaliated by removing a word document  
from the attachments table, which obviously is not the clean way to  
proceed.

You should check for the biggest attachment in the attachments table  
by the following statement:

select max(length(Content)) from Attachments;

This should give You the actual size of the largest attachment in the  
database in bytes. Setting max_allowed_packet to something slightly  
larger than this should help.

If this does not help, there might be a problem with the attachment  
itself.

Regards,
     Harald
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Buy your copy of our new book, RT Essentials, today! 

Download a free sample chapter from http://rtbook.bestpractical.com