Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I recently installed/configured DRBD 8.0 on a newly installed Gentoo pair. Functionally, everything appears to be working great. However, my console and log files are filling with the message shown below on the Primary node: Apr 22 09:24:41 arrogance drbd1: ASSERT( mdev->net_conf->wire_protocol == DRBD_PROT_A ) in /var/tmp/portage/sys-cluster/drbd- 8.0.0/work/drbd-8.0.0/drbd/drbd_receiver.c:3156 Apr 22 09:24:41 arrogance drbd1: ASSERT( mdev->net_conf->wire_protocol == DRBD_PROT_A ) in /var/tmp/portage/sys-cluster/drbd- 8.0.0/work/drbd-8.0.0/drbd/drbd_receiver.c:3156 Apr 22 09:24:41 arrogance drbd1: ASSERT( mdev->net_conf->wire_protocol == DRBD_PROT_A ) in /var/tmp/portage/sys-cluster/drbd- 8.0.0/work/drbd-8.0.0/drbd/drbd_receiver.c:3156 This message is is written several times a minute under nominal/non-existent activity. So far is has not caused problems for me but my activity has been lightweight and my logs are being flooded. Does anyone know if this message is indicative of something to be concerned about. If not, is there someway to just surpress it? My configuration: global { usage-count yes; } common { syncer { rate 10M; } } resource ha-as { protocol B; handlers { pri-on-incon-degr "echo O > /proc/sysrq-trigger ; halt -f"; pri-lost-after-sb "echo O > /proc/sysrq-trigger ; halt -f"; local-io-error "echo O > /proc/sysrq-trigger ; halt -f"; outdate-peer "/usr/lib/drbd/outdate-peer.sh"; } startup { degr-wfc-timeout 120; # 2 minutes. } disk { on-io-error detach; } net { after-sb-0pri disconnect; after-sb-1pri disconnect; after-sb-2pri disconnect; rr-conflict disconnect; } syncer { rate 100M; al-extents 257; } on arrogance { device /dev/drbd1; disk /dev/sda6; address 192.168.208.5:7789; meta-disk internal; } on gluttony { device /dev/drbd1; disk /dev/sda6; address 192.168.208.6:7789; meta-disk internal; } }