NIS+ des errors

NIS+ des errors

Post by rwrya » Fri, 10 Jun 1994 04:52:38



Can anyone shed some light on the inner meaning of the following
NIS+ messages;

Jun  5 01:00:37 xxxxx nisd[145]: authdes_refresh: unable to synch up w/server
Jun  4 04:05:01 xxxxx syslog: authdes_validate: verifier mismatch
Jun  6 15:38:21 xxxxx pcnfsd[310]: authdes_validate: verifier mismatch
Jun  6 19:32:03 xxxxx automountd[125]: authdes_validate: verifier mismatch
Jun  7 11:49:39 xxxxx nis_cachemgr: authdes_validate: verifier mismatch
Jun  7 10:09:05 xxxxx authdes_refresh: unable to encrypt conversation key

Robert

--
Robert W. Ryan Chemical Bank 270/277 Park Avenue NY, NY 10172

 
 
 

NIS+ des errors

Post by Alexander Dauenstein » Wed, 15 Jun 1994 01:04:11


: Can anyone shed some light on the inner meaning of the following
: NIS+ messages;
:  
: Jun  5 01:00:37 xxxxx nisd[145]: authdes_refresh: unable to synch up w/server
: Jun  4 04:05:01 xxxxx syslog: authdes_validate: verifier mismatch
: Jun  6 15:38:21 xxxxx pcnfsd[310]: authdes_validate: verifier mismatch
: Jun  6 19:32:03 xxxxx automountd[125]: authdes_validate: verifier mismatch
: Jun  7 11:49:39 xxxxx nis_cachemgr: authdes_validate: verifier mismatch
: Jun  7 10:09:05 xxxxx authdes_refresh: unable to encrypt conversation key
:  
: Robert

: --
: Robert W. Ryan Chemical Bank 270/277 Park Avenue NY, NY 10172

Unfortunately I don't have an answer but I can report similar problems on our
system. Errors like these are collected in /var/adm/messages  and f*ck up my
/var.

Any hints? Patches?

Alex

 
 
 

1. Redhat 7.3 NIS errors (Internal NIS error)

Hello.

I am running NIS on a newly installed RedHat 7.3 box. Originally, I
had the box running as a YP slave. The YP master is a Sun box running
Solaris 2.7. About two weeks after I installed 7.3, I occasionally get
these errors in the logs:

Jul 16 23:09:55 butthead amd[26613]: nis_isup: error getting the order
of map amd.raid_home: Internal NIS error
Jul 16 23:09:55 butthead amd[26613]: nis_isup: error getting the order
of map amd.net: Internal NIS error
Jul 16 23:09:55 butthead amd[26613]: nis_isup: error getting the order
of map amd.lab: Internal NIS error

When this happens, users get kicked off and can't login because the
machine is not getting the passwd map from the master. I don't believe
this has anything to do with amd, just that amd is the only thing
complaining. The one time I caught it having this problem, I noticed
that when I did `ypcat passwd`, the passwd file
was coming from another NIS master in the subnet that serves a
different NIS domain. I shutoff ypserv and let it bind to the
ypmaster. Initially, that worked, but the problem surfaced again.
The problem usually clears itself after a short period of time.

I am guessing there is some problem with ypbind. This machine is the
only one in the affected NIS domain that is running Redhat 7.3. None
of the other machines are having any problem. However, I just recently
setup the other NIS master (also Redhat 7.3) serving another NIS
domain, so maybe this is causing some problems.The affected machine
used to run Redhat 6.2, and there were no problems with that setup.

Anyone have any ideas on how to troubleshoot this?

Thanks.

Peter.

2. Execute a script, when logout from kde

3. Un editeur qui pond/lit des .DOC pour bouffer des parts de marché à Bill

4. mouse trails in X

5. des timestamp in nis+

6. Change blocksize of SCSI tape unit?

7. NIS+ Des credentials encoding/decoding (C programming)

8. SunOS 4.1.4

9. Giving a user DES credentials under NIS+

10. NIS+ question (LOCAL, DES)

11. NIS+ credentials -- system call to des crypt private key

12. NIS+ without DES

13. (nis+ lookup): Error in accessing NIS+ cold start file