Date: Tue, 5 May 2020 08:42:14 +0200 From: Michael Tuexen <tuexen@freebsd.org> To: "Reynolds, Paul" <paul.reynolds@redcom.com> Cc: "freebsd-transport@freebsd.org" <freebsd-transport@freebsd.org> Subject: Re: SCTP deadlock Message-ID: <7B548240-AF6D-4F40-B506-9B83052EC7CE@freebsd.org> In-Reply-To: <112525e87fce467e97f1d455ef9bf685@redcom.com> References: <112525e87fce467e97f1d455ef9bf685@redcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 5. May 2020, at 02:22, Reynolds, Paul <paul.reynolds@redcom.com> = wrote: >=20 > Hi, >=20 >=20 > My apologies if this is not the right mailing list for this question. = I am hoping to get some suggestions on how to debug an sctp issue I have = been having. >=20 >=20 > I have a set of programs that use sctp for communication. For now = these processes are all running on the same machine. They are using = SEQPACKET mode to send messages back and forth. Each process has = multiple threads, but only one socket. The threads are mutex protected = such that the socket cannot be accessed by more than one thread at a = time. Very occasionally one of the sockets will become permanently = blocked on an sctp send or receive call and I am trying to figure out = why. In the cases where it has become blocked on a send call, the = corresponding receive process is not blocked and can send/receive data = to other destinations. These processes can run fine for months and then = suddenly run into this problem. I have been able to reproduce this once = or twice by subjecting the system to unrealistically high levels of = traffic, but it still takes several days or more to reproduce the = problem. I now have a system that is stuck in this mode and am trying to = gather as much information > as poss > ible. >=20 >=20 > How should I go about debugging this? The output of sockstat and = netstat have not been very helpful up to this point. Which version of FreeBSD are you using? Best regards Michael >=20 >=20 > Thanks for any help you might be able to provide, >=20 > Paul > _______________________________________________ > freebsd-transport@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-transport > To unsubscribe, send any mail to = "freebsd-transport-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B548240-AF6D-4F40-B506-9B83052EC7CE>