Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> Ok, my problem is when 'server1' goes down and _later_ returns to
> takeover 'server2' services... Connection status on 'server2' stay
> with 'StandAlone' and 'st' Secondary/Unknown.
>
> 'server1' starts with "wfc-timeout prompt" and doesnt find (drbd point
> of view) 'server2' anymore.. Connection status is 'WFConnection' and
> 'st' is Primary/Unknown.
The server2 going into StandAlone seems to be the problem. You might
want to try:
startup {
degr-wfc-timeout 0;
}
This makes sure it keeps waiting for the peer to return.
Another reason not to allow StandAlone is the full sync.
--
Leroy