Failure: repodata/repomd.xml please help

1

how should the following be coded so it work so I don’t keep getting any errors. please the exact baseurl.

thanks
lenard

[root@server1 ~]# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)

[Kaltura]
name = Kaltura Server
baseurl = http://installrepo.kaltura.org/releases/rhel7/RPMS/$basearch/
gpgkey = http://installrepo.kaltura.org/releases/RPM-GPG-KEY-kaltura
gpgcheck = 1
enabled = 1

[Kaltura-noarch]
name = Kaltura Server arch independent
baseurl = http://installrepo.kaltura.org/releases/rhel7/RPMS/$basearch/
gpgkey = http://installrepo.kaltura.org/releases/RPM-GPG-KEY-kaltura
gpgcheck = 1
enabled = 1

[root@server ~]# yum install kaltura-server
Loaded plugins: fastestmirror, universal-hooks
Determining fastest mirrors
epel/x86_64/metalink | 17 kB 00:00:00

https://wiki.centos.org/yum-errors

If above article doesn’t help to resolve this issue please use https://bugs.centos.org/.

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

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

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

failure: repodata/repomd.xml from Kaltura: [Errno 256] No more mirrors to try.
http://installrepo.origin.kaltura.org/releases/rhel7/7/RPMS/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
[root@server ~]#

[root@server ~]# curl -I -v http://installrepo.origin.kaltura.org/releases/latest/RPMS/noarch/ropodata/repomd.xml

HEAD /releases/latest/RPMS/noarch/ropodata/repomd.xml HTTP/1.1
User-Agent: curl/7.29.0
Host: installrepo.origin.kaltura.org
Accept: /

< HTTP/1.1 301 Moved Permanently
HTTP/1.1 301 Moved Permanently
< Date: Wed, 19 Jun 2019 16:46:26 GMT
Date: Wed, 19 Jun 2019 16:46:26 GMT
< Server: Apache
Server: Apache
< Location: http://installrepo.origin.kaltura.org/releases/15.0.0/RPMS/noarch/ropodata/repomd.xml
Location: http://installrepo.origin.kaltura.org/releases/15.0.0/RPMS/noarch/ropodata/repomd.xml
< Connection: close
Connection: close
< Content-Type: text/html; charset=iso-8859-1
Content-Type: text/html; charset=iso-8859-1

<

  • Closing connection 0
2

Hello @lblanks240,

Your kaltura.repo file contains incorrect URLs.

The kaltura-release package creates that file and you can (and should) update it to the latest version.
This is covered here:

The file should contain the following lines:

[Kaltura]
name = Kaltura Server
baseurl = http://installrepo.kaltura.org/releases/latest/$releasever/RPMS/$basearch/
gpgkey = http://installrepo.kaltura.org/releases/RPM-GPG-KEY-kaltura
gpgcheck = 1
enabled = 1

[Kaltura-noarch]
name = Kaltura Server arch independent
baseurl = http://installrepo.kaltura.org/releases/latest/$releasever/RPMS/noarch
gpgkey = http://installrepo.kaltura.org/releases/RPM-GPG-KEY-kaltura
gpgcheck = 1
enabled = 1