Bug 1902312 - abrt retrace takes a very long time
Summary: abrt retrace takes a very long time
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 33
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1939467
TreeView+ depends on / blocked
 
Reported: 2020-11-27 16:57 UTC by Ivan Molodetskikh
Modified: 2022-11-21 03:29 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-05 15:24:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ivan Molodetskikh 2020-11-27 16:57:04 UTC
Description of problem:
I had a gnome-software crash and started a remote retrace to report the bug. 3.5 hours later it's still going. I'm not sure if it hanged, it keeps adding dots.

Version-Release number of selected component (if applicable):
abrt-2.14.4-7.fc33.x86_64


--- Running report_uReport ---
('report_uReport' completed successfully)

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Preparing an archive to upload
You are going to upload 77,3 MiB. Continue? 'YES'
Uploading 77,3 MiB
Upload successful
Retrace job started
Analyzing crash data
................................................................................
...............
Generating backtrace
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
......................

Comment 1 Christian Kujau 2020-12-07 21:50:51 UTC
In my case it was "gnome-shell" that crashed, so generating the backtrace might take a long time depending on how big or complex the core dump is. After some hours of printing dots it did eventually complete (but then failed again due to a maintenance reboot, according to Matej over in bug 1885154 - thanks!)



--- Running report_uReport ---
('report_uReport' completed successfully)

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Preparing an archive to upload
You are going to upload 19.1 MiB. Continue? 'YES'
Uploading 19.1 MiB
Upload successful
Retrace job started
Analyzing crash data
................................................................................
......................................
Generating backtrace
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
.......An error occurred while connecting to 'https://retrace.fedoraproject.org'
Could not connect: Connection refused
Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'YES'
Analyzing coredump 'coredump'
Cleaning cache...
Cache cleaning has finished
Coredump references 200 debuginfo files, 400 of them are not installed
Initializing package manager
Setting up repositories
Looking for needed packages in repositories
[....]

Comment 2 Miroslav Suchý 2021-01-05 15:11:11 UTC
This should be fixed now. Can you confirm @mgrabov

Comment 3 Matej Grabovsky 2021-01-05 15:24:21 UTC
Yes, this should be fixed with the recent addition of hard timeouts.

Feel free to reopen if you encounter the problem again.

Comment 4 John Kizer 2022-11-21 03:29:13 UTC
Hi - Sorry, I'm not sure if this is appropriate to report here, but Google led me here as the gnome-photos app crashed on me (after clicking the "Import" button with my iPhone connected, FWIW), I went into the Problem Reporting tool to upload a report, and after about 25 minutes on the "Analyzing crash data" stage, with dots continuing to be added, I got a "Retrace failed. Try again later and if the problem persists report this issue please." message. Is that related to what was filed here, or totally separate?

Log shown in the window titled "gnome-photos killed by SIGSEGV - org.freedesktop.GnomeAbrt":
--- Running report_uReport ---
('report_uReport' completed successfully)

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Preparing an archive to upload
You are going to upload 21.2 MiB. Continue? 'YES'
Uploading 21.2 MiB
Upload successful
Retrace job #697856428 started
Analyzing crash data
................................................................................
............................................


Thanks,


Note You need to log in before you can comment on or make changes to this bug.