Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Jun 10, 2013 at 11:22:09AM +0200, andreas graeper wrote: > hi, > i build drbd8.4.3. from source on centos64. > > # /var/log/messages on n1 > conn( Unconnected -> WFConnection ) > Handshake successful: Agreed network protocol version 101 > expected AuthChallenge packet, received: ReportProtocol (0x000b) > Authentication of peer failed, trying again. > conn( WFConnection -> NetworkFailure ) > Connection closed > conn( NetworkFailure -> Unconnected ) > One side configured for authentication, the other not. The one that is configured for authentication expects an AuthChallenge packet, but the peer skipped authentication and proceeded directly to exchange ReportProtocol (net config parameters). The one configured for authentication rejects this, obviously. Since this situation won't change without reconfiguration, there is no point in retrying, thus -> StandAlone. > # /var/log/message on n2 > Restarting receiver thread > receiver (re)started > conn( Unconnected -> WFConnection ) > Handshake successful: Agreed network protocol version 101 > conn( WFConnection -> WFReportParams ) > Starting asender thread (from drbd_r_r0 [18568]) > Unexpected data packet AuthChallenge (0x0010) > conn( WFReportParams -> ProtocolError ) > asender terminated > Terminating drbd_a_r0 > Connection closed > conn( ProtocolError -> Unconnected ) > receiver terminated > > Restarting receiver thread > receiver (re)started > conn( Unconnected -> WFConnection ) > conn( WFConnection -> Disconnecting ) > Discarding network configuration. > Connection closed > conn( Disconnecting -> StandAlone ) > receiver terminated -- : 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