1

1

Importing from bugzilla now goes through several hundred bugs at a time bug then hits a FogBugz Internal Error. The first time this happened I still had customErrors on so I don't know the exact info, but after turning it off and restarting the import from where it left off I got this:

Error:  Packets larger than max_allowed_packet are not allowed.
Stack Trace:    Hide Stack Trace
MySql.Data.MySqlClient.MySqlException: Packets larger than max_allowed_packet are not allowed.
  at MySql.Data.MySqlClient.MySqlStream.StartOutput (UInt64 length, Boolean resetSequence) [0x00000] 
  at MySql.Data.MySqlClient.NativeDriver.ExecuteCommand (DBCmd cmd, System.Byte[] bytes, Int32 length) [0x00000] 
Browser:     Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-US) AppleWebKit/534.12 (KHTML, like Gecko) Chrome/9.0.572.1 Safari/534.12
Source:  MySql.Data
OS Version:  Unix 2.6.18.194
Database:    MySQL
ixPerson:    2
QueryString:     ?pg=pgImportBugzilla&
URL:     /default.asp
Content Type:    application/x-www-form-urlencoded
Content Length:  128
Local Addr:  10.6.12.105
Remote Addr:     10.6.12.92
Time:    11/15/2010 2:56:29 PM
Post:    sURL=http://bugzilla.****.com/&sUser=****&sPassword=*****&nStartBug=630&nStopBug=9999&OK=OK

Update: This is repeatable for particular bugs (just two so far). It may have something to do with large attachments -- the bug I'm looking at now has a 6MB log file attached to it.

flag
max_allowed_packet is a MySQL thing, a limit on the maximum size of a row. Looks like it defaults to 1MB in mysqld, but can be configured to be larger. I'll try doing that. dev.mysql.com/doc/refman/5.1/en/… – Jens Alfke Nov 16 2010 at 0:27

2 Answers

1

I solved it by configuring MySQL to have a larger max_packet_size. On Unix, edit /etc/my.cnf and insert the following line beneath the "[mysqld]" line:

max_allowed_packet=50M

and add at EOF, after a blank line:

[client]
max_allowed_packet=50M

Then restart both mysqld and FogBugz.

It would be nice if FogBugz would store large attachments in the filesystem instead of MySQL. It's generally considered bad to have huge rows in a database (our largest attachment is about 20MB.)

link|flag
FogBugz used to use the filesystem, but we use the database now for the simple reason that it makes backups and transfers easier. There are downsides as well, of course. – Ted Nov 16 2010 at 14:36
This was perfect for OSX Server as well, which has the line but is set to 1M by default. Thx. – Infinite Sep 19 at 5:50
1

max_allowed_packet is one of the gotchas of MySQL configuration for FogBugz. Please take a look at the full list to make sure you don't hit any of the others.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.