On Tue, Mar 01, 2011 at 10:12:36AM +0100, [email protected] wrote: > Lars: > That broken pipe messages from my experience always show up on the master, > when the slave produces the digest mismatch messages. from my point of > view this is a bit misleading.
Guess what, "broken pipe" shows up on almost all attempts to send something on a socket where the other side already closed the connection. And there is more than one reason for the remote end to do that. > On Mon, Feb 28, 2011 at 01:39:58PM +0100, [email protected] wrote: > > Lars Ellenberg gave some interesting information about this messages - > at > > least if you have verification of your Network traffic enabled: > > Well, that's not much to do with "BrokenPipe", > but with "Digest mismatch", "Digest integrity check FAILED" etc. > And there has been no mention of that in the (much too short) log > excerpt shown. > > So this may be something completely different. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
