Yum Causing RPC Timed Out?

Home » CentOS » Yum Causing RPC Timed Out?
CentOS 6 Comments

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
epel/x86_64 Extra Packages for Enterprise Linux 7 – x86_64 7,312
extras/7/x86_64 CentOS-7 – Extras
rpmforge RHEL 7 – RPMforge.net –
dag 245
updates/7/x86_64 CentOS-7 – Updates
repolist: 17,847
[root@localhost ~]# yum –disablerepo=epel –disablerepo=rpmforge provides
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/3cda64d1c161dd0fead8398a62ef9c691e78ee02fe56d04566f850c94929f61f-filelists.sqlite.bz2:
[Errno 12] Timeout on http://CentOS.corenetworks.net/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fead8398a62ef9c691e78ee02fe56d04566f850c94929f61f-filelists.sqlite.bz2:
(28, ‘Resolving timed out after 30385 milliseconds’)
Trying other mirror. do_ypcall: clnt_call: RPC: Timed out
[etc. etc.]

6 thoughts on - Yum Causing RPC Timed Out?

  • 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/3cda64d1c161dd0fead8398a62ef9c691e78ee02fe56d04566f850c94929f61f-filelists.sqlite.bz2:
    [Errno 12] Timeout on http://mirror.supremebytes.com/CentOS/7.0.1406/os/x86_64/repodata/3cda64d1c161dd0fead8398a62ef9c691e78ee02fe56d04566f850c94929f61f-filelists.sqlite.bz2:
    (28, ‘Resolving timed out after 30384 milliseconds’)
    Trying other mirror.

  • 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

  • “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.

  • grep hosts /etc/nsswitch.conf hosts: files nis dns myhostname

    Maybe I should change to hosts: files dns nis myhostname

    It is a problem if yum expects it to be something else. NIS passes all the tests I have (“ypcat ” outputs what I expect). thanks, Dave

  • 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.