As I originally (probably erroneously) reported to abrt: [1]
--- Running report_uReport ---
Failed to upload uReport to the server 'https://retrace.fedoraproject.org/faf' with curl: Failed to connect to retrace.fedoraproject.org port 443 after 133856 ms: Could not connect to server
Error: curl_easy_perform: Timeout was reached
('report_uReport' exited with 1)
…appears every time I attempt to abrt report. Is this true for anyone else?
→ https://status.fedoraproject.org
→ https://pagure.io/fedora-infrastructure/issue/12955
notably:
retrace/abrt/faf will be down and not accepting user reports
Yes, this is part of a planned datacenter move.
See https://www.fedorastatus.org/
Things have taken longer than expected due to bad weather in the region
where the new datacenter is. ;(
Hopefully it will be back soon…
kevin
Now that FAF appears to be back, I still don’t appear to be able to generate FAF traces for old bugs, at least via gnome-abrt-1.4.3-8.fc43: [1]
--- Running report_uReport --- Server responded with an error: 'Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing' --- 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 --- Generating backtrace Backtrace is generated and saved, 160044 bytes --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#2420701' was found Searching for updates No updates for this package found --- Running report_Bugzilla --- This problem was already reported to Bugzilla (see 'https://bugzilla.redhat.com/show_bug.cgi?id=242070'). Do you still want to create a new bug? 'NO' --- Running post_report --- This problem does not have an uReport assigned.
Can I force abrt-2.17.8-1 to regenerate them? I’ve managed to generate retrace.fedoraproject.org/faf/reports/bthash/2c694f59becd42d6cd499ee8572ff81d64400b89, [2] but one of the best attribtes of FAF is that it tracks crashes that abrt doesn’t consider sufficiently useful to report to RHBZ.