Hi,
We have one Fedora core5 Server for NIS and NFS running on it and there is
also a second server for NFS. We have two NFS servers to distribute the
load as well as increase disk quota for users. We have also the second NFS
server configured as a NIS secondary for more load balancing.
The configuration works fine most of the time but sometimes it is seen
that the server either stops authenticating the client or does not mount
the home directory of clients and reports a rpc time out.The log messages
generated at that time are as below:
***The client side log messages comming are:
Aug 31 15:25:29 localhost automount[2270]: >> mount: RPC: Timed out Aug 31
15:25:29 localhost automount[2270]: mount(nfs): nfs: mount failure
172.16.88.13:/home1/sachsrinu on /home/sachsrinu
Aug 31 15:25:29 localhost automount[2270]: failed to mount /home/sachsrinu
Aug 31 15:25:29 localhost gdm[2175]: gdm_slave_session_start: Home
directory for sachsrinu: '/home/sachsrinu' does not exist!
Aug 31 15:25:33 localhost ainit:
Aug 31 15:25:33 localhost ainit:
***The server side log messages comming are:
Aug 31 15:21:41 nismaster ypserv[1784]: refused connect from
172.16.91.237:706 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:22:03 nismaster mountd[15524]: authenticated mount request from
172.16.92.250:979 for /home1/bheeku16 (/home1)
Aug 31 15:22:37 nismaster ypserv[1784]: refused connect from
172.16.90.201:880 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:22:37 nismaster ypserv[1784]: refused connect from
172.16.90.201:929 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:22:39 nismaster mountd[15524]: authenticated mount request from
172.16.91.213:618 for /home1/rajkumar (/home1)
Aug 31 15:22:48 nismaster ypserv[1784]: refused connect from
172.16.88.15:33474
to procedure ypproc_match (dcis,netmasks.byaddr;-4)
Aug 31 15:22:49 nismaster ypserv[1784]: refused connect from
172.16.88.15:33474
to procedure ypproc_match (dcis,netmasks.byaddr;-4)
Aug 31 15:23:04 nismaster ypserv[1784]: refused connect from
172.16.92.217:623 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:23:05 nismaster ypserv[1784]: refused connect from
172.16.88.15:33474
to procedure ypproc_match (dcis,netmasks.byaddr;-4)
Aug 31 15:23:28 nismaster last message repeated 5 times
Aug 31 15:23:31 nismaster ypserv[1784]: refused connect from
172.16.90.239:807 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:23:33 nismaster mountd[15524]: authenticated mount request from
172.16.88.200:689 for /home1/mwas_cs (/home1)
Aug 31 15:23:47 nismaster ypserv[1784]: refused connect from
172.16.90.201:1010
to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:23:59 nismaster ypserv[1784]: refused connect from
172.16.88.15:33474
to procedure ypproc_match (dcis,netmasks.byaddr;-4)
Aug 31 15:24:19 nismaster ypserv[1784]: refused connect from
172.16.94.243:612 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:24:27 nismaster mountd[15524]: authenticated mount request from
172.16.93.232:769 for /home1/revathi (/home1)
Aug 31 15:25:03 nismaster mountd[15524]: authenticated mount request from
172.16.91.203:839 for /home1/vidyakrishna_v (/home1)
Aug 31 15:25:40 nismaster mountd[15524]: authenticated mount request from
172.16.92.250:992 for /home1/bheeku16 (/home1)
Aug 31 15:26:14 nismaster mountd[15524]: Caught signal 15, un-registering
and exiting.
Aug 31 15:26:16 nismaster ypserv[1784]: refused connect from
172.16.93.191:702 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:26:18 nismaster kernel: nfsd: last server has exited
Aug 31 15:26:18 nismaster kernel: nfsd: unexporting all filesystems Aug 31
15:26:18 nismaster kernel: RPC: failed to contact portmap (errno -5). Aug
31 15:26:19 nismaster nfsd[15948]: nfssvc_versbits: +2 +3 +4
Aug 31 15:26:19 nismaster kernel: NFSD: Using /var/lib/nfs/v4recovery as
the NFSv4 state recovery directory
Aug 31 15:26:19 nismaster kernel: NFSD: unable to find recovery directory
/var/lib/nfs/v4recovery
Aug 31 15:26:19 nismaster kernel: NFSD: starting 90-second grace period
Aug 31 15:26:55 nismaster mountd[15965]: authenticated mount request from
172.16.90.231:650 for /home1/mwas_cs (/home1)
Aug 31 15:28:43 nismaster mountd[15965]: authenticated mount request from
172.16.92.235:807 for /home1/bsaritha (/home1)
Aug 31 15:29:10 nismaster ypserv[1784]: refused connect from
172.16.89.200:986 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:29:17 nismaster ypserv[1784]: refused connect from
172.16.88.15:33474
to procedure ypproc_match (dcis,netmasks.byaddr;-4)
Aug 31 15:29:37 nismaster mountd[15965]: authenticated mount request from
172.16.94.231:871 for /home1/bheeku16 (/home1)
Aug 31 15:29:38 nismaster ypserv[1784]: refused connect from
172.16.92.235:773 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:30:39 nismaster ypserv[1784]: refused connect from
172.16.93.232:804 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:30:49 nismaster mountd[15965]: authenticated mount request from
172.16.90.231:655 for /home1/mwas_cs (/home1)
Aug 31 15:31:27 nismaster ypserv[1784]: refused connect from
172.16.88.15:33474
to procedure ypproc_match (dcis,netmasks.byaddr;-4)
Aug 31 15:31:32 nismaster ypserv[1784]: refused connect from
172.16.93.232:726 to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:31:53 nismaster ypserv[1784]: refused connect from
172.16.92.219:1013
to procedure ypproc_all (dcis,auto.master;-4)
Aug 31 15:32:01 nismaster mountd[15965]: authenticated mount request from
172.16.91.203:707 for /home1/venkat (/home1)
Aug 31 15:32:55 nismaster mountd[15965]: authenticated mount request from
***The NIS configuration done is :
We have one NIS server the configuration done for the nis server is 1. we
have made changes to the file /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=nismaster name
NISDOMAIN=nis server domain name
2.complied make file in /var/yp
***The nis client side changes that we have made is:
1. In /etc/yp.conf we have added the domain name server
2. In /etc/nsswitch we made changes so nsswitch file is follows
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason #
(like no NIS server responding) then the search continues with the # next
entry.
#
# Legal entries are:
#
# nisplus or nis+ Use NIS+ (NIS version 3)
# nis or yp Use NIS (NIS version 2), also called YP #
dns Use DNS (Domain Name Service)
# files Use the local files
# db Use the local database (.db) files #
compat Use NIS on compat mode
# hesiod Use Hesiod for user lookups
# [NOTFOUND=return] Stop searching if not found so far #
# To use db, put the "db" in front of "files" for entries you want to be #
looked up first in the databases
#
# Example:
#passwd: db files nisplus nis
#shadow: db files nisplus nis
#group: db files nisplus nis
passwd: files nis
shadow: files nis
group: files nis
#hosts: db files nisplus nis dns
hosts: files nis dns
# Example - obey only what nisplus tells us...
#services: nisplus [NOTFOUND=return] files
#networks: nisplus [NOTFOUND=return] files
#protocols: nisplus [NOTFOUND=return] files
#rpc: nisplus [NOTFOUND=return] files
#ethers: nisplus [NOTFOUND=return] files
#netmasks: nisplus [NOTFOUND=return] files
#bootparams: nisplus [NOTFOUND=return] files
ethers: files
netmasks: files
networks: files
protocols: files nis
rpc: files
services: files nis
netgroup: files nis
#publickey: nisplus
automount: files nis
aliases: files nis
3. We have made changes to the file /etc/sysconfig/network and added lines
to file as
NETWORKING = yes
NISDOMAIN = nisserver domain name
***The NFS server side configuration
1. In /etc/export we have added the ip address of system to which it is
exported with (rw,sync).
2. we have directory mount for some user from /home and some as /home1 in
the /etc/passwd file as some user are in nfs1 and some user are in nfs2.
***The NFS client side
1.We have changed the file auto.master in which we added the
first home as nfs1
and second home as home1 for nfs2
2.we have auto.home in client for nfs1
3 we have auto.home in client for nfs2
Please Reply if you know the solution to the problem.
Thanking you
Find out what India is talking about on - Yahoo! Answers India
Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW
