Re: Please help: pgAdmin 4 on Amazon Linux 2

Hi,

Amazon Linux is not compatible with RHEL the way CentOS is and it's not a
supported platform for the RPM installation:
https://www.pgadmin.org/download/pgadmin-4-rpm/

The repo configuration probably uses some variables to create the download
URLs and because the versions don't match, it results in a 404. You may
have some luck downloading and installing the RPM directly, but you'll
likely want to take a look at other installation methods on the page I
linked if you want to install pgAdmin on Amazon Linux.

On Fri, Aug 27, 2021 at 5:34 PM Blake McBride <blake1024(at)gmail(dot)com> wrote:

> Greetings,
>
> I am trying to install pgAdmin 4 on Amazon Linux 2. PostgreSQL is already
> installed and working fine. I believe Amazon Linux 2 is based on RedHat.
>
> I am doing the following:
>
> [root(at)a-1lxumlkkw4mu4 ~]# rpm -i
> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/yum/pgadmin4-redhat-repo-2-1.noarch.rpm
> warning: /var/tmp/rpm-tmp.ZEygli: Header V3 RSA/SHA256 Signature, key ID
> 210976f2: NOKEY
> [root(at)a-1lxumlkkw4mu4 ~]# yum install pgadmin4
> Loaded plugins: amzn_workspaces_filter_updates, halt_os_update_check,
> priorities, update-motd
> amzn2-core
> | 3.7 kB 00:00:00
>
> amzn2extra-GraphicsMagick1.3
> | 3.0 kB 00:00:00
>
> amzn2extra-docker
> | 3.0 kB 00:00:00
>
> amzn2extra-epel
> | 3.0 kB 00:00:00
>
> amzn2extra-gimp
> | 1.3 kB 00:00:00
>
> amzn2extra-libreoffice
> | 3.0 kB 00:00:00
>
> amzn2extra-mate-desktop1.x
> | 3.0 kB 00:00:00
>
> epel/x86_64/metalink
> | 15 kB 00:00:00
>
> firefox
> | 2.2 kB 00:00:00
>
> google-chrome
> | 1.3 kB 00:00:00
>
>
> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/yum/redhat/rhel-2-x86_64/repodata/repomd.xml:
> [Errno 14] HTTPS Error 404 - Not Found
> Trying other mirror.
>
>
> One of the configured repositories failed (pgadmin4),
> and yum doesn't have enough cached data to continue. At this point the
> only
> 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
> problem.
>
> 2. Reconfigure the baseurl/etc. for the repository, to point to a
> working
> 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=pgAdmin4 ...
>
> 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 pgAdmin4
> or
> subscription-manager repos --disable=pgAdmin4
>
> 5. Configure the failing repository to be skipped, if it is
> unavailable.
> Note that yum will try to contact the repo. when it runs most
> commands,
> 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
> compromise:
>
> yum-config-manager --save
> --setopt=pgAdmin4.skip_if_unavailable=true
>
> failure: repodata/repomd.xml from pgAdmin4: [Errno 256] No more mirrors to
> try.
>
> https://ftp.postgresql.org/pub/pgadmin/pgadmin4/yum/redhat/rhel-2-x86_64/repodata/repomd.xml:
> [Errno 14] HTTPS Error 404 - Not Found
> [root(at)a-1lxumlkkw4mu4 ~]#
>
>
> I have no idea how to fix this. Any help would sure be appreciated.
>
> Blake McBride
>
>

--
Tiemen Ruiten
Infrastructure Engineer