Date: Thu, 11 Feb 1999 13:11:37 -0500 (EST) From: Mikhail Teterin <mi@misha.cisco.com> To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Cc: bugs@FreeBSD.ORG Subject: Re: bin/10031: ypxfr does not work with Solaris master server(s) Message-ID: <199902111811.NAA18222@misha.cisco.com> In-Reply-To: <199902111727.MAA23424@skynet.ctr.columbia.edu> from Bill Paul at "Feb 11, 1999 12:27:56 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > >Category: bin > > >Synopsis: ypxfr does not work with Solaris master server(s) > > No, ypxfr works fine with a Solaris master server. It's your NIS > master server (or what you believe to be the master server) that's the > problem. That's quite possible, actually. The reason I started to bother was because yp-related lookups are very slow and fail on occasion here. > > The master server nis1, apparently, redirects requests to another > > (slave?) server nis2. > > No, the 'master' server is redirecting ypxfr to another server because of > a problem with the maps. > > The fact that you put (slave?) in parentheses and with a question mark > gives me the impression that you aren't even really sure how NIS is > configured on your network. This could also be part of the problem. Absolutely! > > Both of them run Solaris. > _WHAT VERSION_ of Solaris. Good question. I do not have a login account there... > > ypxfr: couldn't create udp handle to ypserv: RPC: Program not registered > > ypxfr: source was: nis2 <-- my message on ypxfr_misc.c:229 > > ypxfr: failed to get order number of passwd.byname from nis2: > > RPC failure talking to server <-- my modifiction of message > > on ypxfr_main.c:368 > The error messages clearly indicate that host "nis2" is not running ypserv. > This is why I questioned your reasons for saying "(slave?)" before in > reference to nis2. It also clearly indicates the real problem, and it > has nothing to do with ypxfr. Perhaps. All I know, is that `ypwich' return nis1, but ypxfr -h nis1 talks to nis2. May be, it is nis1's fault for redirecting to non-functional nis2, I don't know. All I know is that ypbind works, but is slow on occasition and I wanted to run a local slave server. > Wrong. The information you provide is not sufficient to duplicate the > problem you describe. You have made the assumption that the Solaris > server machines are configured correctly. The Solaris machines are not > configured correctly (or at the very least are not configured the way > you think they are). Please, don't be angry. Before filing the pr I asked for help on questions and received only one, erroneous, suggestion... > > >Fix: > > > > I think, this has to do with ypxfr not failing over properly to > > the SunOS compatable strategy, but I'm not sure... I wish, there > > was a switch to not even try the FreeBSD-specific algorithm... > No, this has nothing at all to do with the FreeBSD-specific ypxfr Ok, it was just a guess... > You specified nis1 as the source host, but the maps say that the master > server is nis2. This can happen if: [...] > If you don't believe me, run 'yppoll passwd.byname' from the FreeBSD Well, not that I do not believe you, but yppoll does not work: # yppoll passwd yppoll: no such map passwd. Reason: YP server error ypcat does, however: # ypcat passwd | wc -l 8888 Any chance of getting the initial databases from one of the funcitonal slaves? Thanks for your help! I guess, the pr can be closed... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902111811.NAA18222>