MyTetra Share
Делитесь знаниями!
ISSUE do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused
Время создания: 20.05.2016 22:13
Раздел: root - Linux - Distro - SL&CentOS
Запись: Yurons/mytetra/master/base/1463771600uwdxp40lku/text.html на
Issue with 
dsh -n fe22 -a uptime
 do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused
just remove infor about NIS
rm -f /var/yp/binding/*
Some addition info below
Adam C. Powell, IV wrote:

> Does anyone recognize the above error message?  I started getting it
> after installing glibc-2.0.7pre5 (appeared a week ago on
>  It breaks ypbind (none of the NIS server's
> users are known).  The message also spews 5-at-a-time during lynx,
> finger, ftp outside the domain, and 'tar x', which is annoying, but all
> of them work except fingering a username on the NIS server.

DOH!  It was in the glibc FAQ:

     2.18.   I have killed ypbind to stop using NIS, but glibc
     continues using NIS.

     {TK} For faster NIS lookups, glibc uses the /var/yp/binding/
     files from ypbind.  ypbind 3.3 and older versions don't always
     remove these files, so glibc will continue to use them.  Other
     BSD versions seem to work correctly.  Until ypbind 3.4 is
     released, you can find a patch at

     2.19.   Under Linux/Alpha, I always get "do_ypcall: clnt_call:
     RPC: Unable to receive; errno = Connection refused" when using

     {TK} You need a ypbind version which is 64bit clean.  Some
     versions are not 64bit clean.  A 64bit clean implementation is
     ypbind-mt.  For ypbind 3.3, you need the patch from (See the previous question).  I don't know about
     other versions.

> I have heard of another glibc tree with names like glibc-2.0.7-13.  I
> didn't find it anywhere on the gnu ftp sites, but saw mention of it on a
> list archive.  Is this a fork of glibc similar to egcs?

This question remains unresolved...


MyTetra Share v.0.58
Яндекс индекс цитирования