Attempting to upload a crash report, apport failed with "HTTP Error 500: Internal Server Error"

This looks like a temporary Launchpad.net downtime. Can you please do

  touch /var/crash/*

? This should trigger apport-gtk again for the same issue. Does it work now?

Hmm... I also tried to submit the crashfile via the web site directly (as an attachment to a bug report). It also failed with an Error 500 (if I recall correctly).

At this time, I don't have the same 96M file anymore. I worked around the problem by doing an "apport-retrace -c" to remove the core dump and was able to attach that 160K file with no problem.

I just submitted a 26M file and it worked fine.

If you're convinced this is a transient site bug, feel free to close, if I get this happening again with another crashfile, I'll reopen.

Ah, if it just fails with big files, then this is rather a Launchpad problem.

Bjorn, does the cloakroom limit the size of uploaded files? If so, should apport just discard uploads which are that large? If that is not the case, do you think this was a transient problem?

On Tue, Feb 27, 2007 at 12:39:37PM -0000, Martin Pitt wrote:
> Bjorn, does the cloakroom limit the size of uploaded files? If so,
> should apport just discard uploads which are that large? If that is not
> the case, do you think this was a transient problem?

At the moment the cloakroom doesn't limit the size, although it might do
in the future. As for this problem, it's definitely some bug in
Launchpad, since you should never get a 500 page. I don't have access to
see what really went wrong, so I'll have to look at the OOPS report
tomorrow to find out.

Closing apport task then and keeping malone task. Thanks, Bjorn!

Just got it again with another 92MB evolution crashfile (it happened some time in the last ~8 hours)

Sorry, I missed this problem the other when I logged one similar to this. Bug# 95822 is the one I opened up. You can look at the detail that I provided, but to reiterate my bug report, there does seem to be a file size limitation.

I generated a massive firefox crash report (approximately 120Mbytes). If I tried to send that one up either manually or as part of the apport reporting system I would receive the internal 500 error. Since the developer only needed the CoreDump from this report, because he got everything else I took that file and tried to send it. I got at error there too. The file size was just over 90 Mbytes.

When I changed the way I was compressing the file I got it down to about 85 mbytes in size. This one could then be uploaded properly. Any file size over 90 Mbytes seemed to fail for me, so some part of the transport is putting in a limit to what can be uploaded...

I hope this help a little bit, bit I can confirm this problem with a little more anecdotal information of my own.... Good Luck.

Is this still happening? I haven't see any OOPSes related to this lately.

I'm no longer using pre-releases of Ubuntu, so apport is off, and I haven't had any major crashes in large applications, so I don't know.

I suppose this might as well be marked as a dupe of bug 95822.

On Tue, Aug 26, 2008 at 08:08:56PM -0000, Michael R. Head wrote:
> I'm no longer using pre-releases of Ubuntu, so apport is off, and I
> haven't had any major crashes in large applications, so I don't know.
>
> I suppose this might as well be marked as a dupe of bug 95822.

Indeed.

    duplicate 95822