From: Eric Wong <e@80x24.org>
To: Sergey Organov <sorganov@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: inbox.comp.version-control.git just stopped working
Date: Wed, 7 Mar 2018 09:37:54 +0000 [thread overview]
Message-ID: <20180307093754.GA27748@dcvr> (raw)
In-Reply-To: <8760684f31.fsf@javad.com>
Sergey Organov <sorganov@gmail.com> wrote:
> Hi,
>
> I'm using inbox.comp.version-control.git for a few days now, and it
> worked fine till now. I'm using Gnus from within Emacs to access it via
> NNTP.
>
> Just a few minutes ago, however, attempts to enter the
> inbox.comp.version-control.git from Gnus started to give "Server closed
> connection" error, even though some other groups on public-inbox still
> work fine.
Uh oh, did you notice any delay in how long it took for you
to see this message from when Gnus started connecting?
I'm not familiar with Gnus or Emacs at all, but is there a way
you can show me a protocol dump?
> The only difference I see is that inbox.comp.version-control.git has
> much more messages than most of the other groups on the
> public-inbox... wait...
>
> Here are 3 fattest groups, and none of them I can visit from Gnus:
>
> 438320: inbox.comp.lang.ruby.core
> 438320: inbox.comp.lang.ruby.dev
Eeek, I noticed 438320 was introduced via ruby-talk; so maybe I
have a bug in that causing messages to leak into the other Ruby
lists I follow :x
> 341199: inbox.comp.version-control.git
OK, 341199 looks reasonable.
> To check if it's Gnus problem, I've just visited:
>
> 1523921: gmane.linux.debian.devel.bugs.general
>
> and it works fine.
>
> Any idea what's wrong between Gnus and public-inbox for large groups?
Not sure, I haven't made any changes to the code running on
"public-inbox.org" in a few weeks, now. I suspect there's a
fairness problem in the NNTP server in how it handles XOVER
and that might cause timeouts in clients.
Fwiw, I might not be online much the next few days.
next prev parent reply other threads:[~2018-03-07 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 5:41 inbox.comp.version-control.git just stopped working Sergey Organov
2018-03-07 9:37 ` Eric Wong [this message]
2018-03-07 9:56 ` Eric Wong
2018-03-07 10:06 ` Sergey Organov
[not found] ` <877eqoylu6.fsf@javad.com>
2018-03-07 19:16 ` Eric Wong
2018-03-12 5:03 ` Sergey Organov
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180307093754.GA27748@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=sorganov@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.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).