Show Previous Reports doesn't work for a user with lots of them

[IKT]

In the control panel under security and privacy > diagnostics > I have send error reports to Canonical ticked, and there is a button to 'Show Previous Reports'

When I click on this I get taken to a page which presents the following:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /user/510841b87d15dc78a2b05dfaf72c23b03d3344aa07556d7f25bd70b7e4a7aa38e6df5e681eba3d61108ddabf5a23c98006e537992be7ce057529508a6724bb88.

Reason: Error reading from remote server

Apache/2.2.22 (Ubuntu) Server at errors.ubuntu.com Port 443

[Brian Murray (brian-murray)]

I've recreated this error by visiting the following url:

https://errors.ubuntu.com/user/510841b87d15dc78a2b05dfaf72c23b03d3344aa07556d7f25bd70b7e4a7aa38e6df5e681eba3d61108ddabf5a23c98006e537992be7ce057529508a6724bb88

[IKT (ikt)]

It fixed itself!

I'd say it took so long to show up and was timing out because I report a lot of bugs.

5124 reports apparently.

Keeping this open in case someone has some spare time and feels like implementing something to deal with people who have reported a large amount of errors.

[Brian Murray (brian-murray)]

This is probably because we switched to a new database which (temporarily) doesn't have all of your previous reports. Given the volume of crashes that you are reporting, I'd expect it to timeout again rather soon.

[Vindicator (vindicator)]

I'm also encountering this issue.
I have tried over the past couple of days. I have never been able to view that page.

[Brian Murray (brian-murray)]

A better approach on this page, instead of loading all the error reports, would be loading the first one hundred and using an infinite scroll.

[Vindicator (vindicator)]

I am having my doubts that I would have many reports submitted since I've really only begun to use Ubuntu as my primary OS.

[Brian Murray (brian-murray)]

@Vindicator - can your provide me with the contents of /var/lib/whoopsie/whoopsie-id? or the url you visit to see your previous reports.

[Vindicator (vindicator)]

@Brian Murray
510841b87d15dc78a2b05dfaf72c23b03d3344aa07556d7f25bd70b7e4a7aa38e6df5e681eba3d61108ddabf5a23c98006e537992be7ce057529508a6724bb88

[Bryan Quigley (bryanquigley)]

Another example file - https://errors.ubuntu.com/user/510841b87d15dc78a2b05dfaf72c23b03d3344aa07556d7f25bd70b7e4a7aa38e6df5e681eba3d61108ddabf5a23c98006e537992be7ce057529508a6724bb88

I've uploaded a lot of crash reports. Is there any way (except manually reviewing the stracktrace) for me to associate a crash I just had with a bug without this?

[Brian Murray (brian-murray)]

You can check /var/log/syslog for messages from whoopsie e.g.

May 20 07:48:56 impulse whoopsie[3019]: [07:48:56] Parsing /var/crash/_usr_bin_audacity.1000.crash.
May 20 07:48:56 impulse whoopsie[3019]: [07:48:56] Uploading /var/crash/_usr_bin_audacity.1000.crash.
May 20 07:49:03 impulse whoopsie[3019]: [07:49:03] Sent; server replied with: No error
May 20 07:49:03 impulse whoopsie[3019]: [07:49:03] Response code: 200
May 20 07:49:03 impulse whoopsie[3019]: [07:49:03] Reported OOPS ID 58445722-feff-11e4-aeee-fa163e22e467

[Bryan Quigley (bryanquigley)]

Thanks! (for any one else reading, do https://errors.ubuntu.com/oops/<oops-id> )

[Phil P (pgpndw)]

Should the contents of /var/lib/whoopsie/whoopsie-id be unique to each installed system?

I ask because my version of this file also contains the string 510841b8 7d15dc78 a2b05dfa f72c23b0 3d3344aa 07556d7f 25bd70b7 e4a7aa38 e6df5e68 1eba3d61 108ddabf 5a23c980 06e53799 2be7ce05 7529508a 6724bb88 (spaces added for formatting), which is the same ID value as in the orignal report and in all the replies posted so far.

When I click the "show previous reports" button, I see a list that I'm convinced is *not* the list of crash reports sent from my system.

[Bryan Quigley (bryanquigley)]

Yes, it's gotta be per user not per machine - It shows me reporting a libreoffice bug 3 months ago for 12.04.. when this machine was definitely on 16.04.

On track for this bug, all the current example links work fine. Was this fixed on the recent code updates/machine upgrades? Can anyone reproduce it still?

[Phil P (pgpndw)]

@Bryan Quigley

Sorry if this is cluttering the bug report with stuff not directly related to the bug, but I'm not sure I understand you correctly.

Are you saying that each user should have a unique /var/lib/whoopsie/whoopsie-id, which is the same across all their Ubuntu installations, or are you saying that *all* Ubuntu installations should have the same ID string in /var/lib/whoopsie/whoopsie-id?

I had assumed that when I click the "Show Previous Reports" button on my machine, I would be shown a list of reports sent from *my* machine (I only have one). Is that assumption wrong?

To clarify my earlier reply, when I click "Show Previous Reports", I'm taken to the URL https://errors.ubuntu.com/user/510841b87d15dc78a2b05dfaf72c23b03d3344aa07556d7f25bd70b7e4a7aa38e6df5e681eba3d61108ddabf5a23c98006e537992be7ce057529508a6724bb88, which is the same URL as mentioned in Brian Murray's reply #1, and your own reply #9 above. I can see that the ID in that URL is taken from the whoopsie-id file, and is the same ID as that in IKT's original bug report and in Vindicator's reply #8.

[Bryan Quigley (bryanquigley)]

@Phil
I thought whoopsie-ids were unique. Now I'm a bit confused.

[Phil P (pgpndw)]

I've been looking into this, and I think I have an idea what the problem is. (It's not related to *this* bug report though):

I think the whoopsie-id is *supposed* to be unique to each machine, but it's generated from the system UUID retrieved from the PC's BIOS (which in turn is *supposed* to be unique).

When I retrieve my system UUID, I get this:

$sudo dmidecode -s system-uuid
00020003-0004-0005-0006-000700080009

... which is a very suspicious value for a UUID!

Putting that number into Google reveals that this has caused problems with many other systems too. I'm guessing it's a dummy value that's produced when the BIOS manufacturer didn't do their job right.

I'd put money on you having the same UUID value if you run the above command.

So, it looks like what's happening here is that a number of different Ubuntu installations have been submitting crashes to errors.ubuntu.com under the same ID, which is why we're all seeing an unexpectedly large list of reports when we click "Show Previous Reports".

Furthermore, I wouldn't be surprised to find that the logging software on errors.ubuntu.com is filtering out some of those reports because other information provided in the crash logs reveals them to be inconsistent with each other. Because there are crash reports that I *know* I've submitted that don't appear in that list.

[Bryan Quigley (bryanquigley)]

Nice analysis Phil - reported bug 1636954 to track it.

When I get some time, I'll investigate changing our machines to use MAC addresses or something else.