From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: nntpd errors retrieving group list
Date: Tue, 24 Aug 2021 20:11:15 +0000 [thread overview]
Message-ID: <20210824201115.GA8587@dcvr> (raw)
In-Reply-To: <20210824135835.7ujvhisruasihlpo@nitro.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hello:
>
> I tried the nntpd daemon on x-lore, but I seem to be hitting something odd
> while retrieving the group list. This is from syslog:
>
> public-inbox-nntpd: Can't call method "minmax" on an undefined value at /usr/local/share/perl5/PublicInbox/NNTP.pm line 264.
> public-inbox-nntpd: during long response[14] - 0.0 03772
>
> This is in nntpd.out.log
>
> [14] MODE READER - 0.000052
> [14] LIST - 0.003624 pending
> deferred[14] aborted - 0.003772
>
> All entries in the config file have a newsgroup= entry, so I don't have any
> immediate insights why something would be "undefined" at that line.
Any chance you're out-of-FDs or permissions are wrong?
There's also an off chance a non-inbox (extindex) object is there.
Perhaps this debugging patch can shine a light on things:
diff --git a/lib/PublicInbox/NNTP.pm b/lib/PublicInbox/NNTP.pm
index 9df47133..6f07db84 100644
--- a/lib/PublicInbox/NNTP.pm
+++ b/lib/PublicInbox/NNTP.pm
@@ -261,8 +261,11 @@ sub parse_time ($$;$) {
sub group_line ($$) {
my ($self, $ibx) = @_;
- my ($min, $max) = $ibx->mm->minmax;
- more($self, "$ibx->{newsgroup} $max $min n");
+ eval {
+ my ($min, $max) = $ibx->mm->minmax;
+ more($self, "$ibx->{newsgroup} $max $min n");
+ };
+ warn "Error: $@ - $ibx $ibx->{newsgroup}\n" if $@;
}
sub newgroups_i {
next prev parent reply other threads:[~2021-08-24 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 13:58 nntpd errors retrieving group list Konstantin Ryabitsev
2021-08-24 20:11 ` Eric Wong [this message]
2021-08-24 20:48 ` Konstantin Ryabitsev
2021-08-24 22:49 ` [PATCH] imap+nntp: die loudly if ->mm or ->over disappear Eric Wong
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=20210824201115.GA8587@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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.
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).