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.
+++ This bug was initially created as a clone of Bug #1408579 +++
Description of problem:
When lvmetad is stopped with SIGINT/SIGTERM, the following error is printed to the system journal:
lvmetad[356]: Failed to accept connection errno 11.
This also appears when lvmetad is stopped by systemd through "systemctl stop lvm2-lvmetad.service".
This is the source code location that produces the error: https://git.fedorahosted.org/cgit/lvm2.git/tree/libdaemon/server/daemon-server.c#n494
Version-Release number of selected component (if applicable):
lvm2 2.02.168
How reproducible: Always
Steps to Reproduce:
1. Run "lvmetad -f" in a terminal
2. Press Ctrl+C or send SIGTERM to the process
Actual results: The above error is printed to the journal
Expected results: lvmetad terminates gracefully
Marking verified with latest rpms. The "error" message after sending SIGINT/SIGTERM to lvmetad is now suppressed.
BEFORE PATCH:
# lvmetad
# kill -2 $(pidof /usr/sbin/lvmetad)
# tail -n 1 /var/log/messages
Oct 16 14:52:58 virt-363 lvmetad[23253]: Failed to accept connection errno 11
===================================================
AFTER PATCH:
# lvmetad
# kill -2 $(pidof /usr/sbin/lvmetad)
# tail -n 1 /var/log/messages
Oct 16 14:52:53 virt-371 systemd: Starting LVM2 metadata daemon...
===================================================
3.10.0-727.el7.x86_64
lvm2-2.02.175-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017
lvm2-libs-2.02.175-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017
lvm2-cluster-2.02.175-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017
device-mapper-1.02.144-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017
device-mapper-libs-1.02.144-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017
device-mapper-event-1.02.144-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017
device-mapper-event-libs-1.02.144-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017
device-mapper-persistent-data-0.7.3-2.el7 BUILT: Tue Oct 10 11:00:07 CEST 2017
cmirror-2.02.175-2.el7 BUILT: Fri Oct 13 13:31:22 CEST 2017
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/RHEA-2018:0853