[DRBD-user] Re: meta connection shut down by peer

Seki Lau sekilau at gmail.com
Fri Sep 24 05:07:03 CEST 2004

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

Dear all,
I read the post on 12 Aug

and I am now facing the same problem.

I have machine  M0 and M1. M0 is startup. No problem at all. It
becomes Primary and the states is Primary/unknown
Then I strart M1. No problem. It becomes Secondary/Primary (I expect
this result for every secondary).

Then I power down M0. M1 becomes primary (expected result).

Then I power up M0. Problem occurs here.
M0: Secondary/unknow
M1: Primary/unknow.

I check the /var/log/messages in M0. it gives that

meta connection shut down by peer.
asender terminated
sock was shut down by peer

Then I power restart  M1, it becomes normal again:
M0 Primary/Secondary
M1 Secondary/Primary

I am using drbd 0.7.4 and I find from mail list that, it is
recommanded to start drbd before heartbeat(M0 and M1 do so).

So, what should be the source of problem and how to fix it?

Thank in prior
Seki Lau

More information about the drbd-user mailing list