search

LINBIT / drbd

LINBIT DRBD kernel module
https://docs.linbit.com/docs/users-guide-9.0/
GNU General Public License v2.0
583 stars 100 forks source link

troubleshoot connection problem #11

Closed alucionet closed 3 years ago

alucionet commented 3 years ago

Hello, I am new to drbd and find it very hard to get proper help from google on drbd. I just setup 2 nodes using the following version on CentOS 7: DRBDADM_BUILDTAG=GIT-hash:\ a7820b3c14497a34f955ba5ce56cf1bc9d2d353e\ build\ by\ root@xena.xxx\,\ 2021-05-02\ 22:04:05 DRBDADM_API_VERSION=2 DRBD_KERNEL_VERSION_CODE=0x09001c DRBD_KERNEL_VERSION=9.0.28 DRBDADM_VERSION_CODE=0x091000 DRBDADM_VERSION=9.16.0

The disk on the master is setup and running fine...but it keeps trying to connect to the secondary node. The secondary node is also trying to connect. No errors seen in /var/log/messages

May 17 16:27:13 xena kernel: drbd himalaya himalaya.xx: conn( Connecting -> Disconnecting ) May 17 16:27:13 xena kernel: drbd himalaya himalaya.xx: Restarting sender thread May 17 16:27:13 xena kernel: drbd himalaya himalaya.xx: Connection closed May 17 16:27:13 xena kernel: drbd himalaya himalaya.xx: helper command: /sbin/drbdadm disconnected May 17 16:27:13 xena kernel: drbd himalaya himalaya.xx: helper command: /sbin/drbdadm disconnected exit code 0 May 17 16:27:13 xena kernel: drbd himalaya himalaya.xx: conn( Disconnecting -> StandAlone ) May 17 16:27:13 xena kernel: drbd himalaya himalaya.xx: Terminating receiver thread

The following is my resource file:

resource himalaya { connection { host himalaya.xxx port 6999; host xena.xxx port 6998; net { cram-hmac-alg sha256; shared-secret "VmKuU2PPZzoHF3kuG/Km"; protocol C; } } on xena.xxx { node-id 1; address ipv4 10.8.9.15:6998; device /dev/drbd1; disk /dev/himalaya/himalayadata; meta-disk internal; } on himalaya.xxx { node-id 0; address ipv4 10.17.0.254:6999; device /dev/drbd0; disk /dev/mailpool/maildata; meta-disk internal; } }

How can I turn on debugging ? Where can I see some useful logs on what is causing the problem?

On the secondary node: [root@xena drbd.d]# netstat -an | grep 6998 tcp 0 0 10.8.9.15:6998 0.0.0.0:* LISTEN
tcp 0 0 10.8.9.15:6998 103.xxx:52423 SYN_RECV
tcp 0 0 10.8.9.15:6998 103.xxx:60099 SYN_RECV
tcp 0 0 10.8.9.15:6998 103.xxx:53059 SYN_RECV

On the master node: tcp 0 0 103.xxx:6999 0.0.0.0:* LISTEN
tcp 0 1 103.xxx:58212 10.8.9.15:6998 SYN_SENT

alucionet commented 3 years ago

Problem is fixed after using different IP on the master host. Looks like the endpoints IP must match on multi-ip node.