unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47431@debbugs.gnu.org
Subject: bug#47431: Process Whois connection broken by remote peer.
Date: Sun, 28 Mar 2021 15:12:23 +0800	[thread overview]
Message-ID: <CAGP6POKK54PbZ_kxnJjHsVj81zLyC+StPNutYBUDpQHHSQ8bzw@mail.gmail.com> (raw)
In-Reply-To: <83h7kvok9r.fsf@gnu.org>

On Sun, Mar 28, 2021 at 2:38 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> > Date: Sun, 28 Mar 2021 09:41:20 +0800
> > Cc: 47431@debbugs.gnu.org
> >
> > > I think that's unrelated, so I don't understand why it hangs
> > > indefinitely for you.  Are you sure you waited enough time before
> > > giving up?
> >
> > It will hang up there forever.
>
> Maybe your network connection blocks some addresses or something?
> Otherwise, how to explain that it doesn't block for me?

I further debug this problem with tcpdump for a runing `emcas -Q`
process, as described below.

For `M-x whois RET gnu.org RET`, when the query succeeds, the
following info will be captured:

$ sudo tcpdump -i any port 43
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked v1), capture size
262144 bytes
15:00:29.061914 IP6 X10DAi.56918 >
whois.publicinterestregistry.net.whois: Flags [S], seq 1929893031, win
64440, options [mss 1432,sackOK,TS val 417951633 ecr 0,nop,wscale 7],
length 0
15:00:29.398867 IP6 whois.publicinterestregistry.net.whois >
X10DAi.56918: Flags [S.], seq 1816069595, ack 1929893032, win 1440,
options [mss 1379,nop,nop,TS val 2007125977 ecr 417951633,sackOK,eol],
length 0
15:00:29.398923 IP6 X10DAi.56918 >
whois.publicinterestregistry.net.whois: Flags [.], ack 1, win 64440,
options [nop,nop,TS val 417951970 ecr 2007125977], length 0
15:00:29.399038 IP6 X10DAi.56918 >
whois.publicinterestregistry.net.whois: Flags [P.], seq 1:10, ack 1,
win 64440, options [nop,nop,TS val 417951970 ecr 2007125977], length 9
15:00:30.297592 IP6 X10DAi.56918 >
whois.publicinterestregistry.net.whois: Flags [P.], seq 1:10, ack 1,
win 64440, options [nop,nop,TS val 417952869 ecr 2007125977], length 9
15:00:31.321603 IP6 X10DAi.56918 >
whois.publicinterestregistry.net.whois: Flags [P.], seq 1:10, ack 1,
win 64440, options [nop,nop,TS val 417953893 ecr 2007125977], length 9
15:00:31.339068 IP6 whois.publicinterestregistry.net.whois >
X10DAi.56918: Flags [P.], seq 1:1368, ack 10, win 2880, options
[nop,nop,TS val 2007127334 ecr 417952869], length 1367
15:00:31.339120 IP6 X10DAi.56918 >
whois.publicinterestregistry.net.whois: Flags [.], ack 1368, win
63073, options [nop,nop,TS val 417953910 ecr 2007127334], length 0

For `M-x whois RET baidu.com RET`, when the query fails, the following
info will be captured:

$ sudo tcpdump -i any port 43
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked v1), capture size
262144 bytes
15:05:24.433913 IP X10DAi.47186 > 198.41.3.79.whois: Flags [S], seq
1963456950, win 64240, options [mss 1460,sackOK,TS val 2174254150 ecr
0,nop,wscale 7], length 0
15:05:25.465604 IP X10DAi.47186 > 198.41.3.79.whois: Flags [S], seq
1963456950, win 64240, options [mss 1460,sackOK,TS val 2174255182 ecr
0,nop,wscale 7], length 0
15:05:27.481605 IP X10DAi.47186 > 198.41.3.79.whois: Flags [S], seq
1963456950, win 64240, options [mss 1460,sackOK,TS val 2174257198 ecr
0,nop,wscale 7], length 0

I also will see the following in *Messages* buffer:

For information about GNU Emacs and the GNU system, type C-h C-a.
open-network-stream: Failed connect: No route to host

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Polytechnic University of Science and Technology engineering
NO. 552 North Gangtie Road, Xingtai, China





  reply	other threads:[~2021-03-28  7:12 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27  1:39 bug#47431: Process Whois connection broken by remote peer Hongyi Zhao
2021-03-27  6:30 ` Eli Zaretskii
2021-03-27  7:23   ` Gregory Heytings
2021-03-27  8:08     ` Eli Zaretskii
2021-03-27 11:01       ` Gregory Heytings
2021-03-27 11:04         ` Gregory Heytings
2021-03-28 15:39         ` Lars Ingebrigtsen
2021-03-28 20:23           ` Gregory Heytings
2021-03-29  0:19             ` Hongyi Zhao
2021-03-29  4:50             ` Eli Zaretskii
2021-03-29  7:35               ` Gregory Heytings
2021-03-29  8:38                 ` Eli Zaretskii
2021-03-29 11:31                   ` Gregory Heytings
2021-03-29 12:02                     ` Eli Zaretskii
2021-03-29 12:12                       ` Gregory Heytings
2021-03-29 14:16                         ` Hongyi Zhao
2021-03-29 10:58             ` Lars Ingebrigtsen
2021-03-29 11:20               ` Gregory Heytings
2021-03-29 12:19                 ` Gregory Heytings
2021-03-30 13:22                   ` Lars Ingebrigtsen
2021-03-31  7:53                     ` Gregory Heytings
2021-03-31 13:39                       ` Lars Ingebrigtsen
2021-03-31 14:27                         ` Gregory Heytings
2021-04-14 14:55                           ` Stefan Kangas
2022-06-28 13:40                           ` Lars Ingebrigtsen
2022-07-28 10:35                             ` Lars Ingebrigtsen
2022-07-28 21:56                               ` Gregory Heytings
2022-07-29 11:34                                 ` Lars Ingebrigtsen
2021-03-27  9:50   ` Hongyi Zhao
2021-03-27  9:57   ` Hongyi Zhao
2021-03-27 10:33     ` Eli Zaretskii
2021-03-27 12:29       ` Hongyi Zhao
2021-03-27 13:44         ` Eli Zaretskii
2021-03-28  1:41           ` Hongyi Zhao
2021-03-28  6:38             ` Eli Zaretskii
2021-03-28  7:12               ` Hongyi Zhao [this message]
2021-03-28 14:11                 ` Lars Ingebrigtsen
2021-03-28 14:15                   ` Eli Zaretskii
2021-03-28 14:19                     ` Lars Ingebrigtsen
2021-03-28 14:55                       ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGP6POKK54PbZ_kxnJjHsVj81zLyC+StPNutYBUDpQHHSQ8bzw@mail.gmail.com \
    --to=hongyi.zhao@gmail.com \
    --cc=47431@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).