pglogical repo fails for amazon linux

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

pglogical repo fails for amazon linux

S Bob

I've done the following on an amazon EC2 VM running amazon linux:

1) created the postgresql repo for V12:

# tee /etc/yum.repos.d/pgdg.repo<<EOF
name=PostgreSQL 12 for RHEL/CentOS 7 - x86_64

2) Ran the pglogical curl command:

# curl 
| bash

3) attempted to install the pglogical package via yum:

# yum install postgresql12-pglogical

Steps 1 and 2 were successful, step 3 produces the output below, anyone
know why? am I doing something wrong? These exact same steps work on a
local Linux VM (Not amazon).

Thanks in advance

Step 3 output:

# yum install postgresql12-pglogical
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd 
[Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.

  One of the configured repositories failed (2ndQuadrant packages (PG12)
for 2 - x86_64),
  and yum doesn't have enough cached data to continue. At this point the
  safe thing yum can do is fail. There are a few ways to work "fix" this:

      1. Contact the upstream for the repository and get them to fix the

      2. Reconfigure the baseurl/etc. for the repository, to point to a
         upstream. This is most often useful if you are using a newer
         distribution release than is supported by the repository (and the
         packages for the previous distribution release still work).

      3. Run the command with the repository temporarily disabled
             yum --disablerepo=2ndquadrant-dl-default-release-pg12 ...

      4. Disable the repository permanently, so yum won't use it by
default. Yum
         will then just ignore the repository until you permanently
enable it
         again or use --enablerepo for temporary usage:

             yum-config-manager --disable
             subscription-manager repos

      5. Configure the failing repository to be skipped, if it is
         Note that yum will try to contact the repo. when it runs most
         so will have to try and fail each time (and thus. yum will be
be much
         slower). If it is a very temporary problem though, this is
often a nice

             yum-config-manager --save

failure: repodata/repomd.xml from 2ndquadrant-dl-default-release-pg12:
[Errno 256] No more mirrors to try. 
[Errno 14] HTTPS Error 404 - Not Found