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:
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: Splitting up /var/lib/apt/lists/partial/apt.postgresql.org_pub_repos_apt_dists_bookworm-pgdg_InRelease into data and signature failed
W: Failed to fetch http://apt.postgresql.org/pub/repos/apt/dists/bookworm-pgdg/InRelease Splitting up /var/lib/apt/lists/partial/apt.postgresql.org_pub_repos_apt_dists_bookworm-pgdg_InRelease into data and signature failed W: Some index files failed to download. They have been ignored, or old ones used instead.--
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.
[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 when using a browser.
Cheers,
Andrej
Please don't top post, and don't use HTML e-Mail :} Make your quotes concise.
