Bug 11978 – Bugzilla error attaching file to bug

• Status: RESOLVED
• Resolution: FIXED
• Component: New Bugs

[Patricia Warwick]

Actually this is more of a Bugzilla bug. I tried to post an attachment to another bug I just entered, and I got an error. Then I tried to mail info about this error [e-mail] and that email was returned as undeliverable. Here is the email which includes details of the original error:

Delivery to the following recipient failed permanently:

    [e-mail]

Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 9): 550 5.1.1 <[e-mail]>: Recipient address rejected: User unknown in virtual mailbox table

  ----- Original message -----

Received: by 10.70.47.19 with SMTP id u19mr23714636wxu.1167142553063;
       Tue, 26 Dec 2006 06:15:53 -0800 (PST)
Received: by 10.70.13.11 with HTTP; Tue, 26 Dec 2006 06:15:52 -0800 (PST)
Message-ID: <[e-mail]>
Date: Tue, 26 Dec 2006 09:15:53 -0500
From: "Patricia Warwick" <[e-mail]>
Reply-To: [e-mail]
To: [e-mail]
Subject: Error attaching file to bug
MIME-Version: 1.0
Content-Type: multipart/alternative;
       boundary="----=_Part_65928_16547552.1167142553032"

------=_Part_65928_16547552.1167142553032
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

DBD::mysql::st execute failed: Got a packet bigger than
'max_allowed_packet' bytes [for Statement "INSERT INTO attachments
     (thedata, bug_id, creation_ts, filename, description,
      mimetype, ispatch, isprivate, submitter_id)
     VALUES (?, 11977, '2006-12-26 06:18:05', 'Safari.crash copy.log',

  ----- Message truncated -----

[David Kilzer (:ddkilzer)]

Patricia, this probably means that the file you're trying to attach is too big.

In the case of the Safari.crash.log, you really only need to include the LAST crash log in the file (which is at the end, not the beginning).  Crash logs are separated by "**********" lines.  Please make a copy of Safari.crash.log locally, delete the content above the last crash, then post the smaller file.  Thanks!

[Patricia Warwick]

I guess that when I thought I was extracting this crash from the log that I was not doing so. I had previously cleared the log (or thought I had) but the log file was 1.2 MB. I've changed that. But is anyone supporting the Bugzilla ... i.e. should that address be valid?

[Mark Rowe (bdash)]

Why did you decide to email [e-mail]?  Is that listed somewhere as the contact address for Bugzilla issues?

The error you got was:

DBD::mysql::st execute failed: Got a packet bigger than
'max_allowed_packet' bytes [for Statement "INSERT INTO attachments
     (thedata, bug_id, creation_ts, filename, description,
      mimetype, ispatch, isprivate, submitter_id)
     VALUES (?, 11977, '2006-12-26 06:18:05', 'Safari.crash copy.log',

This suggests that there is an inconsistency between the configuration of maximum upload size in Bugzilla and the maximum allowable MySQL packet size in the database daemon.

[Patricia Warwick]

Yes ... [e-mail] is the email address that comes up when any bugzilla error is reported and the user is instructed to forward such errors to that address. I have a small bugzilla system myself and you can configure it with a specific address for bugzilla errors.

[Mark Rowe (bdash)]

Thanks Patricia.

Tim, are you able to have the two relevant settings adjusted? (Bugzilla admin email address should be set to something sane, and maximum upload size needs reconciled with the MySQL maximum packet size).

[Timothy Hatcher]

I corrected the admin email, it now points to my address. 

The max size for attachments and patches is 2000kb. I am not sure what the default MySQL max_allowed_packet size is, but it must be smaller than 2000kb. I would have thought bugzilla whould have bailed when before it inserted into the database if the size was larger than 2000kb...

[Mark Rowe (bdash)]

http://dev.mysql.com/doc/refman/5.0/en/server-parameters.html suggests that the maximum packet size is 1MB.  Patricia reported seeing the error while uploading a 1.2MB file, which would be small enough to sneak in under Bugzilla's check for a large file while exceeding the maximum MySQL packet size.  I'd suggest bumping the MySQL max_allowed_packet value in the server configuration up to something much larger -- the 'mysql' command line client defaults to 16MB, for example.

[David Kilzer (:ddkilzer)]

I haven't had any problems uploading files recently, nor have I heard of others having problems recently.

Patricia, if this happens again, please reopen this bug or open a new one.

[Mark Rowe (bdash)]

This was still an issue, but I just tweaked the MySQL server configuration such that the max_allowed_packet size was larger than our setting for maximum Bugzilla attachment size.