CentOS 7 Cannot find a valid baseurl for repo: EA4/$releasever/x86_64

[The Old Man]

Hello,

CENTOS 7.9 virtuozzo [vps71163] v98.0.6 Load Averages: 0.44 0.68 0.89

I'm trying to re-install Ghostscript but in the default /user/local bin directory as apps can't seem to find it where Centos 7.9 has it, but keep getting this error message:

Cannot find a valid baseurl for repo: EA4/$releasever/x86_64


Tried ping Google.com and that's fine, then yum clean all, yum makecache and yum update.

 yum install --nogpgcheck --installroot=/usr/local ghostscript
Loaded plugins: fastestmirror, tsflags, universal-hooks
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c$releasever-x86_64-mirrorlist error was
14: HTTP Error 404 - Not Found


One of the configured repositories failed (Unknown),
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=<repoid> ...

     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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     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=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4/$releasever/x86_64

Any advice appreciated! Thank you.

 

[cPRex]

Hey there! The way it is naming the repo file seems odd to me. Can you send me the output of this command?

ls -lah /etc/yum.repos.d

 

[The Old Man]

Hello!

Here is the output...

ls -lah /etc/yum.repos.d
total 216K
drwxr-xr-x   2 root root 4.0K Sep 10 18:29 ./
drwxr-xr-x 105 root root  20K Sep 11 01:30 ../
-rw-r--r--   1 root root 1.7K Sep 10 18:27 CentOS-Base.repo
-rw-r--r--   1 root root 1.3K Nov 23  2020 CentOS-CR.repo
-rw-r--r--   1 root root  649 Nov 23  2020 CentOS-Debuginfo.repo
-rw-r--r--   1 root root  314 Nov 23  2020 CentOS-fasttrack.repo
-rw-r--r--   1 root root  630 Nov 23  2020 CentOS-Media.repo
-rw-r--r--   1 root root 1.3K Nov 23  2020 CentOS-Sources.repo
-rw-r--r--   1 root root 8.4K Nov 23  2020 CentOS-Vault.repo
-rw-r--r--   1 root root  616 Nov 23  2020 CentOS-x86_64-kernel.repo
-rw-r--r--   1 root root  257 Jul 18  2019 cPAddons.repo
-rw-------   1 root root  241 Sep 10 06:14 cpanel-plugins.repo
-rw-r--r--   1 root root  204 Aug  7  2015 EA4.repo
-rw-r--r--   1 root root 1.1K Aug 28 06:34 epel.repo
-rw-r--r--   1 root root 1.2K Oct 31  2020 epel-testing.repo
-rw-r--r--   1 root root  122 Sep 26  2016 IMH-Base-Ded.repo
-rw-r--r--   1 root root  218 Aug 26 20:17 imunify360.repo
-rw-r--r--   1 root root  234 Aug 26 20:17 imunify360-testing.repo
-rw-r--r--   1 root root 2.2K Aug 23 14:49 imunify-rollout.repo
-rw-r--r--   1 root root  267 Aug 17 02:38 MariaDB103.repo
-rw-------   1 root root  144 Aug 17 02:38 MariaDB105.repo
-rw-r--r--   1 root root  271 Oct 27  2020 MariaDB.repo
-rw-r--r--   1 root root  780 Aug 16 20:32 percona-original-release.repo
-rw-r--r--   1 root root  301 Aug 16 20:32 percona-prel-release.repo
-rw-r--r--   1 root root  528 Jul 24 06:55 percona-tools-release.repo
-rw-r--r--   1 root root  531 Jul  3 17:58 powerdns-rec-45.repo
-rw-r--r--   1 root root  446 Sep  2 10:35 remi-glpi91.repo
-rw-r--r--   1 root root  446 Sep  2 10:35 remi-glpi92.repo
-rw-r--r--   1 root root  446 Sep  2 10:35 remi-glpi93.repo
-rw-r--r--   1 root root  446 Sep  2 10:35 remi-glpi94.repo
-rw-r--r--   1 root root  855 Sep  2 10:35 remi-modular.repo
-rw-r--r--   1 root root  456 Sep  2 10:35 remi-php54.repo
-rw-r--r--   1 root root 1.3K Sep  2 10:35 remi-php70.repo
-rw-r--r--   1 root root 1.3K Sep  2 10:35 remi-php71.repo
-rw-r--r--   1 root root 1.3K Sep  2 10:35 remi-php72.repo
-rw-r--r--   1 root root 1.3K Sep  2 10:35 remi-php73.repo
-rw-r--r--   1 root root 1.3K Jul 23 20:37 remi-php74.repo
-rw-r--r--   1 root root 1.3K Jul 23 20:37 remi-php80.repo
-rw-r--r--   1 root root 1.3K Sep  2 10:35 remi-php81.repo
-rw-r--r--   1 root root  23K Jan  4  2021 remi-release-7.rpm
-rw-r--r--   1 root root 2.6K Jul 23 20:38 remi.repo
-rw-r--r--   1 root root  750 Sep  2 10:35 remi-safe.repo
-rw-r--r--   1 root root  286 Dec 18  2020 wp-toolkit-cpanel.repo

 

[RoseHosting]

Please post the content of the

/etc/yum.repos.d/EA4.repo

Also, what is the output of

curl -I http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist

 

[The Old Man]

Please post the content of the

/etc/yum.repos.d/EA4.repo

EA4]
name=EA4 ( EasyApache 4 )
mirrorlist=http://httpupdate.cpanel.net/ea4-c$releasever-$basearch-mirrorlist
gpgcheck=1
gpgkey=https://securedownloads.cpanel.net/cPanelPublicRPMKey.asc
enabled=1
cost=50

Also, what is the output of

curl -I http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist

curl -I http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist
HTTP/1.1 200 OK
Date: Sat, 11 Sep 2021 19:40:49 GMT
Server: Apache
Last-Modified: Sat, 11 Sep 2021 19:38:08 GMT
Vary: Accept-Encoding
Cache-Control: max-age=300
X-Backend-IP: 208.74.123.6
X-Varnish: 47159367 46146104
Age: 114
Via: 1.1 varnish-v4
ETag: W/"47c-5cbbd5f1b8478-gzip"
X-Cache: HIT
X-VCL-Code-Version: 2.10
Connection: keep-alive

Thanks!

 

[cPJustinD]

Hi there! I've compared the output you provided to the repo information on my own test server, and the only difference I noticed is that you have some additional repositories. However, I could not determine any differences in the EA4 repo configuration between yours and my test server. I was also able to replicate the error.

I think it would be best to open a support ticket so that our analysts can review the issue more thoroughly and determine what exactly is occurring. You can submit a support request using the "Submit a ticket" link in my signature below. Please be sure to link this thread when opening the ticket and provide the ticket number here so that we can track the issue appropriately. If possible, please post the resolution on this thread as it may help other community members with similar issues.

 

[The Old Man]

Thank you for looking into this and doing some testing, appreciate it. I'm an end user so I don't think it will let me.

I just tried the command again and same results.

yum install --nogpgcheck --installroot=/usr/local ghostscript

So I retried:

yum install --installroot=/usr/local ghostscript

and the error message was slightly different in that it now mentions Wordpress toolkit, which I've never used or intended to use. I do have existing Wordpress installations.

root@vps [~]# yum install --installroot=/usr/local ghostscript
Loaded plugins: fastestmirror, tsflags, universal-hooks

You have enabled checking of packages via GPG keys. This is a good thing.
However, you do not have any GPG public keys installed. You need to download
the keys for packages you wish to install and install them.
You can do that by running the command:
    rpm --import public.gpg.key


Alternatively you can specify the url to the key you would like to use
for a repository in the 'gpgkey' option in a repository section and yum
will install it for you.

For more information contact your distribution or package provider.

Problem repository: wp-toolkit-cpanel
root@vps  [~]#

I was using the command with the nopgp flag because of the mentioned issue with PGP.

Thank you anyway, much appreciated.

 

[cPJustinD]

Hello again. I understand that you are an end-user, however, as long as you have root access to the server we should still be able to review the issue via ticket.



I still believe the best step moving forward would be to open a ticket with our Technical Support team so that we can access the server and take a closer look. As I mentioned previously, you can submit a support request using the "Submit a ticket" link in my signature below. Please be sure to link this thread when opening the ticket and provide the ticket number here so that we can track the issue appropriately. If possible, please post the resolution on this thread as it may help other community members with similar issues.

 

[000]

in 2023 we have same problem:

[root@api ~]# yum -y update
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known"

One of the configured repositories failed (Unknown),
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=<repoid> ...

     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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     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=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: EA4-c7/7/x86_64
[root@api ~]#

following yours recommendations:

[root@api ~]# cat /etc/yum.repos.d/EA4.repo
[EA4-c$releasever]
name=EA4 ( EasyApache 4 - c$releasever )
mirrorlist=http://httpupdate.cpanel.net/ea4-c$releasever-$basearch-mirrorlist
gpgcheck=1
gpgkey=https://securedownloads.cpanel.net/cPanelPublicPkgKey.asc
enabled=1
cost=50
[root@api ~]#

... what we can do in 2023 ?


our real problem is:

 

[quietFinn]

Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was
14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known"

You don't have the "same problem", your problem is that httpupdate.cpanel.net does not resolve.

what do you get if you do:
nslookup httpupdate.cpanel.net

 

[000]

... what do you get if you do:nslookup httpupdate.cpanel.net

thanks master, this is result:

[root@api ~]#  nslookup httpupdate.cpanel.net
;; connection timed out; no servers could be reached

[root@api ~]#

 

[quietFinn]

I think there is something wrong with networking in your server,
Maybe you should open a ticket

 

[000]

I think there is something wrong with networking in your server,
Maybe you should open a ticket

thanks by your time