Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi, On 05/17/2011 03:04 PM, Edwige Odedele wrote: > Thanks for answer, don't mention it, but please send your answers to the list! > > > This is the kernel’s log of the node that shows “ Unconnected “ > > > > May 17 14:57:34 sd-XXXXX kernel: [1124558.113675] block drbd0: ASSERT > FAILED cstate = WFConnection, expected < WFConnection > > May 17 14:57:34 sd-XXXXX kernel: [1124558.113876] block drbd0: > Connection closed > > May 17 14:57:34 sd-XXXXX kernel: [1124558.113884] block drbd0: conn( > WFConnection -> Unconnected ) > > May 17 14:57:35 sd-XXXXX kernel: [1124559.111062] block drbd0: conn( > Unconnected -> WFConnection ) > > May 17 14:57:35 sd-XXXXX kernel: [1124559.203047] block drbd0: Handshake > successful: Agreed network protocol version 91 > > May 17 14:57:35 sd-XXXXX kernel: [1124559.203375] block drbd0: expected > AuthChallenge packet, received: ReportProtocol (0x000b) > > *May 17 14:57:35 sd-XXXXX kernel: [1124559.203380] block drbd0: > Authentication of peer failed, trying again.* > > May 17 14:57:35 sd-XXXXX kernel: [1124559.203384] block drbd0: ASSERT > FAILED cstate = WFConnection, expected < WFConnection > > May 17 14:57:35 sd-XXXXX kernel: [1124559.203524] block drbd0: > Connection closed > > May 17 14:57:35 sd-XXXXX kernel: [1124559.203532] block drbd0: conn( > WFConnection -> Unconnected ) > > May 17 14:57:36 sd-XXXXX kernel: [1124560.198077] block drbd0: conn( > Unconnected -> WFConnection ) > > > > > > What do you think the problem could be? > > Or do I need to generate a new sshkeygen between the nodes? No, this is authantication at DRBD level. Have you messed up the config on either node? You may want to re-sync the configs. HTH, Felix