All of lore.kernel.org
 help / color / mirror / Atom feed
From: Madison Kelly <linux@alteeve.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] pvscan connect() failed on local socket: Connection refused
Date: Fri, 05 Feb 2010 20:42:05 -0500	[thread overview]
Message-ID: <4B6CC8ED.2070107@alteeve.com> (raw)

Hi all,

   I've got a two-node Xen cluster I am trying to setup with a DRBD 
partition under an LVM pv. My layout is:

* Both node's hard drive is a PV used by one VG.
* Each node has the host OS  (dom0) install on an LV using a small 
portion of the available space.
* The majority of the space is assigned to an LV on either node that 
DRBD uses.
* The DRBD partition is itself setup as a new PV.

   The problem is; Once I setup '/dev/drbd0' as a VG, I had to enable 
cluster-aware mode by changing lvm.conf to:

filter = [ "a|drbd.*|", "r|.*|" ]
locking_type = 3

   And then running:

lvmconf --enable-cluster

   After that, when I run 'pvscan', I get this output on both nodes:

[root@an_san02 ~]# pvscan
   connect() failed on local socket: Connection refused
   WARNING: Falling back to local file-based locking.
   Volume Groups with the clustered attribute will be inaccessible.
   PV /dev/drbd0                      lvm2 [399.99 GB]
   Total: 1 [399.99 GB] / in use: 0 [0   ] / in no VG: 1 [399.99 GB]

   How can I tell what or where the connection is failing? It *should* 
be going over 'eth1' on both nodes which is outside of Xen's control. 
I've also checked iptables and I don't see any relevant rules (I've 
flushed the tables and there is only now Xen-related bridging rules). 
Also, I can ping the other node over the dedicated DRBD interfaces.

   Thanks for any insight!

Madi

             reply	other threads:[~2010-02-06  1:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-06  1:42 Madison Kelly [this message]
2010-02-07  7:57 ` [linux-lvm] pvscan connect() failed on local socket: Connection refused Luca Berra

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=4B6CC8ED.2070107@alteeve.com \
    --to=linux@alteeve.com \
    --cc=linux-lvm@redhat.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.