From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] Unreliable delivery
Date: Fri, 16 Jul 2021 14:06:11 -0400 [thread overview]
Message-ID: <9638F9EE898153F8D19FCE2F8E0DBBEC@5ess.inri.net> (raw)
In-Reply-To: <20210716105048.6a921b17@x1c.home.jtm.cx>
> Looks like the issue hasn't happened again, so unfortunately I don't
> have any trace. Here are some more detailed logs from the original
> issue.
thanks. of course the transient nature of these failures makes
nothing any easier. i've not yet figured out a good way to rig up
logging that can capture exactly where things are going long (or even
to examine the logging i've already captured, in depth).
(help appreciated)
in the meantime, i've added bind /net /net.alt to the cron-spawn runq
as well as the listeners for incoming mail. as ori suggested, this
gives us a free retry. subjectively, the queue is processing more
efficiently since this change.
sl
prev parent reply other threads:[~2021-07-16 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 23:50 Jonas
2021-07-14 23:59 ` Kurt H Maier
2021-07-15 1:20 ` Stanley Lieber
2021-07-15 14:07 ` John Murphy
2021-07-15 14:54 ` ori
2021-07-16 14:50 ` John Murphy
2021-07-16 18:06 ` sl [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9638F9EE898153F8D19FCE2F8E0DBBEC@5ess.inri.net \
--to=sl@stanleylieber.com \
--cc=9front@9front.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 NNTP newsgroup(s).