Boris,

what does your network connection in between DRBD nodes look like? Which
NICs?

B.

On 02/21/11 12:45, Boris Virc wrote:
> Hello,
> 
> I have installed SLES with kernel version 2.6.32.19-0.3 and DRBD 8.3.8.1 
> (using two nodes - primary-slave).
> 
> I noticed that there is a lot of BrokenPipe errors in log files:
> 
> Feb 11 12:59:40 sles1 crm-fence-peer.sh[64879]: invoked for r0
> Feb 11 12:59:41 sles1 crm-fence-peer.sh[64879]: INFO peer is reachable, my 
> disk is UpToDate: placed constraint 'drbd-fence-by-handler-ms_drbd'
> Feb 11 12:59:41 sles1 kernel: [6022113.566198] block drbd0: helper command: 
> /sbin/drbdadm fence-peer minor-0 exit code 4 (0x400)
> Feb 11 12:59:41 sles1 kernel: [6022113.566206] block drbd0: fence-peer helper 
> returned 4 (peer was fenced)
> Feb 11 12:59:41 sles1 kernel: [6022113.566228] block drbd0: pdsk( DUnknown -> 
> Outdated )
> Feb 11 12:59:41 sles1 kernel: [6022113.566400] block drbd0: conn( BrokenPipe 
> -> Unconnected )
> Feb 11 12:59:41 sles1 kernel: [6022113.566418] block drbd0: receiver 
> terminated
> Feb 11 12:59:41 sles1 kernel: [6022113.566422] block drbd0: Restarting 
> receiver thread
> Feb 11 12:59:41 sles1 kernel: [6022113.566426] block drbd0: receiver 
> (re)started
> Feb 11 12:59:41 sles1 kernel: [6022113.566441] block drbd0: conn( Unconnected 
> -> WFConnection )
> Feb 11 12:59:41 sles1 pengine: [30521]: notice: unpack_config: On loss of CCM 
> Quorum: Ignore
> 
> The system works, but within 2 monts, there was already two unpredictable 
> error (we had to restart secondary server so that primary started to work 
> again).
> 
> Is there anything that we can do to avoid those errors ?
> 
> Regards,
> Boris
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to