357689 - When attempting large attachments getting attachment.cgi: CGI.pm Server closed during multipart read ( client aborted?) Compilation failed in require at /var/www/bugzilla-2.20 /attachment.cgi line 43.

Status: RESOLVED INCOMPLETE

(Bugzilla :: Attachments & Requests, defect)

Description

[Annette Brady]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 1.0.3705; .NET CLR 2.0.50727)
Build Identifier: Bugzilla 2.20

I attempted to create a my.cnf and added the 

   /etc/my.cnf as below.

   If you are using MySQL 4.0 or newer, enter:
  [mysqld]
  # Allow packets up to 1M
  max_allowed_packet=1M
I also change the called 'maxattachmentsize' (default =
   1000 Kb) that controls the maximum allowable attachment size. 
I also tried using 'maxlocalattachment' parameter. and it does not work.

I always get the same error as listed above.


Reproducible: Always

Steps to Reproduce:
1.Increased parameters as listed above under Buguzilla-2.20
2.Attempt to attach a large file 
3.Should get error listed under summary

Actual Results:  
Attach a file as a patch, a text file, or as a local file.

get error at web browser attachment.cgi: CGI.pm Server closed during multipart read ( client aborted?) Compilation failed in require at /var/www/bugzilla-2.20 /attachment.cgi line 43. 

Expected Results:  
attachment.cgi: CGI.pm Server closed during multipart read ( client aborted?) Compilation failed in require at /var/www/bugzilla-2.20 /attachment.cgi line 43. 

Thanks for your help.

Comment 1

[Jeremy Baron]

This looks like a Bugzilla install other than BMO.  (I'm assuming that I'd recognize the name of anyone messing with BMO config or the db for it.)

->  Bugzilla :: Attachments & Requests

Comment 2

[Dave Miller [:justdave]]

How big is the file you're trying to upload?

The settings you indicate that you're using set the maximum size to 1MB.  If you're uploading something bigger than that, it's going to fail.

You also mention that you're using 2.20...  I'm pretty sure this was fixed in 2.22 to give a meaningful error message instead of crashing/timing out.

Comment 3

[Frédéric Buclin]

We got no additional information from the reporter in the last 11 months, and this bug is about Bugzilla 2.20 which is restricted to security fixes anyway. Closing this bug.