Bug 1067440
| Summary: | [RFE] abrt-cli list should be more verbose | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | David Kutálek <dkutalek> | ||||||
| Component: | libreport | Assignee: | Matej Habrnal <mhabrnal> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Kyral <mkyral> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 7.0 | CC: | bblaskov, jfilak, lmiksik, mkyral | ||||||
| Target Milestone: | rc | Keywords: | FutureFeature | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | libreport-2.1.11-12.el7 | Doc Type: | Enhancement | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-03-05 13:26:00 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
David Kutálek
2014-02-20 13:10:13 UTC
Another user request raised in ABRT TD: "option for `abrt-cli list` to list only dirs/ids one per line (so that you can feed it to abrt-cli report) e.g. `-1` as in `ls`" Real life example of some random user (me):
$ abrt-cli list
id 509b0e5fc1ba7284d7fe6e16a9ad78d26d4f0bc4
Directory: /var/tmp/abrt/Python-2014-02-18-09:40:14-18345
count: 2
executable: /bin/nitrate
package: python-nitrate-0.9-2.fc20
time: Tue 18 Feb 2014 09:40:14 AM CET
uid: 1000
id 41681637cb245a0eeca67f95ec57700938d1a907
Directory: /var/tmp/abrt/Python-2014-02-18-09:21:52-14708
count: 1
executable: /bin/nitrate
package: python-nitrate-0.9-2.fc20
time: Tue 18 Feb 2014 09:21:52 AM CET
uid: 1000
id d14d9eee9f2089d7c232cc92e2a7d118edacf184
Directory: /var/tmp/abrt/Python-2014-02-13-11:46:12-28206
count: 1
executable: /bin/bkr
package: beaker-client-0.14.3-1.fc18
time: Thu 13 Feb 2014 11:46:12 AM CET
uid: 1000
id 058a45ff6ceca500e50cfceff764a5d7dcc2df3b
Directory: /var/tmp/abrt/oops-2014-02-01-12:46:17-4045-0
count: 3
package: kernel
time: Sat 01 Feb 2014 12:46:17 PM CET
id cbde981ea15f79438fa9d045b88b6d2b3beb228e
Directory: /var/tmp/abrt/oops-2014-02-01-12:46:17-4045-2
count: 1
package: kernel
time: Sat 01 Feb 2014 12:46:19 PM CET
id b1bd991cbbc91ddb6c72bf62b8057c0840cd370d
Directory: /var/tmp/abrt/Python-2013-11-26-14:26:05-27967
count: 2
executable: /bin/nitrate
package: python-nitrate-0.9-2.fc20
time: Tue 26 Nov 2013 02:26:05 PM CET
uid: 1000
id 5ef227ff25344363edfc27afc836b0a4584f0f83
Directory: /var/tmp/abrt/Python-2014-01-18-14:59:58-6309
count: 1
executable: /bin/fpaste
package: fpaste-0.3.7.1-9.fc20
time: Sat 18 Jan 2014 02:59:58 PM CET
uid: 1000
id fb57413cf9a5fcf7191f70c9f769b5617c3d467f
Directory: /var/tmp/abrt/Python-2014-01-08-12:01:31-20184
count: 1
executable: /bin/tcms-submit
package: qa-tools-workstation-3.2-176
time: Wed 08 Jan 2014 12:01:31 PM CET
uid: 1000
id e90f2e96241babfef23f4c26137e88f8c4e97058
Directory: /var/tmp/abrt/ccpp-2013-12-12-10:02:48-27972
count: 1
executable: /usr/bin/surf
package: surf-0.6-2.fc20
time: Thu 12 Dec 2013 10:02:48 AM CET
uid: 1000
id eb3efe7799dc710911894732f78e177f3edb2821
Directory: /var/tmp/abrt/Python-2013-11-25-08:30:30-1944
count: 2
executable: /bin/ranger
package: ranger-1.6.1-1.fc20
time: Mon 25 Nov 2013 08:30:30 AM CET
uid: 1000
id 57262f10856126ea2ce04c7c3a66d5c9000d089c
Directory: /var/tmp/abrt/ccpp-2013-12-06-12:45:22-22223
count: 1
executable: /usr/bin/surf
package: surf-0.6-2.fc20
time: Fri 06 Dec 2013 12:45:22 PM CET
uid: 1000
id beb2db069f50d286453639805e5ce96bf575a87f
Directory: /var/tmp/abrt/Python-2013-11-25-10:32:16-6699
count: 5
executable: /bin/tcms-plan
package: qa-tools-workstation-3.2-160
time: Mon 25 Nov 2013 10:32:16 AM CET
uid: 1000
I can see tons of errors. For example /usr/bin/surf - but what I can see is just some very long ID, directory, and so.. Nothing relevant for me to know which crash was it.
I would really appreciate arguments at least.
I know that traceback is very long and not generated right after crash but what about adding it to 'abrt-cli info'?
I really don't understand of usage of 'info' command because its the same as 'list' (just for one crash).
Adding these seems quite reasonable: cmdline: will_cpp_segfault -A some_param --verbose reason : will_cpp_segfault killed by SIGSEGV I propose to replace 'executable' with 'cmdline' and add 'reason' item with the following format: 'crash_function' + ':' + 'reason'. I also like the idea of having 'backtrace' in 'info' output, but it requires huge changes, so we won't have it implemented in RHEL7.1 time frame. Branislav, could you please file an upstream ticket (https://github.com/abrt/abrt/). (In reply to Jakub Filak from comment #5) > Branislav, could you please file an upstream ticket > (https://github.com/abrt/abrt/). Filled as issue 841: https://github.com/abrt/abrt/issues/841 You won't need to feed 'abrt-cli report' by output of 'abrt-cli list' because we will develop the batch-reporting feature (bug #1066482). Regarding 'info' vs. 'list': We should make info's '-d' option default and add a new option '-s' (silent). 'abrt-cli info -d' contains all the information you need (including backtrace). Created attachment 939928 [details]
Proposed patch 1/2
Created attachment 939929 [details]
Proposed patch 2/2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0556.html |