[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Closed connection errors with the new Gnus
From: |
Stefan Monnier |
Subject: |
Closed connection errors with the new Gnus |
Date: |
Tue, 12 Oct 2004 11:34:22 -0400 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3.50 (gnu/linux) |
Since we switched to the new Gnus, I tend to get errors about the server
closing the connection. I'm assume such disconnections happened before as
well, but they were handled transparently.
See the backtrace below (which is all I can offer just now). Anybody knows
what's going on? Is it just a matter of a failure to catch the error and
reconnect&retry?
Stefan
Debugger entered--Lisp error: (error "Server closed connection")
signal(error ("Server closed connection"))
error("Server closed connection")
apply(error "Server closed connection")
nntp-report("Server closed connection")
nntp-accept-process-output(nil)
byte-code("
=\203%\nT\305!\203\306\f\204\n\307U\203\310\311\312\"\210\313\202\305\207"
[article gnus-async-current-prefetch-article tries proc nntp-have-messaged
nntp-accept-process-output 0 3 gnus-message 5 "Waiting for async article..." t]
3)
gnus-async-wait-for-article(15752)
gnus-async-request-fetched-article("nnimap+diro:emacs" 15752 #<buffer
*Article*>)
gnus-request-article-this-buffer(15752 "nnimap+diro:emacs")
gnus-article-prepare(15752 nil)
gnus-summary-display-article(15752)
gnus-summary-next-article(t nil)
gnus-summary-next-unread-article()
call-interactively(gnus-summary-next-unread-article)
- Closed connection errors with the new Gnus,
Stefan Monnier <=