From: nljlistbox2@gmail.com (N. Jackson)
To: Eli Zaretskii <eliz@gnu.org>
Cc: eric@ericabrahamsen.net, larsi@gnus.org, 28596@debbugs.gnu.org
Subject: bug#28596: 26.0.60; Gnus gets into an ambiguous plugged/unplugged state that prevents retrieval of news
Date: Thu, 12 Jul 2018 11:33:32 -0400 [thread overview]
Message-ID: <877em0ii43.fsf@moondust.localdomain> (raw)
In-Reply-To: <87tvpe6e2x.fsf@moondust.localdomain> (N. Jackson's message of "Wed, 04 Jul 2018 14:38:46 -0400")
At 14:38 -0400 on Wednesday 2018-07-04, N. Jackson wrote:
>
>>> At 19:50 +0300 on Wednesday 2018-07-04, Eli Zaretskii wrote:
>>>>
>>>> Is it possible for you to try the branch? I think it's
>>>> important to know whether this problem still exists on the
>>>> release branch.
> I have really built the emacs-26 branch [1] this time!
>
> As promised, I will use it from now on as my every-day Emacs and
> report back here if I see the bug again.
>
> [1] Repository revision: 0dce5e59206db7bd0b9cd43ae712272105300ae4
Yes, the problem still exists. Gnus got into the confused
plugged/unplugged state again this morning.
FWIW:
M-x emacs-uptime RET
==> 5 days, 0 hours, 26 minutes, 55 seconds
Memory information:
((conses 16 1153669 478417)
(symbols 48 121724 355)
(miscs 40 24187 11415)
(strings 32 308736 20050)
(string-bytes 1 12884595)
(vectors 16 74179)
(vector-slots 8 2504362 73640)
(floats 8 2016 1881)
(intervals 56 41378 48502)
(buffers 992 323))
After Gnus got into the confused state and after trying for several
minutes to get it back to it's senses, I exited Gnus (but not Emacs) and
restarted Gnus (with M-x gnus RET) and it was still in it's stuck state
and it printed these messages as it started:
20180712T104052.549> Reading /home/nlj/.newsrc.eld...
20180712T104052.735> Opening nnfolder server on archive...
20180712T104052.736> Opening nnfolder server on archive...done
20180712T104052.737> Opening nntp server on nntp.olduse.net...
20180712T104132.771> Opening nntp server on nntp.olduse.net...failed: >>> (error nntp.olduse.net/nntp Name or service not known)
20180712T104132.772> Opening nntp server on nntp.aioe.org...
20180712T104212.811> Opening nntp server on nntp.aioe.org...done
20180712T104212.811> Opening nntp server on dusty...
20180712T104252.851> Opening nntp server on dusty...failed: >>> (error news.gmane.org/nntp Name or service not known)
20180712T104252.852> Opening nntp server on news.gmane.org...
20180712T104332.887> Opening nntp server on news.gmane.org...done
20180712T104332.887> Opening nnimap server on Local Dovecot Mailstore...
20180712T104332.888> Opening connection to localhost via tls...
20180712T104333.079> Opening connection to localhost...done
20180712T104333.080> Opening nnimap server on Local Dovecot Mailstore...done
20180712T104333.144> No new newsgroups
20180712T104333.161> Checking new news...
20180712T104333.164> Reading active file via nnnil...
20180712T104333.164> Reading active file via nnnil...
20180712T104333.164> Reading active file via nnnil...done
20180712T104333.164> Reading active file from nntp.olduse.net via nntp...
20180712T104333.164> Opening nntp server on nntp.olduse.net...
20180712T104333.165> Server nntp+nntp.olduse.net previously determined to be down; not retrying
20180712T104333.165> Opening nntp server on nntp.olduse.net...failed: >>> (error news.gmane.org/nntp Name or service not known)
20180712T104333.192> Opening nntp server on nntp.aioe.org...
20180712T104333.193> Opening nntp server on nntp.aioe.org...done
20180712T104333.194> Opening nntp server on news.gmane.org...
20180712T104333.195> Opening nntp server on news.gmane.org...done
20180712T104333.201> nnimap read 0k from localhost
20180712T104333.408> Reading active file from archive via nnfolder...
20180712T104333.409> Opening nnfolder server on archive...
20180712T104333.410> Opening nnfolder server on archive...done
20180712T104333.410> Reading active file from archive via nnfolder...
20180712T104333.411> Reading active file from archive via nnfolder...done
20180712T104333.412> Reading active file via nnfolder...
20180712T104333.412> Opening nnfolder server...
20180712T104333.413> Opening nnfolder server...done
20180712T104333.440> Reading incoming mail from file...
20180712T104333.441> nnfolder: Reading incoming mail (no new mail)...done
20180712T104333.442> Reading active file via nnfolder...
20180712T104333.443> Reading active file via nnfolder...done
20180712T104333.443> Reading active file via nndraft...
20180712T104333.446> Reading active file via nndraft...
20180712T104333.447> Reading active file via nndraft...done
20180712T104333.448> Checking new news...done
Warning: Opening nntp server on nntp.olduse.net...failed: >>> (error news.gmane.org/nntp Name or service not known); Server nntp+nntp.olduse.net previously determined to be down; not retrying; Opening nntp server on dusty...failed: >>> (error news.gmane.org/nntp Name or service not known); Opening nntp server on nntp.olduse.net...failed: >>> (error nntp.olduse.net/nntp Name or service not known)
The errors for olduse.net happen all the time (I suspect the site has
gone away), so I assume they are unrelated, but the second message at
20180712T104333.165 seems odd: it appears to suggest that it was
checking olduse.net and gmane.org failed. Or maybe I'm just not reading
that right.
[The server I have set up with the name of "dusty" is on gmane, so the
messages about gmane not being known when checking dusty do make sense.]
I then exited Gnus and exited Emacs, restarted Emacs, restarted Gnus and
everything was back to working as normal.
next prev parent reply other threads:[~2018-07-12 15:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 15:01 bug#28596: 26.0.60; [Gnus] Checking mail is no longer reliable and C-g no longer quits N. Jackson
2017-09-25 17:03 ` N. Jackson
2017-09-25 17:14 ` Noam Postavsky
2017-09-26 14:13 ` N. Jackson
2017-09-29 9:10 ` Eli Zaretskii
2017-09-29 15:20 ` Eric Abrahamsen
2017-09-29 17:27 ` N. Jackson
2017-09-29 20:17 ` Eric Abrahamsen
2017-12-02 17:40 ` Eli Zaretskii
2017-12-04 17:14 ` N. Jackson
2017-12-04 17:56 ` Eli Zaretskii
2017-12-22 13:43 ` Eli Zaretskii
2017-12-27 21:00 ` Lars Ingebrigtsen
[not found] ` <871sjfdaql.fsf_-_@moondust.localdomain>
2017-12-28 12:07 ` bug#28596: 26.0.60; Gnus gets into an ambiguous plugged/unplugged state that prevents retrieval of news Lars Ingebrigtsen
2017-12-28 16:27 ` Eli Zaretskii
2017-12-28 16:29 ` Lars Ingebrigtsen
2017-12-28 17:54 ` Eli Zaretskii
2017-12-28 20:15 ` Lars Ingebrigtsen
2017-12-29 0:14 ` N. Jackson
2018-07-02 17:55 ` Eli Zaretskii
2018-07-03 0:19 ` N. Jackson
2018-07-04 16:50 ` Eli Zaretskii
2018-07-04 18:03 ` N. Jackson
2018-07-04 18:13 ` N. Jackson
2018-07-04 18:30 ` Eli Zaretskii
2018-07-04 18:38 ` N. Jackson
2018-07-04 18:41 ` Eli Zaretskii
2018-07-12 15:33 ` N. Jackson [this message]
2018-07-12 15:45 ` Eli Zaretskii
2019-09-27 15:25 ` Lars Ingebrigtsen
2020-07-19 15:44 ` Lars Ingebrigtsen
2018-07-04 18:30 ` Eli Zaretskii
2017-12-11 17:58 ` bug#28596: " N. Jackson
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=877em0ii43.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=28596@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.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).