From: Eric Wong <e@80x24.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: meta@public-inbox.org
Subject: Re: Occasional public-inbox-httpd flakiness
Date: Tue, 5 Nov 2024 23:24:45 +0000 [thread overview]
Message-ID: <20241105232445.M291444@dcvr> (raw)
In-Reply-To: <875xp15n3o.fsf@trenco.lwn.net>
Jonathan Corbet <corbet@lwn.net> wrote:
> The LWN archive server is running Debian's 1.9.0 public-inbox package.
> Every now and then, usually after at least a week of operation, HTTP
> requests will start returning empty messages; I find stuff like this in
> the log:
>
> Nov 05 15:24:37 archive2.lwn.net public-inbox-httpd[1267166]: Use of uninitialized value in index at /usr/share/perl5/PublicInbox/Eml.pm line 109.
> Nov 05 15:24:37 archive2.lwn.net public-inbox-httpd[1267166]: Use of uninitialized value in index at /usr/share/perl5/PublicInbox/Eml.pm line 109.
> Nov 05 15:24:37 archive2.lwn.net public-inbox-httpd[1267166]: Use of uninitialized value in pattern match (m//) at /usr/share/perl5/PublicInbox/Eml.pm line 115.
> Nov 05 15:24:37 archive2.lwn.net public-inbox-httpd[1267166]: Use of uninitialized value in pattern match (m//) at /usr/share/perl5/PublicInbox/Eml.pm line 120.
> Nov 05 15:24:37 archive2.lwn.net public-inbox-httpd[1267166]: Use of uninitialized value in pattern match (m//) at /usr/share/perl5/PublicInbox/Eml.pm line 127.
> Nov 05 15:24:37 archive2.lwn.net public-inbox-httpd[1267166]: Use of uninitialized value in substitution (s///) at /usr/share/perl5/PublicInbox/Mbox.pm line 115.
Definitely something that's popped up in my recollection; but
hasn't happened in a while for Eml.pm and Mbox.pm (yeah, it's
been a while since v1.9 :x).
Are the git cat-file (or Gcf2) processes still running? Are any
successful responses returned for requests to mail messages?
Error handling should be improved in .git nowadays but I'm still
struggling to get a release out due to coderepo <=> inbox mapping
messiness :<
> The pattern is pretty much always the same. Restarting
> public-inbox-httpd makes the problem go away again.
Usually, uninitialized value errors are isolated to a single
request (e.g. broken emails) and there shouldn't be a
need to restart unless every request is failing.
> Is this a problem that anybody else has seen, or am I especially
> lucky...?
I've had some similar problems from inboxes/coderepos getting
removed; also there's OOMs on my HW causing git processes to fail.
next prev parent reply other threads:[~2024-11-05 23:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 22:31 Occasional public-inbox-httpd flakiness Jonathan Corbet
2024-11-05 23:24 ` Eric Wong [this message]
2024-11-05 23:29 ` Jonathan Corbet
2024-11-05 23:34 ` Eric Wong
2024-11-12 19:14 ` Jonathan Corbet
2024-11-12 19:20 ` Eric Wong
2024-11-12 21:25 ` Jonathan Corbet
2024-11-12 21:41 ` Eric Wong
2024-11-12 21:46 ` Jonathan Corbet
2024-11-12 21:54 ` 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=20241105232445.M291444@dcvr \
--to=e@80x24.org \
--cc=corbet@lwn.net \
--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).