CentOS - 7.1 - トラブルシュート - epel にアクセスできない?

1. 概要

1. 概要

 あるサイトで、epel からインストールできないと話題になっていて。  やってみたら確かに動かない。  ってか、そもそもリストできない・・・?

$ yum list
読み込んだプラグイン:fastestmirror, langpacks
base                                                                                                       | 3.6 kB  00:00:00
epel/x86_64/metalink                                                                                       | 4.1 kB  00:00:00
epel                                                                                                       | 4.7 kB  00:00:00
extras                                                                                                     | 3.4 kB  00:00:00
updates                                                                                                    | 3.4 kB  00:00:00
Loading mirror speeds from cached hostfile
 * base: mirror.vodien.com
 * epel: ftp.yz.yamagata-u.ac.jp
 * extras: mirror.vodien.com
 * updates: ftp.iij.ad.jp

 One of the configured repositories failed (不明),
 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 <repoid>

     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

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

file is encrypted or is not a database