Need help in addressing an NIS client configuration problem

[whn]

I have a linux machine running on SUSE LINUX Enterprise Server 9 (x86_64), which has some NIS issues. For example, both ‘df –k’ and ‘mount’ commands hang on this client. I have made sure that the NIS server is working fine and I can ping the NIS server from the client.

On the client, I killed the old ypbind and restarted a new ypbind. I also tried to reboot the client. Nothing helped. BTW, when I started ‘ypbind’, I did not get any outputs, not even an error message.

What should I do next to fix this problem?

Thanks for your help.

 

[macd68]

Not a nis issue necessarily. You are not providing details.

The filesystem in question is an NFS or a local filesystem?
Are the required RPC based services running (portmap + rpciod
and other rpc.* ancillaries like lockd, etc... for an NFS client).
What does ypwhich tell you? What does domainname tell you?

This just sounds like typical nis/nfs misconfiguration.
Take a look at your automount or fstab configuration and figure out what filesystems are NFS dependent and then
start at layer3 and work your way up the OSI stack (given evidence of L1/2 function) to determine the root cause.

Good Luck.

 

[whn]

Thank you, macd.

To be frank, I know little about linux admin and I don't understand exactly your questions, either. Sorry for being dumb.

>What does ypwhich tell you? What does domainname tell you?

ypwhich tells me the NIS server name which also manages many other clients fine. Other clients in the same domain are also working fine.

For your other questions, could you please tell me what commands I should run so that I can post the outputs here for you to review?

And here is the fstab file:

% cat /etc/fstab
/dev/sda7            /                    reiserfs   defaults              1 1
/dev/sda1            /data1               auto       noauto,user           0 0
/dev/sdb8            /data10              auto       noauto,user           0 0
/dev/sdb9            /data11              auto       noauto,user           0 0
/dev/sda5            /data2               auto       noauto,user           0 0
/dev/sda6            /data3               auto       noauto,user           0 0
/dev/sda8            /data4               auto       noauto,user           0 0
/dev/sda9            /data5               auto       noauto,user           0 0
/dev/sdb1            /data6               auto       noauto,user           0 0
/dev/sdb5            /data7               auto       noauto,user           0 0
/dev/sdb6            /data8               auto       noauto,user           0 0
/dev/sdb7            /data9               auto       noauto,user           0 0
/dev/sda2            swap                 swap       pri=42                0 0
/dev/sdb2            swap                 swap       pri=42                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
proc                 /proc                proc       defaults              0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
sysfs                /sys                 sysfs      noauto                0 0
/dev/dvd             /media/dvd           subfs      fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0             /media/floppy        subfs      fs=floppyfss,procuid,nodev,nosuid,sync 0 0

 

[whn]

>The filesystem in question is an NFS or a local filesystem?

It is an NFS filesystem.

 

[macd68]

Ok. I'm not seeing an NFS mount listed in this hosts fstab, which means that you may be running an automounter of some sort on the other hosts or that you are missing a configuration line.

If you have access to the correctly functioning linux/*nix hosts you could take a look at their fstab and mount table to determine how the filesystem in question is being mounted.
Once determined you can replicate it on your host and try again.

 

[warmongr]

On the client try

chkconfig portmap on
chkconfig netfs on

And also follow the advice from macd68. He's got you going in the right direction.