Hello Guru's,
yes, I think there is a tough nut to crack:
After a upgrade from 4.0G (with a direct step over version 5.1) to 5.1B
PK1 if have
a strange problem with NIS/YP.
1.) When a user login to the NIS-Master and try to change the passwort
the follwing happens:
NIS-Master>yppasswd
Changing NIS password for USERNAME
Old NIS password:
New password:
Retype new password:
RPC: Timed out
Your NIS passwd may or may not be changed
NIS-Master>
'USERNAME' is the login of the current user.
The passwort is allways changed. But for a short time the NIS passwort
service is not
available! After inserting (even as root) the command 'ypcat passwd' the
answer is:
'no such map in server's domain'. It's about 10 until 15 seconds, but
long enough that
some user can't login or a mail isn't receiving because the user is
unknown in this situation.
2.) When I login at the NIS-Slave and su to root I should get the
NIS-maps without any problems.
But the following is happen (as an example):
NIS-Slave>ypxfr -a d passwd.byname
ypxfr: bind_to_server clnt_call error: RPC: Timed out
The NIS-map is allways updated but it takes a long time.
Here are the processes at the NIS-Master:
PID /usr/sbin/ypbind -s -S swlnis,NIS_MASTER,NIS_SLAVE
PID /usr/sbin/rpc.yppasswdd /var/yp/src/passwd -m passwd DIR= /var/yp/src
PID /usr/sbin/ypserv -a d
PID /usr/sbin/rpc.yppasswdd /var/yp/src/passwd -m passwd DIR= /var/yp/src
PID /usr/sbin/ypxfrd
There are always two yppasswdd's, but I think that's ok.
The processes at the NIS-SLAVE are:
PID /usr/sbin/ypserv -a d
PID /usr/sbin/ypbind -s -S swlnis,NIS_SLAVE,NIS_MASTER
The call 'rpcinfo -p NIS_MASTER' gives:
100004 2 udp 995 ypserv
100004 2 tcp 996 ypserv
100004 1 udp 995 ypserv
100004 1 tcp 996 ypserv
100007 2 tcp 1003 ypbind
100007 2 udp 1005 ypbind
100007 1 tcp 1003 ypbind
100007 1 udp 1005 ypbind
100009 1 udp 999 yppasswdd
100069 1 udp 604 ypxfrd
100069 1 tcp 606 ypxfrd
and 'rpcinfo -p NIS_SLAVE' gives:
100004 2 udp 896 ypserv
100004 2 tcp 897 ypserv
100004 1 udp 896 ypserv
100004 1 tcp 897 ypserv
100007 2 tcp 903 ypbind
100007 2 udp 905 ypbind
100007 1 tcp 903 ypbind
100007 1 udp 905 ypbind
I haven't changed the NIS-configuration neither at the Master nor at the
Slave
after the upgrade.
I searched the archive and found nearly the same question without an answer.
After contacting the people he wrote that he still lives with the 'yppasswd' problem
and that it also exist after a freshly install of version 5.1A.
Is there someone out who can give me a hint for this problem?
Any help is wellcome and I'll give a summary.
Yours sincerely
Norbert
--
Norbert Kasperczyk-Borgmann
Hochschule fuer Angewandte Wissenschaften Hamburg
- Hamburg University of Applied Sciences -
Fachbereich E/I, Softwarelabor, Raum 1186 Berliner Tor 7
D-20099 Hamburg, Germany
phone: +49 40 42875-8417 fax : +49 40 2803770
email: nkb_at_informatik.haw-hamburg.de
Received on Tue Mar 25 2003 - 15:12:24 NZST