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.
Bug 1848871 - abrt fails to generate sosreport due to invalid plugin 'nfsserver'
Summary: abrt fails to generate sosreport due to invalid plugin 'nfsserver'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: abrt
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: ekulik
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-19 06:27 UTC by Martin Kyral
Modified: 2020-09-29 19:53 UTC (History)
4 users (show)

Fixed In Version: abrt-2.1.11-60.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-29 19:53:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3912 0 None None None 2020-09-29 19:53:24 UTC

Description Martin Kyral 2020-06-19 06:27:47 UTC 
Description of problem:
deliberately created crash of ksh was not picked up by ABRT due to failure when generating sosreport:

Jun 19 02:04:50 host-10-0-139-75 abrt-hook-ccpp: Process 27708 (ksh93) of user 0 killed by SIGSEGV - dumping core
Jun 19 02:04:52 host-10-0-139-75 abrt-server: sosreport run failed with exit code 1, log follows:
Jun 19 02:04:52 host-10-0-139-75 abrt-server: sosreport (version 3.9)
Jun 19 02:04:52 host-10-0-139-75 abrt-server: a non-existing plugin (nfsserver) was specified in the command line
Jun 19 02:04:52 host-10-0-139-75 abrt-server: a non-existing plugin (nfsserver) was specified in the command line
Jun 19 02:04:52 host-10-0-139-75 abrt-server: 'post-create' on '/var/spool/abrt/ccpp-2020-06-19-02:04:50-27708' exited with 1
Jun 19 02:04:52 host-10-0-139-75 abrt-server: Deleting problem directory '/var/spool/abrt/ccpp-2020-06-19-02:04:50-27708'

I suspect, this is caused by the recent rebase of sos to 3.9:

https://bugzilla.redhat.com/show_bug.cgi?id=1789025


Version-Release number of selected component (if applicable):
abrt-2.1.11-59.el7

How reproducible:


Steps to Reproduce:
1. kill ksh with pickable signal (ie 11)
2. tail -f /var/log/messages
3.

Actual results:
sosreport fails, crash dir deleted


Expected results:
crash picked up in ABRT


Additional info:
This is not the first time, ABRT gets broken by sosreport update. I wonder, if there's a way to set information flow up in order to prevent such a breakage. It would be nice of sos developers to ping their ABRT counterparts when planning to remove / split plugins so ABRT can be updated in sync. Also please note, that this kind of breakage flies under the radar of regular errata testing as it is performed on released RHEL with just ABRT updated.
Comment 12 errata-xmlrpc 2020-09-29 19:53:13 UTC 
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 (abrt bug fix and enhancement update), 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-2020:3912
Note You need to log in before you can comment on or make changes to this bug.