OVH Community, your new community space.

Erreur yum kimsufi centos 7.1 x86_64

24/05/2015, 16h00

impossible d'utiliser la commande yum depuis un kimsufi KS-2. J'obtient l'erreur ci-dessous :
[root@mail-server ~]# yum clean all
[root@mail-server ~]# yum update
Modules complémentaires chargés*: fastestmirror

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

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

Cannot find a valid baseurl for repo: base/7/x86_64
Après investigation il semble que le retour de l'url ci-dessous ne soit pas bon depuis le kimsufi. Par contre, c'est ok depuis chez moi (Free ADSL). Peut-etre un problème de DNS OVH ?

KO Depuis le Kimsufi :
[root@mail-server ~]# curl ""
Invalid release
[root@mail-server ~]#
OK Depuis chez moi (Free ADSL)
MacBook-Air-de-John:~ jjohn$ curl ""
MacBook-Air-de-John:~ jjohn$
J'ai le même problème sur le kimsufi d'un ami après avoir cleaner le cache yum (yum clean all). Le problème n'est donc pas lié à ma config d'autant que je teste sur un kimsufi a peine sortie d'installation.

Une idée ?