SEMI FINAL UPDATE - More Info -- YP Headaches

Waldher, Travis R Travis.R.Waldher at boeing.com
Fri Sep 3 20:35:11 UTC 2004


 

> -----Original Message-----
> From: Waldher, Travis R 
> Sent: Friday, September 03, 2004 10:37 AM
> To: Getting started with Red Hat Linux
> Subject: RE: UPDATE - More Info -- YP Headaches
> 
>  
> 
> > -----Original Message-----
> > From: Rick Stevens [mailto:rstevens at vitalstream.com]
> > Sent: Friday, September 03, 2004 9:59 AM
> > To: Getting started with Red Hat Linux
> > Subject: Re: UPDATE - More Info -- YP Headaches
> > 
> > Waldher, Travis R wrote:
> > >  > -----Original Message-----
> > > 
> > >>From: Waldher, Travis R
> > >>Sent: Friday, September 03, 2004 9:00 AM
> > >>To: Getting started with Red Hat Linux
> > >>Subject: YP Headaches
> > >>Importance: High
> > >>
> > >>
> > >>When I try to change my NIS password:
> > >>
> > >>[trw3016 at rpdsppc3 trw3016]$ yppasswd -p
> > >>yppasswd: yppasswdd not running on NIS master host ("~hostname~").
> > >>
> > >>On the NIS Server there is this:
> > >>
> > >>   program vers proto   port
> > >>    100000    2   tcp    111  portmapper
> > >>    100000    2   udp    111  portmapper
> > >>    100024    1   udp  32768  status
> > >>    100024    1   tcp  32768  status
> > >>    100004    2   udp    797  ypserv
> > >>    100004    1   udp    797  ypserv
> > >>    100004    2   tcp    800  ypserv
> > >>    100004    1   tcp    800  ypserv
> > >> 600100069    1   udp    806  fypxfrd
> > >> 600100069    1   tcp    808  fypxfrd
> > >>    100021    1   udp  32795  nlockmgr
> > >>    100021    3   udp  32795  nlockmgr
> > >>    100021    4   udp  32795  nlockmgr
> > >>    100021    1   tcp  32903  nlockmgr
> > >>    100021    3   tcp  32903  nlockmgr
> > >>    100021    4   tcp  32903  nlockmgr
> > >>    100011    1   udp    951  rquotad
> > >>    100011    2   udp    951  rquotad
> > >>    100011    1   tcp    970  rquotad
> > >>    100011    2   tcp    970  rquotad
> > >>    100003    2   udp   2049  nfs
> > >>    100003    3   udp   2049  nfs
> > >>    100003    2   tcp   2049  nfs
> > >>    100003    3   tcp   2049  nfs
> > >>    100005    1   udp    973  mountd
> > >>    100005    1   tcp    989  mountd
> > >>    100005    2   udp    973  mountd
> > >>    100005    2   tcp    989  mountd
> > >>    100005    3   udp    973  mountd
> > >>    100005    3   tcp    989  mountd
> > >>    100007    2   udp    866  ypbind
> > >>    100007    1   udp    866  ypbind
> > >>    100007    2   tcp    869  ypbind
> > >>    100007    1   tcp    869  ypbind
> > >>    100009    1   udp    935  yppasswdd
> > >>    391002    2   tcp  32990  sgi_fam
> > >>
> > >>And:
> > >>
> > >>[root at rpdssvr yp]# ps -ef |grep yppass
> > >>root      3726     1  0 08:46 ?        00:00:00 rpc.yppasswdd
> > >>root      4506  3421  0 08:59 pts/1    00:00:00 grep yppass
> > > 
> > > 
> > > Ok let's add to the weirdness.  My NIS Master has two NIC's.
> > > 
> > > eth0      Link encap:Ethernet  HWaddr 00:50:8B:8F:A9:30
> > >           inet addr:136.203.75.118  Bcast:136.203.75.255 
> > > Mask:255.255.255.0
> > > eth1      Link encap:Ethernet  HWaddr 00:04:76:F5:6C:FF
> > >           inet addr:192.168.0.200  Bcast:192.168.0.255 
> > > Mask:255.255.255.0
> > > 
> > > On my 192 client (referencing subnet #) I get this error running
> > > yppasswd:
> > > 
> > > [username at 192client username]$ yppasswd
> > > yppasswd: yppasswdd not running on NIS master host 
> > > ("rpdssvr.ca.boeing.com").
> > > 
> > > If I attempt to telnet to the port indicated in the 
> earlier message:
> > > 
> > > On my 136 client, yppasswd works.
> > > 
> > > [username at 136client username]$ yppasswd Changing NIS account 
> > > information for trw3016 on rpdssvr.ca.boeing.com.
> > > Please enter old password:
> > > Sorry.
> > > 
> > > Any ideas?  I'm REALLY confused now.
> > 
> > Have you checked your firewall configuration on the master 
> server?  It 
> > looks like you have some things blocked there.
> 
> Just checked:
> 
> [root at rpdssvr etc]# service iptables status Firewall is stopped.

Talked to redhat support for a while.  Long story short the problem is
in the yppasswd deamon and you WILL experience this problem if you
intend for your users to use yppaswd from a client that is connected to
a NIS server that has multiple network interfaces connected to
physically isolated networks.

Only eth0 - or, the ip that is tied to the NIC that is tied to the
hostname will work.  All others will fail as they access their own
interface the first time properly, but then try to access eth0 to do the
work.  Which it can't do.  A snippet of the strace:  (this is only an
example, I changed the IP's for security reasons.

Eth0 = 169.254.0.18  (hostname=ypserver)
Eth1 = 192.168.0.200  (hostname=ypserver-2)

sendto(4, "\v\206x\214\0\0\0\0\0\0\0\2\0\1\206\244\0\0\0\2\0\0\0\3"...,
96, 0, {sa_family=AF_INET, sin_port=htons(764),
sin_addr=inet_addr("192.168.0.200")}, 16) = 96
poll([{fd=4, events=POLLIN, revents=POLLIN}], 1, 5000) = 1
recvfrom(4,
"\v\206x\214\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8800, 0,
{sa_family=AF_INET, sin_port=htons(764),
sin_addr=inet_addr("192.168.0.200")}, [16]) = 80
close(4)                                = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
bind(3, {sa_family=AF_INET, sin_port=htons(945),
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
ioctl(3, FIONBIO, [1])                  = 0
setsockopt(3, SOL_IP, IP_RECVERR, [1], 4) = 0
sendto(3, "v#\266z\0\0\0\0\0\0\0\2\0\1\206\240\0\0\0\2\0\0\0\3\0\0"...,
56, 0, {sa_family=AF_INET, sin_port=htons(111),
sin_addr=inet_addr("169.254.0.18")}, 16) = 56
poll([{fd=3, events=POLLIN, revents=POLLERR}], 1, 5000) = 1
recvmsg(3, {msg_name(16)={sa_family=AF_INET, sin_port=htons(111),
sin_addr=inet_addr("169.254.0.18")},
msg_iov(1)=[{"v#\266z\0\0\0\0\0\0\0\2\0\1\206\240\0\0\0\2\0\0\0\3\0\0"..
., 56}], msg_controllen=44, msg_control=0x7fffaf00, ,
msg_flags=MSG_ERRQUEUE}, MSG_ERRQUEUE) = 56
close(3)                                = 0
write(2, "yppasswd: yppasswdd not running "..., 78yppasswd: yppasswdd
not running on NIS master host ("ypserver"





More information about the Redhat-install-list mailing list