Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1319828 - abrt-cli failure on missing pkg_epoch file
abrt-cli failure on missing pkg_epoch file
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: abrt (Show other bugs)
7.2
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: abrt
Martin Kyral
: Reopened
Depends On:
Blocks: 1420851 1473612 1474754
  Show dependency treegraph
 
Reported: 2016-03-21 11:46 EDT by mulhern
Modified: 2018-04-10 13:43 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 13:41:30 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0949 None None None 2018-04-10 13:43 EDT

  None (edit)
Description mulhern 2016-03-21 11:46:35 EDT
Description of problem:

Try to run abrt_cli report on particular abrt directory.

Version-Release number of selected component (if applicable):

2.1.11

How reproducible:

Always.

Steps to Reproduce:
1.[root@megadeth pydevDAG]# sudo abrt-cli report /var/spool/abrt/ccpp-2016-03-18-14:46:21-44595

Actual results:

Red Hat Customer Support Username: amulhern
Red Hat Customer Support Password: 

No changes were detected in the report
Sending ABRT crash statistics data
Unable to open './pkg_epoch': No such file or directory.
('report_RHTSupport' exited with 1)

Expected results:

Success, regardless of pkg_epoch missing, or else, find pkg_epoch, or else give me more information so I can figure out how to fix.

Additional info:

The directory /var/spool/abrt/ccpp-2016-03-18-14:46:21-44595 looks like it is in pretty good shape:

[root@megadeth pydevDAG]# ls /var/spool/abrt/ccpp-2016-03-18-14:46:21-44595
abrt_version    count        kernel           pid               uid
analyzer        dso_list     last_occurrence  proc_pid_status   username
architecture    environ      limits           pwd               uuid
cgroup          event_log    machineid        reason            var_log_messages
cmdline         executable   maps             runlevel
comment         exploitable  open_fds         sosreport.tar.xz
core_backtrace  global_pid   os_info          time
coredump        hostname     os_release       type
Comment 5 Julius Milan 2017-04-19 07:32:01 EDT
Does the executable, which causes this problem, belong to some package or is it unpackaged?

If the first, is it possible to trigger the crash?
(To trigger problem directory creation to see why it doesn't contain pkg_* files)

If it is impossible or too difficult to reproduce the crash, please upload at least problem directory contents (/var/spool/abrt/ccpp-2016-03-18-14:46:21-44595)

journal error logs may also help.
Comment 6 mulhern 2017-04-19 08:49:12 EDT
Sorry, the machine on which I experienced this bug has moved on to other things. You may need to close this as insufficient data.
Comment 7 Matej Marušák 2017-06-20 06:28:26 EDT
So during testing ABRT I was (un)lucky to hit this issue with simple reproducer:
`python -c 'import os; os.kill(os.getpid(), 11)'`
Reopening this, since I noticed that there are other bugs that suffer with this.
Comment 10 Yannick Charton 2017-10-17 10:25:11 EDT
I'm also facing this issue, at least with an unpackaged software.

[root@cmandmzsrv1 ~]# abrt-cli list
id 624c3a7f91955d4c60c7dbafbaa353763741890d
reason:         cmgw killed by SIGSEGV
time:           Tue 17 Oct 2017 09:12:06 AM CEST
cmdline:        /u01/app/oracle/product/12.2.0/client_1/bin/cmgw cmgw1 1 16 cman_cmandmzsrv1 SNLSM:59248000
uid:            800 (oracle)
count:          1
Directory:      /var/spool/abrt/ccpp-2017-10-17-09:12:06-24617
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-10-17-09:12:06-24617' for creating a case in Red Hat Customer Portal

The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
[root@cmandmzsrv1 ~]#
[root@cmandmzsrv1 ~]# abrt-cli report /var/spool/abrt/ccpp-2017-10-17-09\:12\:06-24617
1 Submit anonymous crash report
  Submit anonymous crash report - I do not want to be contacted by Red Hat Support

2 Ask Red Hat Support for help
  Create new Red Hat Support case - I would like to be contacted by Red Hat Support

Select a workflow to run:  2
Red Hat Customer Support Username: Yannick.Charton@cdt.europa.eu
Red Hat Customer Support Password:

No changes were detected in the report
Sending ABRT crash statistics data
Unable to open './pkg_epoch': No such file or directory.
('report_RHTSupport' exited with 1)
[root@cmandmzsrv1 ~]#
Comment 19 errata-xmlrpc 2018-04-10 13:41:30 EDT
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://access.redhat.com/errata/RHBA-2018:0949

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