Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, Feb 04, 2010 at 11:59:33AM +0100, listacc at gmx.de wrote: > Hi Lars, > > > Every few minutes?? > > Thats a bit unusual. > > > > yes, that´s it... > > > Mind do show a log excerpt? > > It is very likely not the only message, is it? > > > > No, they come like this: > > Jan 26 13:34:09 kernel: drbd0: meta connection shut down by peer. > Jan 26 13:34:09 kernel: drbd0: short read expecting header on sock: r=-104 > Jan 26 13:34:10 kernel: drbd0: helper command: /sbin/drbdadm outdate-peer minor-0 exit code 4 (0x400) > Jan 26 13:35:29 kernel: drbd0: meta connection shut down by peer. > Jan 26 13:35:29 kernel: drbd0: short read expecting header on sock: r=-104 > Jan 26 13:35:31 kernel: drbd0: helper command: /sbin/drbdadm outdate-peer minor-0 exit code 4 (0x400) > Jan 26 13:35:49 kernel: drbd0: meta connection shut down by peer. > Jan 26 13:35:49 kernel: drbd0: short read expecting header on sock: r=-104 > uhm. you managed to get yourself into a disconnect/reconnect loop. please: drbdadm disconnect all take a deep breath, let it settle down abit, try again drbdadm connect all there have been a few cases, which we hopefully all fixed upstream already, where, given unlucky timing, a failed first connection attempt could result into drbd not being able to establish the connection at all, instead remaining in limbo, disconnecting/reconnecting in a loop. watch /proc/drbd, as long as it is not Connected UpToDate/UpToDate, you are not in "normal operation". > > http://www.lmgtfy.com/?q=outdate%20peer%20exit%20code%204&l=1 > > Oha, yes... SCNR. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed