[rt-users] MySQL Server has Gone a way; No ticket created but e-mail is sent

[Schultz, Eric]

> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com 
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf 
> Of Nick Metrowsky
> Sent: Friday, March 03, 2006 1:42 PM
> To: Chaim Rieger
> Cc: rt-users at lists.bestpractical.com
> Subject: RE: [rt-users] MySQL Server has Gone a way;No ticket 
> created but e-mail is sent
> 
> Hi Chaim,
> 
> Thank you for writing. Please find below the output of my 
> MySQL variables from mysqladmin.
> 
> Thank you for your help in advance.
> 
> Take care!
> 
> Nick
> 
> +---------------------------------+---------------------------
> | max_allowed_packet              | 1047552                   
>

This is the variable of interest.  Unfortunately, MySQL doesn't tell you
why it dropped the connection, it just does it.  In some testing, I
found that if you are trying to do too large of an extended insert, or a
single insert is too large, your insert will fail.  This is normally
caused by large attachments, such as those over 20MB.  In your case,
anything over 1MB will fail, because that's what max_allowed_packet is
set at.  I'd bet that the 1% of the time this happens is when someone
attaches a large file.  Increase this variable and modify mysql so that
this is something that is set whenever the daemon starts up.  To set
this in the current running daemon:

mysql> set global max_allowed_packet=1677216;