1408579 – "Failed to accept connection errno 11." on lvmetad termination

Bug 1408579 - "Failed to accept connection errno 11." on lvmetad termination

Summary: "Failed to accept connection errno 11." on lvmetad termination

Keywords:
Status:	CLOSED NEXTRELEASE
Alias:	None
Product:	LVM and device-mapper
Classification:	Community
Component:	lvm2
Sub Component:
Version:	2.02.168
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Target Release:	---
Assignee:	LVM and device-mapper development team
QA Contact:	cluster-qe@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:	1434691
TreeView+	depends on / blocked

Reported:	2016-12-25 10:29 UTC by Andrey Vihrov
Modified:	2024-12-20 18:42 UTC (History)
CC List:	8 users (show)
Fixed In Version:	2.02.173
Clone Of:
Clones:	1434691 (view as bug list)
Environment:
Last Closed:	2017-07-06 14:01:49 UTC
Embargoed:
Flags:	agk: lvm-technical-solution+ rule-engine: lvm-test-coverage?

Attachments	(Terms of Use)

Description Andrey Vihrov 2016-12-25 10:29:58 UTC

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

Comment 1 Alasdair Kergon 2017-07-06 14:01:49 UTC

Since it's an expected condition during shutdown, I've applied a patch to suppress it.

https://www.redhat.com/archives/lvm-devel/2017-July/msg00004.html

https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=fdd00ecdd1fd51605be1b616d712a2220ced8875

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