Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
After wading through some lists, still no idea. Any takers?
Cassio B. Caporal wrote:
> Actually I have wfc-timeout and degr-wfc-timeout = 0. But in some
> situations, for example, when 'server1' reboots and 'server2' takeover
> all resources (Im using heartbeat for this purpose) its NEVER connect
> to server2 because I have wfc and degr-wfc-timeout 0.
>
> Then, my question is... Why it doesnt find 'server2'? I have dedicated
> gigabit Ethernet and network conectivity is ok.
>
> Thanks,
>
> On 8/31/06, Leroy van Logchem <leroy.vanlogchem at wldelft.nl> wrote:
>>
>> > 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
>>