Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1maL5R-0000F0-EI for pgsql-bugs@arkaria.postgresql.org; Tue, 12 Oct 2021 16:57:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1maL5Q-0002uk-9p for pgsql-bugs@arkaria.postgresql.org; Tue, 12 Oct 2021 16:57:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1maL2T-0006wR-KM for pgsql-bugs@lists.postgresql.org; Tue, 12 Oct 2021 16:54:05 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1maL2R-0004hG-9e for pgsql-bugs@lists.postgresql.org; Tue, 12 Oct 2021 16:54:05 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 19CGs0qj580888; Tue, 12 Oct 2021 12:54:00 -0400 From: Tom Lane To: Matt Bush cc: postgres@netlag.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17224: Postgres Yum repo mirror has expired SSL certificate In-reply-to: References: <17224-cf1052548fac15af@postgresql.org> <577282.1634053399@sss.pgh.pa.us> Comments: In-reply-to Matt Bush message dated "Tue, 12 Oct 2021 11:04:43 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <580886.1634057640.1@sss.pgh.pa.us> Date: Tue, 12 Oct 2021 12:54:00 -0400 Message-ID: <580887.1634057640@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Matt Bush writes: > As mentioned, it's entirely intermittent. The playbook action immediately > prior to the failing step is to verify that the installed ca-certificates > us up-to-date, which it is: > $ rpm -qa | grep ca-certificates > ca-certificates-2021.2.50-72.el7_9.noarch Okay, but what about your openssl version? (I'd think RHEL7 contains something reasonably up-to-date, but I might be wrong.) It might be worth logging the output of "curl -V". The intermittency might be an artifact of consulting several different mirrors, only some of which use Let's Encrypt certificates. (Although I think all of *.postgresql.org do use those.) You could also investigate by logging the output of openssl s_client -connect download.postgresql.org:443