Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

crash in tracker3-miners results in 'Retrace failed. Try again later and if the problem persists report this issue please.' #411

Open
cmurf opened this issue Jan 31, 2021 · 5 comments
Labels

Comments

@cmurf
Copy link

cmurf commented Jan 31, 2021

Attaching abrt-cli report -vvv but it really isn't revealing why it failed.

Uploading 5.8 MiB
Upload successful
Retrace job started
Generating backtrace
Retrace job failed
Retrace failed. Try again later and if the problem persists report this issue please.
[2021-01-31 00:21:36] [I] Analyzing crash data

retracefailed.txt

abrt-retrace-client-2.14.5-1.fc33.x86_64

@msrb
Copy link
Member

msrb commented Feb 2, 2021

@mgrabovsky any idea if the retrace server had some outage or something?

@mgrabovsky mgrabovsky added the bug label Feb 3, 2021
@mgrabovsky
Copy link
Contributor

I'm not aware of an outage at that time.

@cmurf
Copy link
Author

cmurf commented Feb 3, 2021

I did try multiple times over about 30 minutes; the local backtrace was successfully used to file a new rhbz.

@mgrabovsky
Copy link
Contributor

@cmurf Yeah, this seems to be a bug with retracing certain packages. Could you please share the link to the created bug report or upload the dump directory? The information contained therein might shed some light on why this particular problem directory is— well, problematic.

@cmurf
Copy link
Author

cmurf commented Feb 3, 2021

Looks like a new bug was not filed, there was a dup and it just cc'd me on the dup.
https://bugzilla.redhat.com/show_bug.cgi?id=1909106

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants