From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.5 required=5.0 tests=DATE_IN_PAST_24_48 autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 23212 invoked from network); 26 Mar 2021 22:55:24 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 26 Mar 2021 22:55:24 -0000 Received: from 5ess.inri.net ([107.191.111.177]) by 1ess; Thu Mar 25 15:48:40 -0400 2021 Received: from [127.0.0.1] ([166.170.222.126]) by 5ess; Thu Mar 25 15:48:40 -0400 2021 Date: Thu, 25 Mar 2021 15:48:37 -0400 From: Stanley Lieber To: 9front@9front.org In-Reply-To: <5L9dOv9PILwOg1dZG9BhO2HCJucjv_AjzL84cqY2e-nU7yDeKQ4hQ_T8iZdEf--f7Z_EKodQiYDgYrOj1JqYUX876PzfBRP29ByPHnCE7RA=@protonmail.com> References: <5L9dOv9PILwOg1dZG9BhO2HCJucjv_AjzL84cqY2e-nU7yDeKQ4hQ_T8iZdEf--f7Z_EKodQiYDgYrOj1JqYUX876PzfBRP29ByPHnCE7RA=@protonmail.com> Message-ID: <6253876A-FF7D-4282-965F-3B4069C111DA@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: full-stack reduce/map browser Subject: Re: [9front] issues with the mailing list Reply-To: 9front@9front.org Precedence: bulk On March 25, 2021 2:07:35 PM EDT, kemal wrote: >your message got sent late but latest messages are coming much faster com= pared >to older messages=2E > >=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original = Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 >On Thursday, March 25, 2021 2:17 PM, Stanley Lieber wrote: > >> On March 25, 2021 9:48:40 AM EDT, Stanley Lieber sl@stanleylieber=2Ecom= wrote: >> >> > 1ess; walk /mail/queue|wc -l 6906 >> > divide this number roughly in three to get the number of presently un= delivered messages (to all lists; this machine serves all/only 9front/cat-v= /werc lists)=2E of those, the vast majority are transient dns lookup failur= es for good domains=2E we alleviated this somewhat already by extending the= lookup timeout, but clearly something else is going on=2E >> > all of this started when I moved the server back to 9cloud from ramno= de=2E the first thing we noticed was the default setup hammered the now non= -ssd disk by launching runq every time it processed a message=2E this broug= ht the whole machine to a crawl (this machine also serves the websites -- p= eople complained)=2E that was solved by parallelizing a limited number of r= unqs and launching them periodically from cron=2E the side effect of this i= s exposing all kinds of weirdness that was previously masked by the never-e= nding blast of runqs, which, in spite of transient failures, always eventua= lly clears out the queue=2E >> > I'm not yet sure why the transient dns failures are happening=2E >> > sl >> >> the server has now been configured to run its own resolver=2E we'll see= if this results in fewer transient lookup failures=2E >> >> sl > > > 1ess; date =20 Thu Mar 25 15:47:40 EDT 2021 1ess; walk /mail/qu= eue|wc -l =20 5575