One of the configured repositories failed （Kaltura Server arch independent). and yum donesn’t have enough cached date to continue .At this point the only safe thing yum can do is fail.
…
One of the configured repositories failed (Extra Packages for Enterprise Linux 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. Disable the repository, 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 epel
4. 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=epel.skip_if_unavailable=true
updates: mirrors.163.com
Kaltura-noarch/primary_db | 48 kB 00:01
Resolving Dependencies
–> Running transaction check
—> Package kaltura-release.noarch 0:11.8.0-1 will be updated
—> Package kaltura-release.noarch 0:12.4.0-1 will be an update
–> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
Updating:
kaltura-release noarch 12.4.0-1 Kaltura-noarch 9.3 k
Transaction Summary
Upgrade 1 Package
Total download size: 9.3 k
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for Kaltura-noarch
warning: /var/cache/yum/x86_64/7/Kaltura-noarch/packages/kaltura-release-12.4.0-1.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID ba443ef2: NOKEY
Public key for kaltura-release-12.4.0-1.noarch.rpm is not installed
kaltura-release-12.4.0-1.noarch.rpm | 9.3 kB 00:01
Retrieving key from http://installrepo.kaltura.org/releases/RPM-GPG-KEY-kaltura
Importing GPG key 0xBA443EF2:
Userid : "Kaltura (for RPMs.) community@kaltura.com"
Fingerprint: 1688 ff2e af8e d7b6 ecba a36b b194 baa5 ba44 3ef2
From : http://installrepo.kaltura.org/releases/RPM-GPG-KEY-kaltura
Is this ok [y/N]: y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Warning: RPMDB altered outside of yum.
Updating : kaltura-release-12.4.0-1.noarch 1/2
Cleanup : kaltura-release-11.8.0-1.noarch 2/2
Verifying : kaltura-release-12.4.0-1.noarch 1/2
Verifying : kaltura-release-11.8.0-1.noarch 2/2
y
Updated:
kaltura-release.noarch 0:12.4.0-1
Complete!
[root@localhost wy]# yum clean all
Loaded plugins: fastestmirror, langpacks
Cleaning repos: Kaltura Kaltura-noarch base epel extras updates
Cleaning up everything
Cleaning up list of fastest mirrors
[root@localhost wy]# yum install kaltura-server
Loaded plugins: fastestmirror, langpacks
Kaltura | 2.9 kB 00:00 http://installrepo.kaltura.org/releases/latest/RPMS/noarch/repodata/repomd.xml: [Errno 14] curl#56 - "Recv failure: Connection reset by peer"
Trying other mirror.
One of the configured repositories failed (Kaltura Server arch independent),
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. Disable the repository, 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-noarch
4. 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-noarch.skip_if_unavailable=true
good new. I made it. the problem is the broken links with some files. I manually downloaded then and install them and it works.
thank you for you support