Welcome to Centmin Mod Community
Register Now

PostgreSQL won't install

Discussion in 'Bug Reports' started by mrkip, Oct 25, 2021.

  1. mrkip

    mrkip Premium Member Premium Member

    17
    13
    3
    Jan 29, 2019
    Ratings:
    +18
    Local Time:
    3:25 AM
    Think I've found an issue with PostgreSQL installation process.

    My custom.conf is the following:
    Code:
    POSTGRESQL='y'
    LETSENCRYPT_DETECT='y'
    And I've then proceeded to recompile PHP.


    The process seems to halt when the script tries to import the GPG keys. So I think it's a repo issue.

    Here's some further info:
    Code:
    warning: /svr-setup/pgdg-redhat-repo-latest.noarch.rpm: Header V4 DSA/SHA1 Signature, key ID 442df0f8: NOKEY
    Preparing...                          ########################################
    Updating / installing...
    pgdg-redhat-repo-42.0-20              ########################################
    ls: cannot access /etc/yum.repos.d/pgdg-13-redhat.repo: No such file or directory
    cat: /etc/yum.repos.d/pgdg-13-redhat.repo: No such file or directory
    
    Loaded plugins: fastestmirror, versionlock
    Loading mirror speeds from cached hostfile
     * base: mirror.netsite.dk
     * centos-sclo-rh: mirrors.xtom.de
     * centos-sclo-sclo: mirror.netsite.dk
     * epel: mirrors.coreix.net
     * extras: mirror.netsite.dk
     * updates: mirror.23m.com
    Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG
    Importing GPG key 0x442DF0F8:
     Userid     : "PostgreSQL RPM Building Project <pgsql-pkg-yum@postgresql.org>"
     Fingerprint: 68c9 e2b9 1a37 d136 fe74 d176 1f16 d2e1 442d f0f8
     Package    : pgdg-redhat-repo-42.0-20.noarch (installed)
     From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG
    
    https://download.postgresql.org/pub/repos/yum/common/redhat/rhel-7-x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo pgdg-common
    Trying other mirror.
    
    
     One of the configured repositories failed (PostgreSQL common RPMs for RHEL/CentOS 7 - x86_64),
     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=pgdg-common ...
    
         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 pgdg-common
            or
                subscription-manager repos --disable=pgdg-common
    
         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=pgdg-common.skip_if_unavailable=true
    
    failure: repodata/repomd.xml from pgdg-common: [Errno 256] No more mirrors to try.
    https://download.postgresql.org/pub/repos/yum/common/redhat/rhel-7-x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo pgdg-common
    Is this ok [y/N]:
    real    8m22.416s
    user    0m0.366s
    sys     0m0.109s
    I'm currently playing about with this on a test VPS. So if you want me to try anything out feel free to make suggestions. I'm not too fussed about borking my server and having to reinstall it again.
     
  2. eva2000

    eva2000 Administrator Staff Member

    47,498
    10,769
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +16,742
    Local Time:
    1:25 PM
    Nginx 1.19.x
    MariaDB 5.5/10.x
  3. mrkip

    mrkip Premium Member Premium Member

    17
    13
    3
    Jan 29, 2019
    Ratings:
    +18
    Local Time:
    3:25 AM
    No worries mate:) I understand you've got a lot on your plate ATM, and I'm happy to wait for a fix.

    PS: I wish your mum a speedy recovery.

    Best,