Hi managers,
thank you to all who responded.
I found the problem in a not working ypbind, because there
existed the directory /var/yp/binding from the NIS configuration
before clustering. This directory has to be a cdsl directory and
is not automatically removed when you do a NIS remove and subsequuent
NIS configure (this isn't mentioned elsewhere).
Regards,
Rudi Gabler
-----Ursprüngliche Nachricht-----
Von: Dr. Rudolf Gabler
Gesendet am: Wednesday, July 19, 2000 10:05 AM
An: 'tru64-unix-managers_at_ornl.gov'
Betreff: Cluster NIS problem
Hi all,
in a 2-member TruCLuster (5.0a) I?ve been configuring NIS
with the NIS master name equals the cluster default alias.
Now the following problem occurs: When I boot the first node
into the cluster /sbin/init.d/nis starts up o.k.
When I start the second node /sbin/init.d/nis hangs after
the
NIS high-speed transfer daemon started
message. Only a Ctrl-C continues the boot sequence.
It doesn't matter which node is booted.
When the cluster then is alive, I did a
/sbin/init.d/nis stop
/sbin/init.d/nis start
on each node (as described in the TCR_adm manual).
This works without any waiting on each node.
But only on the "first booted node" I get a result out of
ypwhich; this command hangs on the second node.
Is this a
a) feature
b) misconfiguration
c) bug
??
Any hints are welcome.
Best regards,
Rudi Gabler
Received on Tue Aug 08 2000 - 05:47:40 NZST