1. Got some stuck requests 2. netstat -atp tcp 25 0 dionysius-pc:52340 server-52-85-47-1:https CLOSE_WAIT 1364/brave --type=u tcp 25 0 dionysius-pc:40296 server-13-33-240-:https CLOSE_WAIT 1364/brave --type=u 3. A few second later netstat doesn't show any non-empty queues 4. But requests continue to hang (it will be endless)
вторник, 10 ноября 2020 г. в 23:12:21 UTC+7, ren...@ix.netcom.com: > You can easily have the same problem on localhost if the producer is > faster than the consumer. > > You can use netstat in the localhost as well. > > On Nov 10, 2020, at 9:36 AM, Denis Telyukh <telyuk...@gmail.com> wrote: > > > > Thanks for your advice. But I have this problem on localhost also, I doubt > that problem in network capacity :-( > > вт, 10 нояб. 2020 г. в 19:09, Robert Engels <ren...@ix.netcom.com>: > >> You’ve most likely exhausted the network capacity. You need to use tools >> like netperf and wireshark. Start with netstat and review the outgoing >> queue sizes. >> >> On Nov 10, 2020, at 4:46 AM, Denis Telyukh <telyuk...@gmail.com> wrote: >> >> More complex problem description with images: >> https://caddy.community/t/sometimes-http-2-request-hangs-up-need-help-with-debugging/10439/2 >> >> >> вторник, 10 ноября 2020 г. в 10:25:58 UTC+7, Denis Telyukh: >> >>> Thanks! Maybe it will help. >>> >>> вт, 10 нояб. 2020 г. в 01:21, seank...@gmail.com <seank...@gmail.com>: >>> >>>> maybe setting GODEBUG=http2debug=2 to spit out some logs? >>>> >>>> On Monday, November 9, 2020 at 5:49:57 PM UTC+1 telyuk...@gmail.com >>>> wrote: >>>> >>>>> Hello! >>>>> >>>>> I use third-party software with my own code to build reverse-proxy, >>>>> which supports http/2. Sometimes requests hang up with infinite waiting. >>>>> With Delve I found, that it happens in >>>>> https://golang.org/src/net/http/h2_bundle.go in writeHeaders or in >>>>> writeDataFromHandler. But I have no any idea why it happens. Which tools >>>>> should I use to find the reason of such behaviour? >>>>> >>>>> Denis >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "golang-nuts" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/golang-nuts/CJwsb1H9mGg/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> golang-nuts...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/golang-nuts/94e4b5cd-6005-4a52-916f-9e1a88137399n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/golang-nuts/94e4b5cd-6005-4a52-916f-9e1a88137399n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/a9ac428d-1389-4278-be9a-273ae95751b0n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/golang-nuts/a9ac428d-1389-4278-be9a-273ae95751b0n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/bdffc045-afd0-4096-8fa3-9741cfe92e8an%40googlegroups.com.
