¿Por qué está tratando de atravesar un proxy y otros comportamientos extraños?

De vez en cuando configuro un proxy de túnel SSH para que parezca que estoy usando Internet desde otra location. Lo configuré con:

ssh -D 8080 <remote host> 

y utilice el cuadro de dialog Configuración de networking del shell gnome para configurar el proxy en http://localhost:8080 .

Actualmente, el proxy está configurado en Ninguno y mi connection ssh está desconectada.

Mi navigation por internet está funcionando bien. Sin embargo, no puedo usar yum :

 [root@Eiger yum.repos.d]# yum update Loaded plugins: langpacks, refresh-packagekit http://linuxdownload.adobe.com/linux/x86_64/repodata/repomd.xml: [Errno 14] curl #7 - "Failed connect to localhost:8080; Connection refused" Trying other mirror. <repeated 9 more times> One of the configunetworking repositories failed (Adobe Systems Incorporated), 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 adobe-linux-x86_64 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=adobe-linux-x86_64.skip_if_unavailable=true failure: repodata/repomd.xml from adobe-linux-x86_64: [Errno 256] No more mirrors to try. http://linuxdownload.adobe.com/linux/x86_64/repodata/repomd.xml: [Errno 14] curl #7 - "Failed connect to localhost:8080; Connection refused" <repeated 9 more times> 

Si desactivo el repository de adobe-linux , simplemente dice:

 [root@Eiger yum.repos.d]# yum update Loaded plugins: langpacks, refresh-packagekit One of the configunetworking 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. 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 compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot retrieve metalink for repository: fedora/19/x86_64. Please verify its path and try again 

Es extraño que no sepa el nombre del repository que está fallando por segunda vez. También es extraño que no pruebe ninguno de los otros repositorys que he configurado (fedora, fedora-updates, google-chrome, google-talkplugin, insync, intellinuxgraphics, rpmfusion-free, rpmfusion-free-updates, rpmfusion-nonfree , rpmfusion-nonfree-updates).

Esto ha estado funcionando durante más de un año y no he tocado /etc/yum* .


Puse mi computadora a dormir y la desperté un día después. Ahora todo funciona normalmente. No tengo ninguna explicación para el comportamiento visto ayer, pero ya no puedo reproducirlo.

La eliminación del caching lo resolvió

 rm -Rf /var/cache 

y crea una nueva carpeta

 mkdir /var/cache 

Esto funcionó para mí.

Confirmaría que mi file de configuration de YUM, /etc/yum.conf no contiene ninguna definición de proxy ala:

 [main] proxy=http://localhost:8080 proxy_username=put_proxy_user_name_here proxy_password=put_proxy_user_password_here 

También asegúrese de que ninguno de los otros files .conf bajo /etc/yum.repo.d/* tampoco tenga ninguna mención de los detalles del proxy.

También me gustaría depurar el problema aún más haciendo uso de la function detallada de yum :

 $ yum -v ....