Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1563615 - tcmu-runner: the daemon will crash when shutdown
Summary: tcmu-runner: the daemon will crash when shutdown
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: tcmu-runner
Version: cns-3.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: CNS 3.10
Assignee: Xiubo Li
QA Contact: Sweta Anandpara
Depends On:
Blocks: 1568861
TreeView+ depends on / blocked
Reported: 2018-04-04 10:13 UTC by Xiubo Li
Modified: 2018-09-12 09:26 UTC (History)
9 users (show)

Fixed In Version: tcmu-runner-1.2.0-19.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-09-12 09:25:34 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2691 0 None None None 2018-09-12 09:26:41 UTC

Description Xiubo Li 2018-04-04 10:13:03 UTC
Description of problem:

When shutting down the tcmu-runner daemon the tcmu-runner will crash:

systemd: Stopping LIO Userspace-passthrough daemon...                                                                                                   
kernel: tcmu-runner[59089]: segfault at 7feed3115050 ip 00007feed5facc30 sp 00007ffe8d7b2488 error 4 in libpthread-2.17.so[7feed5fa3000+17000]systemd: tcmu-runner.service: main process exited, code=killed, status=11/SEGV
systemd: Unit tcmu-runner.service entered failed state. 
systemd: tcmu-runner.service failed.

Comment 8 errata-xmlrpc 2018-09-12 09:25:34 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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