Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
abrt-vmcore fails to harvest cores
Version-Release number of selected component (if applicable):
abrt-addon-vmcore-2.0.8-40.el6.x86_64
How reproducible:
always
Steps to Reproduce:
#yum install abrt-addon-kerneloops abrt-tui abrt abrt-addon-python abrt-python abrt-cli abrt-libs abrt-addon-ccpp abrt-addon-vmcore
#chkconfig abrtd on
#chkconfig abrt-ccpp on
#chkconfig abrt-oops on
#chkconfig abrt-vmcore on
At that point, if manually trigger a kernel panic, the crash kernel should take over, write out the kernel panic to /var/crash (assuming you haven't changed the defaults), and the system reboot.
What _should_ happen at that point is system boots into run level 3, the abrtd daemon is started, and then the startup script for abrt-vmcore is executed, moving the kernel panic from /var/crash into the abrt location (/var/spool/abrt ).
However, what actually happens is the system boots into run level 3, the abrt-vmcore startup script runs, but at that time abrtd isn't yet started, and thus abrt-vmcore times out and fails, then abrtd starts. The kernel panic remains in /var/crash, and isn't added to abrt.
Actual results:
It is not taking the vmcores
Expected results:
It should harvest the vmcores
Additional info:
A fresh install contains the line:
# Required-Start: $abrtd
As a result, the following startup scripts are created in run level 3 by chkconfig:
[root@hostname abrt]# ls -al /etc/rc3.d/*abrt*
lrwxrwxrwx. 1 root root 19 May 26 11:58 /etc/rc3.d/S82abrt-ccpp -> ../init.d/abrt-ccpp
lrwxrwxrwx. 1 root root 19 May 26 11:58 /etc/rc3.d/S82abrt-oops -> ../init.d/abrt-oops
lrwxrwxrwx. 1 root root 21 May 26 11:58 /etc/rc3.d/S82abrt-vmcore -> ../init.d/abrt-vmcore
lrwxrwxrwx. 1 root root 15 May 26 11:58 /etc/rc3.d/S82abrtd -> ../init.d/abrtd
If the line ( # Required-Start: $abrtd ) from /etc/init.d/abrt-vmcore is modified to:
# Required-Start: abrtd
and the following commands run, everything works as expected:
/sbin/chkconfig --del abrt-vmcore
/sbin/chkconfig --add abrt-vmcore
At that point, a reboot will perform the following as expected:
system boots up into run level 3, abrtd starts up, abrt-vmcore starts and moves the kernel crash dump under abrt control (and performs any configured abrt actions as expected).
Thank you for the excellent analysis. This is indeed a bug in abrt init scripts. All "Required-Start:" should have "abrtd" and /etc/init.d/abrtd should have "Provide: abrtd".
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-2017-0768.html