so, i just installed CentOS on our server and set up NIS using the same configuration as on our other server, but the clients' ypbind services complain that although they can find the correct server, the server does not respond to requests.
to debug this, i've:
* pinged the server using its ip and it's name * ssh'ed to the server using it's ip and name * ftp'd to the server using its ip and name * used dig to get the server's address from itself (dig @stretch stretch.washcslab.org * checked to see that nfs and ypserv are running * checked to see if stretch could bind to it's own nis server
and all of these were successful. so, I also:
* run ypserv (on the server) and ypbind (on the server) both in debug mode and gotten no errors * run ypserv (on the server) and ypbind (on the CLIENT) both in debug mode and gotten no errors
any help with this really gnarly bug would be greatly appreciated! steve
Around 12:08am on Tuesday, July 17, 2007 (UK time), Steve Strong scrawled:
any help with this really gnarly bug would be greatly appreciated!
You're not blocked by iptables, are you?
Steve
On Mon, 16 Jul 2007, Steve Strong wrote:
so, i just installed CentOS on our server and set up NIS using the same configuration as on our other server, but the clients' ypbind services complain that although they can find the correct server, the server does not respond to requests.
to debug this, i've:
- pinged the server using its ip and it's name
- ssh'ed to the server using it's ip and name
- ftp'd to the server using its ip and name
- used dig to get the server's address from itself (dig @stretch stretch.washcslab.org
- checked to see that nfs and ypserv are running
- checked to see if stretch could bind to it's own nis server
and all of these were successful. so, I also:
- run ypserv (on the server) and ypbind (on the server) both in debug mode and gotten no errors
- run ypserv (on the server) and ypbind (on the CLIENT) both in debug mode and gotten no errors
any help with this really gnarly bug would be greatly appreciated! steve
Is ypserv compiled against libwrap? Does there need to be a hosts.allow entry?
Is SELinux enabled? Does /var/log/audit/audit.log show anything?
Is iptables in use? Does an exception need to be made?
Can you attach strace to ypserv and see anything of significance?
Paul Heinlein wrote:
On Mon, 16 Jul 2007, Steve Strong wrote:
so, i just installed CentOS on our server and set up NIS using the same configuration as on our other server, but the clients' ypbind services complain that although they can find the correct server, the server does not respond to requests.
to debug this, i've:
- pinged the server using its ip and it's name
- ssh'ed to the server using it's ip and name
- ftp'd to the server using its ip and name
- used dig to get the server's address from itself (dig @stretch stretch.washcslab.org
- checked to see that nfs and ypserv are running
- checked to see if stretch could bind to it's own nis server
and all of these were successful. so, I also:
- run ypserv (on the server) and ypbind (on the server) both in debug mode and gotten no errors
- run ypserv (on the server) and ypbind (on the CLIENT) both in debug mode and gotten no errors
any help with this really gnarly bug would be greatly appreciated! steve
Is ypserv compiled against libwrap? Does there need to be a hosts.allow entry?
Is SELinux enabled? Does /var/log/audit/audit.log show anything?
Is iptables in use? Does an exception need to be made?
Can you attach strace to ypserv and see anything of significance?
ypserv: i didn't compile it, i used the rpm that is standard with an installation ---
selinux: disabled (which i hate)
iptables: how do i go about making an exception -- this seems like the problem, since there is no report of an attempt to connect to ypserv by a client in the debug output of a call to start ypserv
Steve Strong wrote:
so, i just installed CentOS on our server and set up NIS using the same configuration as on our other server, but the clients' ypbind services complain that although they can find the correct server, the server does not respond to requests.
to debug this, i've:
- pinged the server using its ip and it's name
- ssh'ed to the server using it's ip and name
- ftp'd to the server using its ip and name
- used dig to get the server's address from itself (dig @stretch stretch.washcslab.org
- checked to see that nfs and ypserv are running
- checked to see if stretch could bind to it's own nis server
and all of these were successful. so, I also:
- run ypserv (on the server) and ypbind (on the server) both in debug mode and gotten no errors
- run ypserv (on the server) and ypbind (on the CLIENT) both in debug mode and gotten no errors
any help with this really gnarly bug would be greatly appreciated! steve
Hi,
Are you running with Security Enhanced Linux Enabled or Disabled ? If so try disabling it at least temporarily. Some people will say set to permissive mode rather than disable, but specifically for NIS I have seen different behaviour between permissive and disabled. If this works others may be able to assist you with getting SE Linux worknig with NIS.
Are you running a Firewall ?
Clint Dilks wrote:
Steve Strong wrote:
so, i just installed CentOS on our server and set up NIS using the same configuration as on our other server, but the clients' ypbind services complain that although they can find the correct server, the server does not respond to requests.
to debug this, i've:
- pinged the server using its ip and it's name
- ssh'ed to the server using it's ip and name
- ftp'd to the server using its ip and name
- used dig to get the server's address from itself (dig @stretch stretch.washcslab.org
- checked to see that nfs and ypserv are running
- checked to see if stretch could bind to it's own nis server
and all of these were successful. so, I also:
- run ypserv (on the server) and ypbind (on the server) both in debug mode and gotten no errors
- run ypserv (on the server) and ypbind (on the CLIENT) both in debug mode and gotten no errors
any help with this really gnarly bug would be greatly appreciated! steve
Hi,
Are you running with Security Enhanced Linux Enabled or Disabled ? If so try disabling it at least temporarily. Some people will say set to permissive mode rather than disable, but specifically for NIS I have seen different behaviour between permissive and disabled. If this works others may be able to assist you with getting SE Linux worknig with NIS.
Are you running a Firewall ? _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
i'm running a firewall, but selinux is disabled. what should i look for in the firewall? steve
-
Clint Dilks -
Paul Heinlein -
Steve Searle -
Steve Strong