Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uEqHm-00DneK-Ha for pgsql-general@arkaria.postgresql.org; Tue, 13 May 2025 14:07:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uEqHl-005h6v-L7 for pgsql-general@arkaria.postgresql.org; Tue, 13 May 2025 14:07:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uEqHl-005h6i-8E for pgsql-general@lists.postgresql.org; Tue, 13 May 2025 14:07:09 +0000 Received: from mail-yb1-xb34.google.com ([2607:f8b0:4864:20::b34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uEqHi-001gcN-14 for pgsql-general@postgresql.org; Tue, 13 May 2025 14:07:08 +0000 Received: by mail-yb1-xb34.google.com with SMTP id 3f1490d57ef6-e7904da218aso3127799276.2 for ; Tue, 13 May 2025 07:07:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander.net; s=mail; t=1747145225; x=1747750025; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=S0yU+yusUuaSJP2VmKOrYiDsBhgc+QU1Nqy5d0LZQnM=; b=GABxyDa4bTHG2r0LESw0R/S9s5jYH+WxUztXqzxTgAmsM7xGLlWWzMU/9HTwTaSiEb MHL+Ffyy0AxESJK4j2+iSGRj7MBsQf1SCwoCTBbLmhXoFAVXXHzNxdY0YX5weiRKqhlK ixS84SDZhNEL9MvY8RWPgA29ojDOXxUA/8Lr4vt/9rYbh6tHH0YQhWaZ/MCBt1lo+7w0 2viKT1sIv/3hXsixTpdXyKuktM9eH3bUzSSK8YptbZKFXT7nMn1sB7LBPqK8AhIzgwkJ llzxrqQnlh9TFF6AKCZm4AD26xlINadeGO1+vZ7KbvoGHyk5YsC+E7/YyMLBn3biU25R NT8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747145225; x=1747750025; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=S0yU+yusUuaSJP2VmKOrYiDsBhgc+QU1Nqy5d0LZQnM=; b=UNfF2B7G8OSXpAn0f3/Di1tNG7qB5wXvUj6Pe0SopUy50BVWpw0E9Dmcj9+oPBaYGa LRIMhDiQfcOnXpWj/LZL/pxPZT2GTMEhuc3uLW6evE+/B4YzKBtWbhYAje03Hz8FUT+d 0Zvm7LjKEGkWAbUOOida9xeN3xwp25pNDvZZDgcZu6KDWlp9Abw12LhQughr2GKoNPMh kj+e4bZauksklXLN2LhQII/Pg4FYdBM8LfTjq8iosdxXsWgbjrY59JmDUXRLwpvIte7f rEDVP+F3sKvYRbu1Bl6/8wzlx8bnfKnyJJRB5YSn2CoUxqZPBQM8tHgpmpchCxuA7S0d jxsw== X-Gm-Message-State: AOJu0Yw/adMP9uROkFc6j5JewzXlZXrewP248ovUZptIKnfkywYHgVW2 rHe167so8ra40NaumiOvPkjMXRCFSD4m2PZxxcgu/5syzC784jOIQlmoG06TD0vvwIDykWnjm0+ LWuNJ4bqZsUcM+sviQfcnk89e9BvPLKH4oLhl X-Gm-Gg: ASbGncvVQVwVxtRK9PCRTxyO1yGiEigP3e6UhvFAPvn67AStPX3TNHTWkffUJmEYtTb +ja5pyQh2Hvdww/3CHfUaSGCP3M4apCxavfEGOtAzu+AbrV02lhnPkESaWZHsEca1B8kiLm7wmD rR6lrXCP9qOYhBOBbCGQCNifkcB1R8RrMRcQ== X-Google-Smtp-Source: AGHT+IHjD8/ZfWHYGP22nYQpbkwTAsY02cw3wfyI5y+gz0SziB4vslMifARvQ480+7z+Z/kszGwsExBwpmkOCj8OTE0= X-Received: by 2002:a05:690c:48c6:b0:6fe:b7ed:9715 with SMTP id 00721157ae682-70a3fa1fdf6mr263709677b3.11.1747145224897; Tue, 13 May 2025 07:07:04 -0700 (PDT) MIME-Version: 1.0 References: <4cbe2e53-0bf3-4a89-bd81-dfb124b4c36e@aklaver.com> In-Reply-To: From: Magnus Hagander Date: Tue, 13 May 2025 16:06:52 +0200 X-Gm-Features: AX0GCFsMCJw77P6XrPw7XsUPOqcrndY8NcgHXRnY3SdPV41dfTh5wNwQBt2ed-M Message-ID: Subject: Re: deb http://apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main 15 To: Andrej Cc: postgresql Forums , Adrian Klaver Content-Type: multipart/alternative; boundary="000000000000805ae0063504f2de" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000805ae0063504f2de Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, May 11, 2025 at 11:23=E2=80=AFPM Andrej w= rote: > Hi Adrian, > > Thank you for the super-quick response! > Just a quick check-back on this: has this issue basically resolve itself by now, or does it still show up? > > We have two clusters of postgres running, and a couple of machines have >> > local postgres databases installed via ansible, using ANXS.postgresql. >> > This has been working fine for years, installing varied versions of >> > postgres, doing upgrades & migrations without a hitch. >> > >> > Since last week we're seeing odd errors which look like they're caused >> > by repo: >> >> May 8th a round of new releases where made: >> >> >> https://www.postgresql.org/about/news/postgresql-175-169-1513-1418-and-1= 321-released-3072/ > > > I see ... but was there anything new in the process of publishing them? > > >> >> > a) W: An error occurred during the signature verification. The >> > repository is not updated and the previous index files will be used. >> GPG >> > error: http://apt.postgresql.org/pub/repos/apt >> > bookworm-pgdg InRelease: >> >> Shouldn't the above be?: >> >> https://apt.postgresql.org/pub/repos/apt/dists/bookworm-pgdg/InRelease > > For browser sessions yes, not inside the sources-file > `/etc/apt/sources.list.d/apt_postgresql_org_pub_repos_apt.list` ... they'= re > structured like this, for example: > > cat apt_postgresql_org_pub_repos_apt.list > deb http://apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main 15 > > >> > b) E: Failed to fetch >> > >> http://apt.postgresql.org/pub/repos/apt/dists/focal-pgdg/main/binary-amd= 64/Packages.bz2 >> < >> http://apt.postgresql.org/pub/repos/apt/dists/focal-pgdg/main/binary-amd= 64/Packages.bz2> >> File has unexpected size (350884 !=3D 350996). Mirror sync in progress?= [IP: >> v.w.x.y[1] 3142] >> > Hashes of expected file: >> > - Filesize:350996 [weak] >> > - >> > SHA256:b946f1cb499ffca9331f532cea373ca5f5d39551fdc156effef354e001a5b86= 5 >> > - SHA1:7aabca4a364ee2b4b891465b02f60d7609b79f8f [weak] >> > - MD5Sum:738420fcc2da36f7728502eb2809aa43 [weak] >> > Release file created at: Mon, 28 Apr 2025 16:16:01 +0000 >> > E: Some index files failed to download. They have been ignored, or old >> > ones used instead. >> > Something weird here. You have bookworm-pgdg in your repository config file, but the error is from focal-pgdg.. Have you somehow ended up with two repos configured? > >> From here: >> >> >> http://apt.postgresql.org/pub/repos/apt/dists/focal-pgdg/main/binary-amd= 64/ >> >> Packages.bz2 09-May-2025 19:58 350884 >> >> Not sure where the Filesize:350996 [weak] and Release file created at: >> Mon, 28 Apr 2025 16:16:01 +0000 is coming from? >> > > Me neither, I'll confess - possibly a version in use that *didn't* receiv= e > an update? > If you still have the issue, or f it reappears, can you please provider the header output from basically a "curl -I " for th different URLs involved at the time of failure? And also note the exact timestamp of when you're doing it, to correlate with logs. --=20 Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000805ae0063504f2de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, May 11, 2025 at 11:23=E2=80=AFPM = Andrej <andrej.groups@gmail.c= om> wrote:
Hi Adrian,

Thank you for the super-quick response!=

Just a quick check-back = on this: has this issue basically resolve itself by now, or does it still s= how up?

=C2=A0
> We have two clusters of postgres running, and a couple of machines hav= e
> local postgres databases installed via ansible, using ANXS.postgresql.=
> This has been working fine for years, installing varied versions of > postgres, doing upgrades & migrations without a hitch.
>
> Since last week we're seeing odd errors which look like they'r= e caused
> by repo:

May 8th a round of new releases where made:

https://ww= w.postgresql.org/about/news/postgresql-175-169-1513-1418-and-1321-released-= 3072/

I see ... but was there anything = new in the process of publishing them?=C2=A0
=C2=A0

> a) W: An error occurred during the signature verification. The
> repository is not updated and the previous index files will be used. G= PG
> error: http://apt.postgresql.org/pub/repos/apt
> <http://apt.postgresql.org/pub/repos/apt> book= worm-pgdg InRelease:

Shouldn't the above be?:

https://apt.postgresql.org/pub= /repos/apt/dists/bookworm-pgdg/InRelease
For browser s= essions yes, not inside the sources-file `/etc/apt/sources.list.d/apt_postg= resql_org_pub_repos_apt.list` ... they're structured like this, for exa= mple:

cat=C2=A0apt_postgr= esql_org_pub_repos_apt.list
deb <= a href=3D"http://apt.postgresql.org/pub/repos/apt/" target=3D"_blank">http:= //apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main 15
<= div>

> b) E: Failed to fetch
> http://a= pt.postgresql.org/pub/repos/apt/dists/focal-pgdg/main/binary-amd64/Packages= .bz2 <= http://apt.postgresql.org/pub/repos/apt/dists/focal-pgdg/main/binary-amd64/= Packages.bz2> =C2=A0File has unexpected size (350884 !=3D 350996). M= irror sync in progress? [IP: v.w.x.y[1] 3142]
>=C2=A0 =C2=A0 =C2=A0Hashes of expected file:
>=C2=A0 =C2=A0 =C2=A0 - Filesize:350996 [weak]
>=C2=A0 =C2=A0 =C2=A0 -
> SHA256:b946f1cb499ffca9331f532cea373ca5f5d39551fdc156effef354e001a5b86= 5
>=C2=A0 =C2=A0 =C2=A0 - SHA1:7aabca4a364ee2b4b891465b02f60d7609b79f8f [w= eak]
>=C2=A0 =C2=A0 =C2=A0 - MD5Sum:738420fcc2da36f7728502eb2809aa43 [weak] >=C2=A0 =C2=A0 =C2=A0Release file created at: Mon, 28 Apr 2025 16:16:01 = +0000
> E: Some index files failed to download. They have been ignored, or old=
> ones used instead.

<= /div>

Something weird here. You have bookworm-pgdg in yo= ur repository config file, but the error is from focal-pgdg.. Have you some= how ended up with two repos configured?

=C2=A0

=C2=A0From here:

http://apt.postgresql.org= /pub/repos/apt/dists/focal-pgdg/main/binary-amd64/

Packages.bz2=C2=A0 =C2=A0 =C2=A0 09-May-2025 19:58=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 350884

Not sure where the Filesize:350996 [weak] and Release file created at:
Mon, 28 Apr 2025 16:16:01 +0000 is coming from?

Me neither, I'll confess - possibly a version in use that *did= n't* receive an update?
<= br>

If you still have the issue, or f it reappears, can you p= lease provider the header output from basically a "curl -I <url>= " for th different URLs involved at the time of failure?=C2=A0

And also note the exact timestamp of when you're doin= g it, to correlate with logs.


--
=C2=A0Magnus Hagander
=C2=A0Me: <= a href=3D"http://www.hagander.net/" target=3D"_blank">https://www.hagander.= net/
=C2=A0Work: https://www.redpill-linpro.com/
--000000000000805ae0063504f2de--