On Wed, May 30, 2001 at 05:16:43PM -0700, Ian Greenhoe wrote: > Not necessarily suprising. I've found the most useful way to get data > from ypserv is to run it from a seperate [aEwx]term with the -d > switch. Word of warning: It can produce a *lot* of data.
Or it might not... bradley:~# ypserv -d [Welcome to the NYS YP Server, version 1.3.11 (with securenets)] Find securenet: 255.0.0.0 127.0.0.0 Find securenet: 0.0.0.0 0.0.0.0 ypserv.conf: 0.0.0.0/0.0.0.0:shadow.byname:2:0:2 ypserv.conf: 0.0.0.0/0.0.0.0:passwd.adjunct.byname:2:0:2 ypserv.conf: 0.0.0.0/0.0.0.0:*:0:0:2 And that's it. I fired up a `ypbind -d -broadcast` in another window and all I got there was bradley:~# ypbind -d -broadcast add_server() domain: mycompany.com, broadcast, slot: 0 [Welcome to ypbind-mt, version 1.7] broadcast: RPC: Timed out. or, alternately, bradley:~# ypbind -d parsing config file Trying entry: domain mycompany.com ypserver bradley.west.mycompany.com parsed domain 'mycompany.com' broadcast add_server() domain: mycompany.com, broadcast, slot: 0 [Welcome to ypbind-mt, version 1.7] Either way, `ypwhich` causes the ypbind to display ypbindproc_domain_2_svc (mycompany.com) Status: YPBIND_FAIL_VAL and start showing RPC timeouts alternating with notes that it's pinging active servers. But, throughout all of this, ypserv just sits there quietly. > 2) There are a number of potential problems: > > * NIS was broken in testing due to recent glibc upgrade. > [upgrade nis if you are using testing/unstable] Nope, it's potato, version 3.8-2. > * make sure that /etc/ypserv.conf is set up appropriately. You might > wish to add the following temporarily [for testing only, since it > opens NIS up to anybody who can access your machine. Better make > sure that your passwords are good!] > > * : * : none No change other than having two "ypserv.conf: 0.0.0.0/0.0.0.0:*:0:0:2" lines in ypserv's output instead of one. > * add a "ypserver" line to /etc/yp.conf if it doesn't exist. Already contains "domain mycompany.com ypserver bradley.west.mycompany.com". > * make sure that NISSERVER=master in /etc/init.d/nis Check. > * make sure that nis was started *after* portmapper. In fact, you may want > to do the following: Check. I actually had tried shutting down NFS and then stopping and starting portmapper and NIS in various combinations yesterday; NIS gives a completely different set of errors when portmapper is shut down. > 3) check that nis is registered with portmapper > (you'll see ypbind/ypserv, not nis, listed) > pmap_dump bradley:~# pmap_dump 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 849 status 100024 1 tcp 851 status 100004 2 udp 673 ypserv 100004 1 udp 673 ypserv 100004 2 tcp 676 ypserv 100004 1 tcp 676 ypserv 100007 2 udp 714 ypbind 100007 1 udp 714 ypbind 100007 2 tcp 717 ypbind 100007 1 tcp 717 ypbind Any further suggestions or anything seemingly relevant in this information? -- That's not gibberish... It's Linux. - Byers, The Lone Gunmen Geek Code 3.12: GCS d? s+: a C++ UL++++$ P++>+++ L+++>++++ E- W--(++) N+ o+ !K w--- O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv+ b+ DI++++ D G e* h r y+