MRatWork Forum by Mustafa Ramadhan
Language Specific Discussions => Indonesia Users => Topic started by: amudy17 on 2016-12-22, 12:51:54
-
Pak Mr,
Tolong bantu ada error fresh install ..
[root@ip-172-31-54-214 /]# yum update mratwork-* -y
Loaded plugins: amazon-id, rhui-lb, search-disabled-repos
mratwork-epel/7Server/x86_64/metalink | 40 kB 00:00
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7Server&arch=x86_64 error was
No repomd file
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
File /var/cache/yum/x86_64/7Server/mratwork-epel/metalink.xml does not exist
please advise
-
Masih belum bisa di CentOS 7. Sebaiknya di CentOS 6.