Gnus NNTP hang

Gnus NNTP hang

[Matthias Andree]

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

Re: Gnus NNTP hang

[Matthias Andree]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> 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).

Backtrace from C-g, with byte code omitted:

Lisp error: (quit)
  signal(quit nil)
  byte-code("..." [nntp-close-server signal quit nil] 3)
  byte-code("..." [group server nntp-connection-timeout timer nntp-with-open-group-internal nntp-possibly-change-group nil nnheader-run-at-time (lambda nil (let ... ...)) ((byte-code "..." [timer nnheader-cancel-timer] 2)) (byte-code "..." [nntp-server-buffer gnus-nov-is-evil nntp-nov-is-evil articles fetch-old article nntp-find-connection-buffer erase-buffer nntp-retrieve-headers-with-xover nov 0 t nil "HEAD" int-to-string mapconcat identity " " get-buffer process-status ... nntp-kill-buffer process-buffer delq nntp-open-connection err ... ... nnheader-report nntp "Couldn't open connection to %s" nntp-open-network-stream nntp-accept-response looking-at regexp-quote 1 gnus-point-at-bol "Couldn't open connection to %s." 50 re-search-forward "\n\\.\r?\n" "[34]" search-forward "\n" 20 nnheader-message 6 "NNTP: Receiving headers... %d%%" 100 "NNTP: Receiving headers...done" ...] 8) ((quit ...))] 4)
  nntp-retrieve-headers((828 829) "gmane.mail.imap.dovecot" "news" nil)
  gnus-retrieve-headers((828 829) "nntp+news:gmane.mail.imap.dovecot" nil)
  gnus-cache-retrieve-headers((828 829) "nntp+news:gmane.mail.imap.dovecot" nil)
  gnus-retrieve-headers((828 829) "nntp+news:gmane.mail.imap.dovecot" nil)
  gnus-fetch-headers((828 829))
  gnus-select-newsgroup("nntp+news:gmane.mail.imap.dovecot" nil nil)
  gnus-summary-read-group-1("nntp+news:gmane.mail.imap.dovecot" nil t nil nil nil)
  gnus-summary-read-group("nntp+news:gmane.mail.imap.dovecot" nil t nil nil nil nil)
  gnus-group-read-group(nil t)
  gnus-summary-reselect-current-group(nil t)
  gnus-summary-rescan-group(nil)
  call-interactively(gnus-summary-rescan-group)

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95

Re: Gnus NNTP hang

[Lars Magne Ingebrigtsen]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

>   nntp-retrieve-headers((828 829) "gmane.mail.imap.dovecot" "news" nil)
>   gnus-retrieve-headers((828 829) "nntp+news:gmane.mail.imap.dovecot" nil)

Try edebug-defun-nig `nttp-retrieve-headers' and see what's going
on...  It's kinda odd that you're seeing hangs in that function,
since it basically should just be calling
`nntp-retrieve-headers-with-xover', if things are OK...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen