Red Hat Bugzilla – Bug 1434691
"Failed to accept connection errno 11." on lvmetad termination
Last modified: 2018-04-10 11:19:55 EDT
+++ 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
Hi Team, Can this error message be safely ignored? Best regards, Shiwang
Yes, it's just saying a thread got interrupted while it was waiting for a connection. Since it's an expected condition during shutdown, I've applied a patch to suppress it in future releases. https://www.redhat.com/archives/lvm-devel/2017-July/msg00004.html https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=fdd00ecdd1fd51605be1b616d712a2220ced8875
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