From: Michael Slass <miknrene@drizzle.com>
Subject: gnus fails to open nntp server every other time
Date: Sat, 05 Oct 2002 00:17:40 GMT [thread overview]
Message-ID: <m33crlwxdq.fsf@localhost.localdomain> (raw)
Hi:
using gnus 5.9.0 on linux (RH 7.3 kernel 2.4.18-10)
From the group buffer, when I hit "G" to check for new news and mail,
on odd-numbered tries, it succeeds, and even numbered tries, it
fails.
The difference is that on the failures, it doesn't try to connect to
the news server -- I think gnus believes it's already connected.
I've advised gnus-group-get-new-news to show existing buffers
and do a netstat before running, and to put the output in the
*Messages* buffer.
It looks like for failures, netstat shows an established socket to the
news server, and there's a leftover buffer:
#<buffer *server netnews.attbi.com nntp *nntpd**>
Also, there's no message:
Opening nntp server on netnews.attbi.com...
Instead, it just jumps straight to:
Reading active file from netnews.attbi.com via nntp...
where the debugger starts.
Anyone have any ideas on why this is happening, and how I can stop it?
Thanks.
--
Mike
From the *Messages* buffer:
For failures:
------------------------------------------------------------
gnus-group-get-new-news diagnostics:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 192.168.1.2:1600 *:* LISTEN -
tcp 0 0 *:32768 *:* LISTEN -
tcp 0 0 eric:32769 *:* LISTEN -
tcp 0 0 *:printer *:* LISTEN -
tcp 0 0 eric:3110 *:* LISTEN -
tcp 0 0 *:6502 *:* LISTEN -
tcp 0 0 *:sunrpc *:* LISTEN -
tcp 0 0 *:x11 *:* LISTEN -
tcp 0 0 eric:3025 *:* LISTEN -
tcp 0 0 *:ssh *:* LISTEN -
tcp 0 0 *:https *:* LISTEN -
tcp 0 0 192.168.1.2:32785 cascadia.drizzle.co:ssh ESTABLISHED -
tcp 0 0 192.168.1.2:33744 netnews.attbi.com:nntp ESTABLISHED 3196/emacs
tcp 0 0 eric:3025 eric:33747 TIME_WAIT -
(
#<buffer *Group*>
#<buffer *scratch*>
#<buffer *Minibuf-1*>
#<buffer *Minibuf-0*>
#<buffer *Messages*>
#<buffer *Echo Area 0*>
#<buffer *Echo Area 1*>
#<buffer *nntpd*>
#<buffer *server netnews.attbi.com nntp *nntpd**>
#<buffer *gnus work*>
#<buffer trace of POP session to localhost>
#<buffer *nnmail message-id cache*>
#<buffer *Original Article*>
#<buffer *Async Prefetch Article*>
#<buffer *gnus article copy*>
#<buffer *canonical address*>
#<buffer *extract address components*>
#<buffer *message work*>
#<buffer *trace of SMTP session to localhost*>
#<buffer October-2002>
#<buffer 13>
#<buffer .newsrc-dribble>
#<buffer *Article*>)
Reading active file from netnews.attbi.com via nntp...
Loading debug...done
Entering debugger...
Debugger entered--Lisp error: (error "Selecting deleted buffer")
nntp-retrieve-groups(("comp.emacs" "gnu.emacs.gnus" "gnu.emacs.sources" "gnu.emacs.help") "netnews.attbi.com")
gnus-retrieve-groups(("comp.emacs" "gnu.emacs.gnus" "gnu.emacs.sources" "gnu.emacs.help") (nntp "netnews.attbi.com"))
gnus-read-active-file-2(("comp.emacs" "gnu.emacs.gnus" "gnu.emacs.sources" "gnu.emacs.help") (nntp "netnews.attbi.com"))
gnus-read-active-file-1((nntp "netnews.attbi.com") nil)
gnus-read-active-file()
ad-Orig-gnus-group-get-new-news(nil)
(setq ad-return-value (ad-Orig-gnus-group-get-new-news arg))
(let (ad-return-value) (message "gnus-group-get-new-news diagnostics:\n%s\n%s" (shell-command-to-string "netstat -tap 2>/dev/null") (replace-regexp-in-string "#" "\n#" ...)) (setq ad-return-value (ad-Orig-gnus-group-get-new-news arg)) ad-return-value)
gnus-group-get-new-news(nil)
call-interactively(gnus-group-get-new-news)
------------------------------------------------------------
For successes:
------------------------------------------------------------
gnus-group-get-new-news diagnostics:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 192.168.1.2:1600 *:* LISTEN -
tcp 0 0 *:32768 *:* LISTEN -
tcp 0 0 eric:32769 *:* LISTEN -
tcp 0 0 *:printer *:* LISTEN -
tcp 0 0 eric:3110 *:* LISTEN -
tcp 0 0 *:6502 *:* LISTEN -
tcp 0 0 *:sunrpc *:* LISTEN -
tcp 0 0 *:x11 *:* LISTEN -
tcp 0 0 eric:3025 *:* LISTEN -
tcp 0 0 *:ssh *:* LISTEN -
tcp 0 0 *:https *:* LISTEN -
tcp 0 0 192.168.1.2:32785 cascadia.drizzle.co:ssh ESTABLISHED -
(
#<buffer *Group*>
#<buffer *Messages*>
#<buffer *Backtrace*>
#<buffer *Minibuf-1*>
#<buffer *scratch*>
#<buffer *Minibuf-0*>
#<buffer *Echo Area 0*>
#<buffer *Echo Area 1*>
#<buffer *nntpd*>
#<buffer *gnus work*>
#<buffer trace of POP session to localhost>
#<buffer *nnmail message-id cache*>
#<buffer *Original Article*>
#<buffer *Async Prefetch Article*>
#<buffer *gnus article copy*>
#<buffer *canonical address*>
#<buffer *extract address components*>
#<buffer *message work*>
#<buffer *trace of SMTP session to localhost*>
#<buffer October-2002>
#<buffer 13>
#<buffer .newsrc-dribble>
#<buffer *Article*>)
Opening nntp server on netnews.attbi.com...
Reading active file from netnews.attbi.com via nntp...
Reading active file via nnml...
nnml: Reading incoming mail from pop...
nnml: Reading incoming mail (no new mail)...done
Reading active file via nnml...done
Reading active file from archive via nnfolder...done
Checking new news...done
------------------------------------------------------------Matches Active Internet connections (...
--
Mike Slass
reply other threads:[~2002-10-05 0:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m33crlwxdq.fsf@localhost.localdomain \
--to=miknrene@drizzle.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).