All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: protserovsd@gmail.com
Subject: Re: [linux-lvm] "lvmetad: Failed to accept connection" on poweroff
Date: Thu, 15 Sep 2016 09:23:04 +0200	[thread overview]
Message-ID: <53b93052-192a-3e7a-f67c-aa94cb6aae84@redhat.com> (raw)
In-Reply-To: <4c5fc2ba-339c-48c6-1039-1e238fda2321@gmail.com>

On 09/15/2016 06:00 AM, Сергей Процеров (Sergey Protserov) wrote:
> Hello! I am using Debian Unstable, systemd, full-disk encryption and lvm
> (version 2.02.164). On poweroff that's what I see in journal:
> сен 12 22:36:51 debian systemd[1]: Stopping LVM2 metadata daemon...
> сен 12 22:36:51 debian lvmetad[332]: Failed to accept connection.
> сен 12 22:36:51 debian systemd[1]: Stopped LVM2 metadata daemon.
> Could you please tell me, if this error signalizes something bad, and if
> this error should be fixed? If it has to be fixed, then how can I do it?
> Thanks in advance.
> 

We've had a report recently about this but it was closed because it was
not reproducible anymore by reporter:

  https://bugzilla.redhat.com/show_bug.cgi?id=1367686

Does this error happen always or only sometimes? Would it be possible
for you to update to lvm2 v2.02.165 and then hit this error again? In
that version, we added a bit more info for the error state that is
printed in this case so this would give us more insight about why the
failure happens exactly.

Thanks.

-- 
Peter

      reply	other threads:[~2016-09-15  7:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15  4:00 [linux-lvm] "lvmetad: Failed to accept connection" on poweroff Сергей Процеров (Sergey Protserov)
2016-09-15  7:23 ` Peter Rajnoha [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53b93052-192a-3e7a-f67c-aa94cb6aae84@redhat.com \
    --to=prajnoha@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=protserovsd@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.