Bug 1278784 - sosreport can not be killed with SIGTERM
Summary: sosreport can not be killed with SIGTERM
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: sos
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bryn M. Reeves
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-06 12:09 UTC by Marius Vollmer
Modified: 2016-07-19 18:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:25:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marius Vollmer 2015-11-06 12:09:05 UTC
Killing a sosreport process with SIGTERM does not stop it.  Instead, one gets

    caught exception in plugin method "selinux.collect()"
    writing traceback to sos_logs/selinux-plugin-errors.txt

Steps:

 # sosreport --batch

While that runs in another shell:

 # pkill sosreport

Using "pkill -SIGINT sosreport" works as expected.

Comment 1 Bryn M. Reeves 2015-11-10 15:47:02 UTC
Thanks - filed as upstream issue #689:

  https://github.com/sosreport/sos/issues/689

Comment 2 Fedora End Of Life 2016-07-19 18:25:50 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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