NIS Server - Slave Setup

nis-master | nis-slave | nis-client | nis-ops

Slave setup

follow the nis-master guide where appropriate (incl. the ACLs) and here’s what’s specific.

ping -c1 ypmaster
nmap -p 111 ypmaster

initialize local the NIS databases

# debian
/usr/lib/yp/ypinit -s ypmaster

# slackware
/usr/lib64/yp/ypinit -s ypmaster

# netbsd
ypinit -s ypmaster

HA acceptance

tests

Now it’s time to validate the Master <-> Slave fail-overs.

  1. shutdown or destroy the master server
  2. and see if getent still shows nis users and groups
  3. also see if NIS users can still log onto the client systems

How to test on the client systems

getent group | tail
ypwhich

results

you will notice the clients stay connected to the last available node, be it the master or the slave.

you will eventually see the following error if you try to talk NIS during the fail-over period.

yp_bind_client_create_v3: RPC: Timed out

but the request will eventually be successfull even though the original call timed out.

Troubleshooting

while generating the maps with ypinit on the slave Transferring group.bygid… Trying ypxfrd …ypmaster.angrycow.ru: RPC: Program not registered rpcb_getaddr (ypmaster.angrycow.ru) failed!

==> start the rpc.xfrd RPC program on the master

TODO


HOME | GUIDES | LECTURES | LAB | SMTP HEALTH | HTML5
Copyright © 2022 Pierre-Philipp Braun