Hi All
Thanks for all your answers - the problem was that ypserv had stopped on the slave machine. Restarting this sorted the problem out. I have included my original question and all the help I received.
Many thanks
Liz
---------------------------------------------------------------------
ORIGINAL QUESTION:
Hi All
I have a network containing several Sun sparc's, running solaris 2.5.1. I
added a new disk and moved a home directory onto this new disk. I
ammended amd.homedir and auto_home to reflect this change but when I ran
make to update the maps I get the following error:-
updated netid
nis server not registered at ekman.
pushed netid
updated auto.home
nis server not registered at ekman.
pushed netid
updated amd.homedir
nis server not registered at ekman.
pushed amd.homedir
(Ekman is the slave)
Any ideas would be very gratefully accepted.
Many thanks
Liz
----------------------------------------------------------------------
Thomas Lewis:
I would go to the slave and reconfigure it as an NIS slave again using
the ypinit -s command (master_server). That is how I solved a similiar
problem here.
Hope this suggestion was helpful.
-----------------------------------------------------------------------
Jürgen Rothenanger:
I would do two things. First look in the ypmap nisservers, whether ekman
is in this map. If not you should add the name (via makemap). Second,
you can remove the directory /var/yp/<domainname> on the slave and
reinstall the slave with ypinit -s <master>.
-----------------------------------------------------------------------
Brooke King:
Most likely ekman cannot do a reverse lookup on the master's IP
address to find the master's name. Check ekman's nsswitch.conf
and anything it references on its hosts line.
-----------------------------------------------------------------------
David Blaine:
ypserv is not running on your slave ekman. Make sure it is still a slave.
-----------------------------------------------------------------------
Richard Roberto:
You can do a quick check to see if the ypserv daemon is running on
ekman, and that ekman's ip address is correct in NIS. Worst case
scenario, you can kill ypserv on ekman, reinit it with ypinit -s,
and restart ypserv.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:51 CDT