[DRBD-user] What causes DRBD to stop listening on TCP ports ?

Ashish Shukla wahjava.ml at gmail.com
Tue Jan 8 13:40:59 CET 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On 1/8/08, Lars Ellenberg <lars.ellenberg at linbit.com> wrote:


> > I've pasted the output of "cat /var/log/messages |fgrep kernel" on
> > server "B" at "http://pastebin.ca/raw/846436". The DRBD is using
> > interface "eth1".
> >
> > Can anyone figure out from the above stuff, what could've caused DRBD
> > to stop listening on its TCP ports, hmm...? Is it due to change in
> > status of "eth1" interface, hmm...?
> first handshake in that log:
> Jan  8 10:01:18 srv1 kernel: drbd0: Handshake successful: DRBD Network
> Protocol version 86
> Jan  8 10:01:18 srv1 kernel: drbd0: Split-Brain detected, dropping
> connection!
> there. "dropping connection".
> what ever you did to get into this split brain,
> according to that log that is the cause for drbd to stop listening.

Okay, so this mean to recover from split-brain, I need to restart DRBD
on both nodes, and discard the data on one of the nodes, hmm...?

Ashish Shukla

More information about the drbd-user mailing list