Bug 1902312
Summary: | abrt retrace takes a very long time | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ivan Molodetskikh <yalterz> |
Component: | abrt | Assignee: | abrt <abrt-devel-list> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 33 | CC: | abrt-devel-list, abrt-sig, jakub, jmilan, johnandmegh, mgrabovs, michal.toman, mihai, mmarusak, msuchy, redhat |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-01-05 15:24:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1939467 |
Description
Ivan Molodetskikh
2020-11-27 16:57:04 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 [....] This should be fixed now. Can you confirm @mgrabov Yes, this should be fixed with the recent addition of hard timeouts. Feel free to reopen if you encounter the problem again. 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, |