Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 304899 - Attachment fails with error 500
Summary: Attachment fails with error 500
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-13 16:39 UTC by Timothy Miller
Modified: 2011-10-30 23:16 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Miller 2010-02-13 16:39:09 UTC
I'm trying to attach a file that is 65515 bytes in size to a bug I'm reporting.  The filename is "vim_build.log", and there's no description (I've tried WITH description too, same error).

When I "Submit" the attachment, bugzilla doesn't respond for a long time, and then I get this error:

500 Internal Server Error
>>>
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@gentoo.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Apache Server at bugs.gentoo.org Port 80
<<<

I've had this happen a lot recently, and it's always when I try to attach a log file.  Does bugzilla have a problem handling files with ".log" in the filename?  Also, "plain text" is manually selected.

Right now, it's 11:38AM EST, Feb 13.

Reproducible: Always
Comment 1 Timothy Miller 2010-02-13 16:44:41 UTC
This turns out to be a permissions problem on my end.  When I add +r to the file, I can attach it.  What I think is happening is that the server is being sent an empty or nonexistant file.  I should get get back an error immediately that it didn't get a valid file.  Of course, my web browser should report an access error, but that's a separate issue.