public inbox for [email protected]  
help / color / mirror / Atom feed
From: Vojtěch Dušátko <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Christoph Berg <[email protected]>
Cc: [email protected]
Subject: Re: Not working Bookworm-pgdg repo
Date: Wed, 18 Feb 2026 21:53:52 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<CABUevEyrnw-AByKGmDuSUfFak9p9c0pnshj726djjLLoF2_k3w@mail.gmail.com>
	<[email protected]>
	<CABUevEzL2eqpagv3i+GfRgfVdhDdWOxbX3NZjeDo5SGNaXs93A@mail.gmail.com>
	<[email protected]>

Now I can confirm the time exactly ...

[130] [21:52:49] root@psql15-test-is-01:~# date
Wed Feb 18 09:52:52 PM CET 2026
[21:52:52] root@psql15-test-is-01:~# apt update
Hit:1http://ftp.cz.debian.org/debian bookworm InRelease
Hit:2http://ftp.cz.debian.org/debian bookworm-updates InRelease
Hit:3http://security.debian.org/debian-security bookworm-security InRelease
Get:4http://apt.postgresql.org/pub/repos/apt bookworm-pgdg InRelease [107 kB]
Hit:5http://haproxy.debian.net bookworm-backports-2.6 InRelease
Hit:6http://haproxy.debian.net bullseye-backports-2.6 InRelease
Get:7http://apt.postgresql.org/pub/repos/apt bookworm-pgdg/main amd64 Packages [408 kB]
Err:7http://apt.postgresql.org/pub/repos/apt bookworm-pgdg/main amd64 Packages
   File has unexpected size (408676 != 407760). Mirror sync in progress? [IP: 146.75.123.52 80]
   Hashes of expected file:
    - Filesize:407760 [weak]
    - SHA256:d2dfe5e2cfb90c2849616207f72afb996dc177533b6e9acd4269b0fe18982c24
    - SHA1:c1af37094108982f088408b65755f1d7d396d930 [weak]
    - MD5Sum:24738e12adcb21b013eaeccb37e4e1d8 [weak]
   Release file created at: Thu, 12 Feb 2026 11:13:19 +0000
Reading package lists... Done
E: Failed to fetchhttp://apt.postgresql.org/pub/repos/apt/dists/bookworm-pgdg/main/binary-amd64/Packages.bz2  File has unexpected size (408676 != 407760). Mirror sync in progress? [IP: 146.75.123.52 80]
    Hashes of expected file:
     - Filesize:407760 [weak]
     - SHA256:d2dfe5e2cfb90c2849616207f72afb996dc177533b6e9acd4269b0fe18982c24
     - SHA1:c1af37094108982f088408b65755f1d7d396d930 [weak]
     - MD5Sum:24738e12adcb21b013eaeccb37e4e1d8 [weak]
    Release file created at: Thu, 12 Feb 2026 11:13:19 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
[100] [21:52:55] root@psql15-test-is-01:~#


Vojtěch Dušátko

On 18/02/26 15:42, Vojtěch Dušátko wrote:
> First I saw this error was at some machine (same external IP) yesterday.
> I was facing the issue today but not sure - I think that the last 
> error was right before I sent an email. I'm not 100% sure, NGL.
>
> ---
> Vojtěch Dušátko
> On Feb 18, 2026, at 15:27, Magnus Hagander <[email protected]> wrote:
>
>     Hi!
>
>     Nope, nothing was done :(
>
>     Do you happen to have a record of the time you first saw the problem?
>
>     I can see that the file you got has been in the closest cache for
>     a bit over two hours. When you sent your report in an hour ago,
>     was that right when you had the problem, or could there have been
>     time between when you got the error out and when you sent the
>     email, and that the actual attempt could have been more than 2
>     hours ago?
>
>     Thanks!
>
>     //Magnus
>
>
>     On Wed, 18 Feb 2026 at 15:23, Vojtěch Dušátko
>     <[email protected]> wrote:
>
>         Hello,
>
>         I can't see the problem anymore, right now.
>
>         If you cleaned up something, thank you.
>
>         If not - some weird behavior happened. I have multiple psql
>         clusters hidden under same public IP (NAT) and now I can't see
>         the same behavior at any node of the farm.
>
>         Thank you.
>
>         Vojtěch Dušátko
>
>         On 18/02/26 15:17, Magnus Hagander wrote:
>>
>>
>>         On Wed, 18 Feb 2026 at 14:41, Christoph Berg
>>         <[email protected]> wrote:
>>
>>             Re: Vojtěch Dušátko
>>             >   Release file created at: Thu, 12 Feb 2026 11:13:19 +0000
>>
>>             We've had several reports about this problems, afaict all
>>             with this
>>             timestamp. The actual file is newer.
>>
>>             The cloud CDN in front is probably caching bad things
>>             there...
>>
>>             Maybe the PG infra admins could check?
>>
>>
>>         Hi!
>>
>>         This problem is still ongoing, right? Could you run:
>>
>>         curl -D -
>>         http://apt.postgresql.org/pub/repos/apt/dists/bookworm-pgdg/InRelease
>>         > curled_InRelease
>>         curl -D -
>>         http://apt.postgresql.org/pub/repos/apt/dists/bookworm-pgdg/main/binary-amd64/Packages
>>         > curled_Packages
>>         curl -D -
>>         http://apt.postgresql.org/pub/repos/apt/dists/bookworm-pgdg/main/binary-amd64/Packages.bz2
>>         > curled_Packages.bz2
>>
>>         And send those two files?
>>
>>         (And it has to be run from the same machine you run apt on,
>>         since the CDN might direct other machines to other nodes)
>>
>>         Thanks!
>>
>>         //Magnus
>>
>

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Not working Bookworm-pgdg repo
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox