I just installed centos 7, yum is acting strange, experiencing RPC time-outs. Sometimes when I disable the additional repos (epel and rpmforge) it seems to make things act normal. But not this time (see below).
Could I have some misconfiguration? Network glitch? What hypotheses should I be considering? Thanks, Dave
[root@localhost ~]# yum repolist repo id repo name status base/7/x86_64 CentOS-7 - Base 8,465 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 7,312 extras/7/x86_64 CentOS-7 - Extras 104 rpmforge RHEL 7 - RPMforge.net - dag 245 updates/7/x86_64 CentOS-7 - Updates 1,721 repolist: 17,847 [root@localhost ~]# yum --disablerepo=epel --disablerepo=rpmforge provides '*/applydeltarpm' do_ypcall: clnt_call: RPC: Timed out do_ypcall: clnt_call: RPC: Timed out http://centos.corenetworks.net/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fe...: [Errno 12] Timeout on http://centos.corenetworks.net/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fe...: (28, 'Resolving timed out after 30385 milliseconds') Trying other mirror. do_ypcall: clnt_call: RPC: Timed out [etc. etc.]
Apparently CentOS-7 - Base is failing, what does that mean? How do I contact the upstream for the repo? How do I find a working upstream?
More info from command execution: do_ypcall: clnt_call: RPC: Timed out do_ypcall: clnt_call: RPC: Timed out http://mirror.supremebytes.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c1...: [Errno 12] Timeout on http://mirror.supremebytes.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c1...: (28, 'Resolving timed out after 30384 milliseconds') Trying other mirror.
One of the configured repositories failed (CentOS-7 - Base), 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 base
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=base.skip_if_unavailable=true
failure: repodata/3cda64d1c161dd0fead8398a62ef9c691e78ee02fe56d04566f850c94929f61f-filelists.sqlite.bz2 from base: [Errno 256] No more mirrors to try. http://centos.corenetworks.net/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fe...: [Errno 12] Timeout on http://centos.corenetworks.net/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fe...: (28, 'Resolving timed out after 30385 milliseconds') http://mirror.us.oneandone.net/linux/distributions/centos/7.0.1406/os/x86_64...: [Errno 12] Timeout on http://mirror.us.oneandone.net/linux/distributions/centos/7.0.1406/os/x86_64...: (28, 'Resolving timed out after 30385 milliseconds') http://centos.sonn.com/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fead8398a6...: [Errno 12] Timeout on http://centos.sonn.com/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fead8398a6...: (28, 'Resolving timed out after 30383 milliseconds') http://centos-distro.cavecreek.net/centos/7.0.1406/os/x86_64/repodata/3cda64...: [Errno 12] Timeout on http://centos-distro.cavecreek.net/centos/7.0.1406/os/x86_64/repodata/3cda64...: (28, 'Resolving timed out after 30383 milliseconds') http://mirror.clarkson.edu/centos/7.0.1406/os/x86_64/repodata/3cda64d1c161dd...: [Errno 12] Timeout on http://mirror.clarkson.edu/centos/7.0.1406/os/x86_64/repodata/3cda64d1c161dd...: (28, 'Resolving timed out after 30383 milliseconds') http://mirror.thelinuxfix.com/CentOS/7.0.1406/os/x86_64/repodata/3cda64d1c16...: [Errno 12] Timeout on http://mirror.thelinuxfix.com/CentOS/7.0.1406/os/x86_64/repodata/3cda64d1c16...: (28, 'Resolving timed out after 30383 milliseconds') http://mirrors.psychz.net/Centos/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0...: [Errno 12] Timeout on http://mirrors.psychz.net/Centos/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0...: (28, 'Resolving timed out after 30383 milliseconds') http://repos.mia.quadranet.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c1...: [Errno 12] Timeout on http://repos.mia.quadranet.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c1...: (28, 'Resolving timed out after 30384 milliseconds') http://mirrors.loosefoot.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c161...: [Errno 12] Timeout on http://mirrors.loosefoot.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c161...: (28, 'Resolving timed out after 30384 milliseconds') http://mirror.supremebytes.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c1...: [Errno 12] Timeout on http://mirror.supremebytes.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c1...: (28, 'Resolving timed out after 30384 milliseconds') [root@localhost ~]#
On Fri, Feb 27, 2015 at 11:06 AM, Dave Burns tburns@hawaii.edu wrote:
I just installed centos 7, yum is acting strange, experiencing RPC time-outs. Sometimes when I disable the additional repos (epel and rpmforge) it seems to make things act normal. But not this time (see below).
Could I have some misconfiguration? Network glitch? What hypotheses should I be considering? Thanks, Dave
[root@localhost ~]# yum repolist repo id repo name status base/7/x86_64 CentOS-7 - Base 8,465 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 7,312 extras/7/x86_64 CentOS-7 - Extras 104 rpmforge RHEL 7 - RPMforge.net - dag 245 updates/7/x86_64 CentOS-7 - Updates 1,721 repolist: 17,847 [root@localhost ~]# yum --disablerepo=epel --disablerepo=rpmforge provides '*/applydeltarpm' do_ypcall: clnt_call: RPC: Timed out do_ypcall: clnt_call: RPC: Timed out
http://centos.corenetworks.net/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fe...: [Errno 12] Timeout on http://centos.corenetworks.net/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fe...: (28, 'Resolving timed out after 30385 milliseconds') Trying other mirror. do_ypcall: clnt_call: RPC: Timed out [etc. etc.]
On 02/27/2015 01:11 PM, Dave Burns wrote:
Apparently CentOS-7 - Base is failing, what does that mean? How do I contact the upstream for the repo? How do I find a working upstream?
More info from command execution: do_ypcall: clnt_call: RPC: Timed out do_ypcall: clnt_call: RPC: Timed out http://mirror.supremebytes.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c1...: [Errno 12] Timeout on http://mirror.supremebytes.com/centos/7.0.1406/os/x86_64/repodata/3cda64d1c1...: (28, 'Resolving timed out after 30384 milliseconds') Trying other mirror.
This has nothing to do with yum.
You are using NIS for name lookup and your NIS server is not responding.
-Thomas
On Fri, Feb 27, 2015 at 11:57 AM, Thomas Eriksson < thomas.eriksson@slac.stanford.edu> wrote:
This has nothing to do with yum.
You are using NIS for name lookup and your NIS server is not responding.
NIS is working fine, at least, for what I expect it to do.
What makes you think NIS is involved? What does yum use NIS for? Is there a test command I could use to see whether NIS is working for yum? What names is yum looking up? Is Errno 12 a clue? I tried searching for (do_ypcall: clnt_call: rpc: timed out "errno 12" ), got many confusing hits, nothing obviously helpful.
thanks, Dave
On Fri, Feb 27, 2015 at 12:38:06PM -1000, Dave Burns wrote:
What makes you think NIS is involved?
Is Errno 12 a clue? I tried searching for (do_ypcall: clnt_call: rpc: timed
"do_ypcall" is a NIS error message. (Previous NIS was called "yellow pages"; the "yp" in do_ypcall is a reference to that).
Maybe you have "hosts: files nis" in /etc/nsswitch.conf or something else that's causing the OS to want to talk to NIS.
You _DO_ have a problem with your NIS setup somewhere.
On Fri, Feb 27, 2015 at 12:41 PM, Stephen Harris lists@spuddy.org wrote:
"do_ypcall" is a NIS error message. (Previous NIS was called "yellow pages"; the "yp" in do_ypcall is a reference to that).
Maybe you have "hosts: files nis" in /etc/nsswitch.conf or something else that's causing the OS to want to talk to NIS.
grep hosts /etc/nsswitch.conf hosts: files nis dns myhostname
Maybe I should change to hosts: files dns nis myhostname ?
You _DO_ have a problem with your NIS setup somewhere.
It is a problem if yum expects it to be something else. NIS passes all the tests I have ("ypcat <various>" outputs what I expect). thanks, Dave
On 02/27/2015 04:16 PM, Dave Burns wrote:
On Fri, Feb 27, 2015 at 12:41 PM, Stephen Harris lists@spuddy.org wrote:
"do_ypcall" is a NIS error message. (Previous NIS was called "yellow pages"; the "yp" in do_ypcall is a reference to that).
Maybe you have "hosts: files nis" in /etc/nsswitch.conf or something else that's causing the OS to want to talk to NIS.
grep hosts /etc/nsswitch.conf hosts: files nis dns myhostname
Maybe I should change to hosts: files dns nis myhostname ?
You _DO_ have a problem with your NIS setup somewhere.
It is a problem if yum expects it to be something else. NIS passes all the tests I have ("ypcat <various>" outputs what I expect). thanks,
Yum is blissfully unaware of how the hostname is resolved. It just uses a system call and expects to get an answer within a reasonable time.
The message "do_ypcall: clnt_call: RPC: Timed out" is coming from ypbind and indicates that NIS is not working as it should.
Swapping the order of dns and nis in nsswitch.conf will probably get you going for this particular case, provided that dns is working. But the NIS problem is going to bite you sooner or later if you don't sort it out.
-Thomas
-
Dave Burns -
Stephen Harris -
Thomas Eriksson