Thread: Re: deb http://apt.postgresql.org/pub/repos/apt/ bookworm-pgdg main 15

On 5/11/25 13:59, Andrej wrote:
> Hi,
> 
> 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-1321-released-3072/

> 
> 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 
> <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


> b) E: Failed to fetch 
> http://apt.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> File has unexpected size
(350884!= 350996). Mirror sync in progress? [IP: v.w.x.y[1] 3142]
 
>     Hashes of expected file:
>      - Filesize:350996 [weak]
>      - 
> SHA256:b946f1cb499ffca9331f532cea373ca5f5d39551fdc156effef354e001a5b865
>      - 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.

 From here:

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

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?

> 
> [1] v.w.x.y  - we use an apt-cacher-ng to proxy package installations to 
> be a good citizen and not pummel upstream machines (not just postgres, 
> but both Ubuntu and Debian as well). I have confirmed that the content 
> on the cacher is identical to what I see on apt.postgresql.org 
> <http://apt.postgresql.org> when using a browser.
> 
> 
> 
> Cheers,
> Andrej
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com




Hi Adrian,

Thank you for the super-quick response!


 
> 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-1321-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
> <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


> b) E: Failed to fetch
> http://apt.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>  File has unexpected size (350884 != 350996). Mirror sync in progress? [IP: v.w.x.y[1] 3142]
>     Hashes of expected file:
>      - Filesize:350996 [weak]
>      -
> SHA256:b946f1cb499ffca9331f532cea373ca5f5d39551fdc156effef354e001a5b865
>      - 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.

 From here:

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

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* receive an update?
 
Cheers,
Andrej


--
Please don't top post, and don't use HTML e-Mail :}  Make your quotes concise.

http://www.georgedillon.com/web/html_email_is_evil.shtml
http://www.catb.org/jargon/html/email-style.html
On Sun, May 11, 2025 at 11:23 PM Andrej <andrej.groups@gmail.com> 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 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-1321-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
> <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


> b) E: Failed to fetch
> http://apt.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>  File has unexpected size (350884 != 350996). Mirror sync in progress? [IP: v.w.x.y[1] 3142]
>     Hashes of expected file:
>      - Filesize:350996 [weak]
>      -
> SHA256:b946f1cb499ffca9331f532cea373ca5f5d39551fdc156effef354e001a5b865
>      - 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-amd64/

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* receive an update?


If you still have the issue, or f it reappears, can you please provider the header output from basically a "curl -I <url>" 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.


--


On Wed, 14 May 2025 at 02:07, Magnus Hagander <magnus@hagander.net> wrote:

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?
Hi Magnus, 

thank you for chiming in. The answer is: -ish.
 
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?
Well ... we're currently in the process of migrating our fleet from Ubuntu to Debian, so we have both atm. The cluster servers are already on Debian, some of the stand-alone machines (special hosts w/ local database) are still Ubuntu.
 
The problem seems to go away when I change the sources list to utilise https:// instead of the previous default, http://
 
Cheers,
Andrej

--
Please don't top post, and don't use HTML e-Mail :}  Make your quotes concise.

http://www.georgedillon.com/web/html_email_is_evil.shtml
http://www.catb.org/jargon/html/email-style.html