Bug 1408579
| Summary: | "Failed to accept connection errno 11." on lvmetad termination | |||
|---|---|---|---|---|
| Product: | [Community] LVM and device-mapper | Reporter: | Andrey Vihrov <andrey.vihrov> | |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> | |
| lvm2 sub component: | lvmetad | QA Contact: | cluster-qe <cluster-qe> | |
| Status: | CLOSED NEXTRELEASE | Docs Contact: | ||
| Severity: | unspecified | |||
| Priority: | unspecified | CC: | agk, heinzm, jbrassow, mail, msnitzer, prajnoha, sjenning, zkabelac | |
| Version: | 2.02.168 | Flags: | agk:
lvm-technical-solution+
rule-engine: lvm-test-coverage? |
|
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | 2.02.173 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1434691 (view as bug list) | Environment: | ||
| Last Closed: | 2017-07-06 14:01:49 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1434691 | |||
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 |
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