Send Outages-discussion mailing list submissions to
outages-discussion@outages.org
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/outages-discussion
or, via email, send a message with subject or body 'help' to
outages-discussion-requ...@outages.org
You can reach the person managing the list at
outages-discussion-ow...@outages.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages-discussion digest..."
Today's Topics:
1. Re: [outages] Zscaler Cloud Down (Chris Burwell)
2. Main list slow again (Andy Ringsmuth)
3. Re: Main list slow again (Jared Mauch)
4. Re: Main list slow again (Grant Taylor)
----------------------------------------------------------------------
Message: 1
Date: Wed, 6 Apr 2022 06:09:13 -0400
From: Chris Burwell <cburw...@gmail.com>
To: Julian Panke <m...@julianpanke.com>
Cc: outages-discussion@outages.org
Subject: Re: [Outages-discussion] [outages] Zscaler Cloud Down
Message-ID: <72d8f3ef-691c-4c55-a46a-e69acb57e...@gmail.com>
Content-Type: text/plain; charset="utf-8"
Any RCA or initial explanation from Zscaler?
> On Apr 6, 2022, at 04:10, Julian Panke via Outages <outa...@outages.org>
> wrote:
>
> ?Service recovered
>
>
>
>
>
>
>
> -------- Original-Nachricht --------
> Am 6. Apr. 2022, 09:41, Julian Panke via Outages schrieb:
>
> admin.zscloud.net does not resolve to A record.
> _______________________________________________
> Outages mailing list
> outa...@outages.org
> https://puck.nether.net/mailman/listinfo/outages
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220406/96a88a06/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - EmailAddress(s=m...@julianpanke.com) - 0xFD7892A4.asc
Type: application/octet-stream
Size: 3192 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220406/96a88a06/attachment-0001.obj>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220406/96a88a06/attachment-0003.htm>
------------------------------
Message: 2
Date: Thu, 21 Apr 2022 21:52:02 -0500
From: Andy Ringsmuth <a...@andyring.com>
To: Outages Discussion <outages-discussion@outages.org>
Subject: [Outages-discussion] Main list slow again
Message-ID: <db44f4ca-94f2-4d73-9798-7bc888617...@andyring.com>
Content-Type: text/plain; charset=us-ascii
For anyone interested, it looks like there is still sluggishness inherent to
the main outages@ list. A 10-minute delay, appears to be
repeatable/reproducible.
Noticed it when I sent a couple posts about a DNS outage at DreamHost. Here are
some relevant headers that seem to indicate the hiccup being within
puck.nether.net:
Received: from puck.nether.net (puck.nether.net. [204.42.254.5]) by
mx.google.com with ESMTPS id
j5-20020ac85c45000000b002eeb6daae5dsi2004320qtj.206.2022.04.21.18.20.16 for
<a...@newslink.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384
bits=256/256); Thu, 21 Apr 2022 18:20:16 -0700 (PDT)
Received: from puck.nether.net (localhost [IPv6:::1]) (using TLSv1.3 with
cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519
server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client
certificate requested) by puck.nether.net (Postfix) with ESMTPSA id
D7B75540091; Thu, 21 Apr 2022 21:18:32 -0400 (EDT)
Received: from butterfly.birch.relay.mailchannels.net
(butterfly.birch.relay.mailchannels.net [23.83.209.27]) (using TLSv1.2 with
cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate
requested) by puck.nether.net (Postfix) with ESMTPS id D02FE540065 for
<outa...@outages.org>; Thu, 21 Apr 2022 21:10:21 -0400 (EDT)
and second message:
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.3
with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519
server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client
certificate requested) by pdx1-sub0-mail-mx204.dreamhost.com (Postfix) with
ESMTPS id 4KkzMM46jyz1fpR for <a...@andyring.com>; Thu, 21 Apr 2022 19:46:55
-0700 (PDT)
Received: from puck.nether.net (localhost [IPv6:::1]) (using TLSv1.3 with
cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519
server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client
certificate requested) by puck.nether.net (Postfix) with ESMTPSA id
3ABFD5400A6; Thu, 21 Apr 2022 22:45:30 -0400 (EDT)
Received: from cyan.elm.relay.mailchannels.net (cyan.elm.relay.mailchannels.net
[23.83.212.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
bits)) (No client certificate requested) by puck.nether.net (Postfix) with
ESMTPS id B1853540075 for <outa...@outages.org>; Thu, 21 Apr 2022 22:37:34
-0400 (EDT)
----
Andy Ringsmuth
5609 Harding Drive
Lincoln, NE 68521-5831
(402) 202-1230
a...@andyring.com
------------------------------
Message: 3
Date: Thu, 21 Apr 2022 23:04:58 -0400
From: Jared Mauch <ja...@puck.nether.net>
To: Andy Ringsmuth <a...@andyring.com>
Cc: Outages Discussion <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] Main list slow again
Message-ID: <2db668a0-4623-473b-ac19-659c2d983...@puck.nether.net>
Content-Type: text/plain; charset=utf-8
I found two problems -
1) systemd exists and wasn?t handling DNS properly so it was falling back
2) spamassassin was semi-wedged which was causing it to take longer for a few
things, which I?m sure that #1 above didn?t help
Lets see if this one passes through faster.
- jared
> On Apr 21, 2022, at 10:52 PM, Andy Ringsmuth <a...@andyring.com> wrote:
>
> For anyone interested, it looks like there is still sluggishness inherent to
> the main outages@ list. A 10-minute delay, appears to be
> repeatable/reproducible.
>
> Noticed it when I sent a couple posts about a DNS outage at DreamHost. Here
> are some relevant headers that seem to indicate the hiccup being within
> puck.nether.net:
>
>
> Received: from puck.nether.net (puck.nether.net. [204.42.254.5]) by
> mx.google.com with ESMTPS id
> j5-20020ac85c45000000b002eeb6daae5dsi2004320qtj.206.2022.04.21.18.20.16 for
> <a...@newslink.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384
> bits=256/256); Thu, 21 Apr 2022 18:20:16 -0700 (PDT)
>
> Received: from puck.nether.net (localhost [IPv6:::1]) (using TLSv1.3 with
> cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519
> server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client
> certificate requested) by puck.nether.net (Postfix) with ESMTPSA id
> D7B75540091; Thu, 21 Apr 2022 21:18:32 -0400 (EDT)
>
> Received: from butterfly.birch.relay.mailchannels.net
> (butterfly.birch.relay.mailchannels.net [23.83.209.27]) (using TLSv1.2 with
> cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate
> requested) by puck.nether.net (Postfix) with ESMTPS id D02FE540065 for
> <outa...@outages.org>; Thu, 21 Apr 2022 21:10:21 -0400 (EDT)
>
> and second message:
>
> Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using
> TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519
> server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client
> certificate requested) by pdx1-sub0-mail-mx204.dreamhost.com (Postfix) with
> ESMTPS id 4KkzMM46jyz1fpR for <a...@andyring.com>; Thu, 21 Apr 2022 19:46:55
> -0700 (PDT)
>
> Received: from puck.nether.net (localhost [IPv6:::1]) (using TLSv1.3 with
> cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519
> server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client
> certificate requested) by puck.nether.net (Postfix) with ESMTPSA id
> 3ABFD5400A6; Thu, 21 Apr 2022 22:45:30 -0400 (EDT)
>
> Received: from cyan.elm.relay.mailchannels.net
> (cyan.elm.relay.mailchannels.net [23.83.212.47]) (using TLSv1.2 with cipher
> ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested)
> by puck.nether.net (Postfix) with ESMTPS id B1853540075 for
> <outa...@outages.org>; Thu, 21 Apr 2022 22:37:34 -0400 (EDT)
>
>
> ----
> Andy Ringsmuth
> 5609 Harding Drive
> Lincoln, NE 68521-5831
> (402) 202-1230
> a...@andyring.com
>
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion@outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion
------------------------------
Message: 4
Date: Thu, 21 Apr 2022 21:14:59 -0600
From: Grant Taylor <gtay...@tnetconsulting.net>
To: outages-discussion@outages.org
Subject: Re: [Outages-discussion] Main list slow again
Message-ID:
<694a5c20-72e7-ca7e-c90f-5e6f56834...@spamtrap.tnetconsulting.net>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 4/21/22 8:52 PM, Andy Ringsmuth wrote:
> For anyone interested, it looks like there is still sluggishness
> inherent to the main outages@ list. A 10-minute delay, appears to
> be repeatable/reproducible.
I don't know about puck.nether.net to Gmail, but the ~8 minute delay
between Received: headers from puck.nether.net itself seems ...
conspicuous to me.
Additional data:
The message that I'm replying to seems to have a much shorter delay:
Received: from puck.nether.net (localhost [IPv6:::1])
... by puck.nether.net ...
Thu, 21 Apr 2022 22:55:05 -0400 (EDT)
Received: from buffalo.ash.relay.mailchannels.net
... by puck.nether.net ...
Thu, 21 Apr 2022 22:52:06 -0400 (EDT)
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4017 bytes
Desc: S/MIME Cryptographic Signature
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220421/2e70c6c5/attachment.p7s>
------------------------------
Subject: Digest Footer
_______________________________________________
Outages-discussion mailing list
Outages-discussion@outages.org
https://puck.nether.net/mailman/listinfo/outages-discussion
------------------------------
End of Outages-discussion Digest, Vol 146, Issue 1
**************************************************
