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/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. >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 at 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. -- rgds Stephen