Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help with NIS master upgrade

Status
Not open for further replies.

ponetguy2

MIS
Aug 28, 2002
442
US
I'm replacing our NIS masters in our DMZ. It is currently running Solaris 8 and I'm replacing it with Solaris 10. I finished building the boxes and copied /var/yp from the existing servers to the new Solaris 10 boxes. From there I ran ypinit -m. I'm about to swap the boxes, but I'm uncomfortable. Has anyone done this before? If so, please advise. I'm new to NIS and I would appreciate any advise.

One more question. How can I make sure that the boxes are masters. Correct me if I'm wrong, ypserv (ypserv -d) needs to be running on the master, right?

FYI: All NIS masters will keep their existing IP and name.

"Not all OSs suck, it's just that some OSs suck worse than others"


 
FYI:

After running ypinit -m, I got these messages below:

If there are running slave yp servers, run yppush now for any data bases
which have been changed. If there are no running slaves, run ypinit on
those hosts which are to be slave servers.
svcadm: Pattern 'network/nis/server:default' doesn't match any instances
ypinit: unable to enable network/nis/server:default
svcadm: Pattern 'network/nis/xfr:default' doesn't match any instances
ypinit: unable to enable network/nis/xfr:default
svcadm: Pattern 'network/nis/passwd:default' doesn't match any instances
ypinit: unable to enable network/nis/passwd:default
svcadm: Pattern 'network/nis/update:default' doesn't match any instances
ypinit: unable to enable network/nis/update:default

Any idea?

"Not all OSs suck, it's just that some OSs suck worse than others"


 
Hi Ponetguy2,

All sounds good to me. In my environment I usually make the new server a slave and then promote it to master.
As long as the source files and correct directory structures are set up then I believe you should be good to go.
ypserv needs to run on masters and slaves.

Good luck
Alan
 
Hello Alan.

When I ran ypinit -m, I got these messages:


NIS make terminated: netgroup.time
Error running Makefile.

test118 has been set up as a yp master server with errors. Please remember
to figure out what went wrong, and fix it.

If there are running slave yp servers, run yppush now for any data bases
which have been changed. If there are no running slaves, run ypinit on
those hosts which are to be slave servers.
svcadm: Pattern 'network/nis/server:default' doesn't match any instances
ypinit: unable to enable network/nis/server:default
svcadm: Pattern 'network/nis/xfr:default' doesn't match any instances
ypinit: unable to enable network/nis/xfr:default
svcadm: Pattern 'network/nis/passwd:default' doesn't match any instances
ypinit: unable to enable network/nis/passwd:default
svcadm: Pattern 'network/nis/update:default' doesn't match any instances
ypinit: unable to enable network/nis/update:default

Should I worry? I'm currently googling right now for the messages. So far, no luck.

"Not all OSs suck, it's just that some OSs suck worse than others"


 
FYI:

I don't have it hooked up to the network. I'm currently connected via serail to the server from my PC. I'm not sure if this would cause a problem when running ypinit -m.

"Not all OSs suck, it's just that some OSs suck worse than others"


 
I don't know much about Solaris 10, but you might have to actually enable NIS services through the svcadm or something.
 
hello coffeysm. i tried to enable nis server through svcadm, but i get these messages.


svcadm: Pattern 'network/nis/server:default' doesn't match any instances


NIS make terminated: netgroup.time
Error running Makefile.

chifakehostname has been set up as a yp master server with errors. Please remember
to figure out what went wrong, and fix it.

If there are running slave yp servers, run yppush now for any data bases
which have been changed. If there are no running slaves, run ypinit on
those hosts which are to be slave servers.
svcadm: Pattern 'network/nis/server:default' doesn't match any instances
ypinit: unable to enable network/nis/server:default
svcadm: Pattern 'network/nis/xfr:default' doesn't match any instances
ypinit: unable to enable network/nis/xfr:default
svcadm: Pattern 'network/nis/passwd:default' doesn't match any instances
ypinit: unable to enable network/nis/passwd:default
svcadm: Pattern 'network/nis/update:default' doesn't match any instances
ypinit: unable to enable network/nis/update:default

"Not all OSs suck, it's just that some OSs suck worse than others"


 
Hi Ponetguy2,

These are the services you should see if you do svcs -a;

disabled Jul_13 svc:/network/nis/server:default
disabled Jul_13 svc:/network/nis/passwd:default
disabled Jul_13 svc:/network/nis/update:default
disabled Jul_13 svc:/network/nis/xfr:default
online Nov_20 svc:/network/nis/client:default

These need to be enabled for NIS.

svcadm enable svc:/network/nis/server:default

This is all I can think of to troubleshoot your problem.
Sorry I can't help any further. I really don't understand why your box is complaining about matching patterns.

I have done this on two seperate occasions now and haven't seen any of these problems you are experiencing.
Good luck and I'll keep looking. Let us know if you find your solution.

Alan
 
Make sure you also have those files even if they are empty. Try running touch netgroup in the NIS directory see if that helps you.
 
Thank you Alan and coffeysm. Maybe I'm getting these error messages because the machine is not on any type of network. As I stated earlier, I'm connecting to it via serial. It's actually sitting on my desk :) I'll keep you guys posted on my progress.

"Not all OSs suck, it's just that some OSs suck worse than others"


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top