Redhat AS4 fresh install ypserv not stable
- From: simon@xxxxxxxxxxxxx
- Date: 21 Dec 2006 09:19:29 -0800
I have been banging my head against a this problem for a day to two
now...
Basically we have a fresh install of AS4 on a machine. I have followed
an amalgamation of a collection of different HOWTOs on the web to get a
NIS master set up on the machine.
Everything a first seems fine...
[root@linuxdev14 ~]# service ypserv stop; service ypserv start
Stopping YP server services: [ OK ]
Starting YP server services: [ OK ]
[root@linuxdev14 ~]# rpcinfo -u localhost ypserv
program 100004 version 1 ready and waiting
program 100004 version 2 ready and waiting
.... then some time later and no longer than 5 minutes - the call to
rpcinfo will change to...
[root@linuxdev14 ~]#
rpcinfo: RPC: Timed out
program 100004 version 0 is not available
.... and will remain like that until it is restarted.
The only lead I have is that at exactly the same time as the call
changes crond also prints the following to /var/log/messages...
Dec 21 16:27:59 linuxdev14 ypserv: ypserv shutdown succeeded
Dec 21 16:27:59 linuxdev14 ypserv[12096]: Support for SLP (line 20)
is not compiled in.
Dec 21 16:27:59 linuxdev14 ypserv[12096]: Support for SLP (line 22)
is not compiled in.
Dec 21 16:27:59 linuxdev14 ypserv: ypserv startup succeeded
Dec 21 16:30:01 linuxdev14 crond(pam_unix)[12486]: session opened for
user rootby (uid=0)
Dec 21 16:30:01 linuxdev14 crond(pam_unix)[12488]: session opened for
user rootby (uid=0)
Dec 21 16:30:01 linuxdev14 crond(pam_unix)[12488]: session closed for
user root
Dec 21 16:30:01 linuxdev14 crond(pam_unix)[12486]: session closed for
user root
I am convinced this can't be a coincidence, in fact if I stop the crond
service these prints stop and the calls to rpcinfo continue to work.
However, if I can still get the rpcinfo calls to change. If I go to a
client machine that is setup to use the master's domain and restart
portmap and ypbind everything at first appears to be okay, but if I
then try and run a command that will make a yp call ( id <nisUser>, su
- <nisUser> ) they cause the calls to rpcinfo that I have running in a
loop in a shell on the master to switch to the Timeout state. Running
these other commands directly on the master will not cause this to
happen...
Things that I have already been through, checked and done from various
news discussions I have found in my web wanderings so far:
- turned off SElinux
- added a /etc/ypserv.securenets file
- added 'ypserv: ALL' to /etc/hosts.allow
- made sure all 5 daemons on the master are up and running
If anyone has any ideas of how to fix this, it would be much
appreciated.
Thanks
Simon
.
- Prev by Date: Re: rup command is not showing remote linux systems
- Next by Date: Bizarre permissions of httpd daemon, RH EL4 with SELinux.
- Previous by thread: Diff between Kernel 2.4 and Kernel 2.6
- Next by thread: Bizarre permissions of httpd daemon, RH EL4 with SELinux.
- Index(es):
Relevant Pages
|
|
