From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Subject: Gnus NNTP hang
Date: Thu, 09 Oct 2003 02:37:06 +0200 [thread overview]
Message-ID: <m3y8vvgsb1.fsf@merlin.emma.line.org> (raw)
Hi,
I have a scenario that causes Gnus' NNTP client to hang. CVS version,
checked out "Mon Sep 29 21:52:56 2003" (as per lisp/CVS/Entries).
NNTP trace (server-side, with DJB's recordio wrapped around leafnode, CR
replaced by $):
2003-10-09 02:28:13.040812500 6962 < MODE READER$
2003-10-09 02:28:14.088993500 6962 > 200 Leafnode 2.0.0.alpha20031001a, pleased to meet you!$
2003-10-09 02:28:14.092283500 6962 < GROUP gmane.mail.imap.dovecot$
2003-10-09 02:28:14.093261500 6962 > 211 0 1 803 gmane.mail.imap.dovecot group selected$
2003-10-09 02:28:14.101396500 6962 < GROUP gmane.mail.imap.dovecot$
2003-10-09 02:28:14.101931500 6962 > 211 0 1 803 gmane.mail.imap.dovecot group selected$
I pressed M-g here after more articles arrived in that group.
2003-10-09 02:29:31.471722500 6962 < GROUP gmane.mail.imap.dovecot$
2003-10-09 02:29:32.513576500 6962 > 211 10 804 813 gmane.mail.imap.dovecot group selected$
2003-10-09 02:29:39.517770500 6962 < XOVER 2-803$
2003-10-09 02:29:39.518567500 6962 > 420 No articles in specified range.$
Gnus hangs here (C-g gets it unstuck though). Apparently it expects
further data (which will never come according to RFC-2980), but doesn't
send the commands to request that data. It should have sent XOVER
804-813 in the first place.
<GUESS id="wild">Seems the range calculation is either bogus or the
response handling doesn't figure that "420" means "no further data will
be sent".</GUESS>
I wonder if Gnus uses /older/ cached GROUP replies, failing to overwrite
it with more current replies it has requested.
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
next reply other threads:[~2003-10-09 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 0:37 Matthias Andree [this message]
2003-10-09 0:49 ` Matthias Andree
2003-10-16 14:37 ` Lars Magne 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y8vvgsb1.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.de \
/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.
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 NNTP newsgroup(s).