502 bad gateway while automated crash reporting happening

Bug #114962 reported by Shirish Agarwal
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Apport
Confirmed
Undecided
Unassigned
Launchpad Bug Report Tool
New
Undecided
Unassigned

Bug Description

Hi all,
       Firefox had crashed. The end-bug report was a 22 MB crash report which apport was supposed to send. After showing the too & fro uploading bar for more than an hr. it said bad gateway. I had network monitor applet running so could see the traffic happening all the time. And the uploading was happening without an issue. Now don't understand why the bad gateway happened as I was able to navigate launchpad as well as other http://en.wikipedia.org/wiki/List_of_HTTP_status_codes also does the same error but doesn't tell much about what constitutes bad gateway & why does it happen. I think I have already reported this one before or not, but please look into it.

Revision history for this message
Daniel J Blueman (danielblueman) wrote :

I have been experiencing this with Gutsy Tribe-2 on AMD64. Apport is version 0.86.

Revision history for this message
Daniel J Blueman (danielblueman) wrote :

Since this prevents crash-reports with coredumps from being fed back, please set the priority to high. I had no proxy set while uploading and was using a fresh account.

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

Ah yes, I'm using ADSL broadband (2+ the marketing brochure says but who knows, but its ~ 256 kbps download, 64 kbps upload from tests done on speakeasy.net at

  through a modem+router. No proxy & dynamic IP . I use deluge-torrent without issues as well as download managers so as far as connection is concerned it should not be an issue. Any ideas?

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

Ah yes, I'm using ADSL broadband (2+ the marketing brochure says but who knows, but its ~ 256 kbps download, 64 kbps upload from tests done on speakeasy.net at various different times over period of many days.

Sorry for that incomplete sentence above :(

Revision history for this message
schnollk (schnollk) wrote :

experienced code 502 here, too. console log follows (apport-cli):

************************************************************

*** Scribus closed unexpectedly on 2007-11-03 at 23:59:53.

If you were not doing anything confidential (entering passwords or other
private information), you can help to improve the application by reporting
the problem.

What would you like to do? Your options are:
  R: Report Problem...
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (R/I/C): R

*** Collecting problem information

The collected information can be send to the developers to improve the
application. This might take a few minutes.
................................

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send complete report (recommended; 18.3 MiB)
  R: Send reduced report (slow Internet connection; 28.7 KiB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  C: Cancel
Please choose (S/R/V/K/C): S

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
99%
*** Error: Netzwerkproblem

Konnte Bericht nicht an Absturz-Datenbank übermitteln:

HTTP Error 502: Bad Gateway

Press any key to continue...

************************************************************

By the way, I got this from http://www.checkupdown.com/status/E502.html:
"...Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed."

Revision history for this message
Ben (benc) wrote :

I've just seen this. Apport uploaded a 10MB+ dump, then at the very end threw the "Bad Gateway" error. Any way to debug this?

Revision history for this message
Savvas Radevic (medigeek) wrote :

Confirmed on hardy heron 8.04 beta updated
I attempted to upload a nautilus ~10mb crash report using apport-cli

This could be a problem related to apport being aggressive to its upload bandwidth usage:
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/196439

I have adsl 512/64kbps connection if that matters

apport-gtk: Installed: 0.105
apport: Installed: 0.105

$ apport-cli -c _usr_bin_nautilus.1000.crash

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (9.2 MiB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  C: Cancel
Please choose (S/V/K/C): s

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
99%
*** Error: Network problem
Could not upload report data to crash database:
HTTP Error 502: Bad Gateway
Press any key to continue...

Changed in apport:
status: New → Confirmed
Revision history for this message
Savvas Radevic (medigeek) wrote :

Could it be the fact that I'm registered on the edge (beta) server of launchpad?
It still happens, I think this problem resides to the launchpad server

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

It just happened to me, and i'm on edge too.
a 30MiBs backtrace for pidgin.

Revision history for this message
Luke Plant (spookylukey) wrote :

I don't think is a duplicate. Bug #95822 seems to describe an error due to edge.launchpad.net being disabled, and is supposedly fixed due to changing to launchpad.net.

But this bug happens after finishing uploading. And it's not fixed, because I just got it, after uploading a 12 Mb korganizer crash report - "502 Bad Gateway".

I think duplicate status should be removed, and it should be marked as high priority, as it stops other bugs being reported. It's also very frustrating and disappointing to be stopped in the process of dealing with one bug by another bug!

Revision history for this message
Caysho (caysho) wrote :

I got this error when uploading a mythfrontend.real crash report that was 30 MB, from a mythbuntu 9.04 beta (with updates).
It nearly completed the upload, then failed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.