[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 789
  • Last Modified:

ypbind fails on only one client

I have a small cluster of 6 nodes all running FC11, on network 192.168.1/24.  Node1 is DHCP, DNS and NIS server for rest.  Nodes 3-6 work correctly as cients for these 3 services.  Node 2 works as DHCP, DNS client to node1, but won't bind - "service ypbind start" times out.  Running wireshark or ypserv -d on node1 shows no NIS related packets being sent from node2 to NIS server.   SSH works fine between all nodes.   Nodes 2-6 have same /etc/yp.conf, from DHCP:

#generated by /sbin/dhclient-script
domain mynisdomain server 192.168.1.41

Selinux is disabled, iptables stoped on all nodes.



0
neilmalloy
Asked:
neilmalloy
  • 4
  • 3
1 Solution
 
jackiechen858Commented:
run "nisdomainname", what's the result? If it's not mynisdomain, then run "nisdomainname mynisdomain "; then restart ypbind.


check /etc/sysconfig/network, make sure it has line "NISDOMAIN=mynisdomain"
0
 
neilmalloyAuthor Commented:
Thanks, but all nodes have nisdomainname set correctly.  They get it from DHCP server when booting, from same host that is running the NIS server.
0
 
jackiechen858Commented:
can you run tcpdump or netstat on node2 to check what's the network activity when trying to start ypbind?

0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
neilmalloyAuthor Commented:
Good suggestion, I did, but result is consistent with results of running tcpdump at server: no packets are being sent.  

The /etc/init.d/ypbind script starts ypbind daemon, tests that it is running using rpcinfo, then tries ypwhich in loop, eventually timing out.  Running ypbind then ypwich from command line shows that after ypbind has supposedly started, ypwhich returns:
"can't yp_bind: Reason: Domain not bound"
But no packets get sent to NIS server at any point.
0
 
jackiechen858Commented:
I couldn't think of any other reason why it won't work then. Maybe the ypbind package on this machine is corrupted, maybe you can reinstall ypbind.
0
 
neilmalloyAuthor Commented:
I had already tried yum remove ypbind, yum install ypbind, with same result.  Other nodes got their ypbind rpm from same local repo and work fine.  

I downloaded source package for same ypbind version, built and installed it.  It works correctly, connects to server normally. I was hoping it would reproduce the problem so I could track it down.  O well.  Thanks for your suggestions.  
0
 
neilmalloyAuthor Commented:
Good debugging suggestions, led to a work-around, but did not help to find the cause of problem.
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now