I received three responses (Thank you!). All three mentioned this as a
known bug. 2 of the three said the work around was to run keyserv with
the -D (debug) switch. I did this, and instead of sending the output to
/dev/null as suggested I took a look at it. I didn't see anything really
helpful, but seeing the error msg got me thinking about some password
problems we had earlier. On a long shot, I re-created the machine
credentials on the nis+ server with nisaddcred, then did a chkey -p as root
on the machine in question. This seems to have cured the problem for now.
Here is my original question and the replies:
Original -
I am getting an error message of "authdes_seccreate, unable to create
session key" on one of my NIS+ client machines. When I check, keyserv is
not running. After I start it up, it dies almost immediately after the
first successful login. This is on Solaris 2.6
Can anyone shed some light on this? I have tried keyserv -n with no
apparent effect.
Reply #1
Known problem with a current set of libthread.so patches. Workaround it to
start keyserv with the -D option (and I'd advise piping the stderr output to
/dev/null). It is bug 4223881. Sun hasn't gotten back to me with an
official fix yet.
Eugene Choi
Reply #2
Have you installed patch 105568-13? If you have, back it out. This
patch causes keyserv to keep dting.
Matthew Atkinson
Reply #3
We were told by Sun that there is a bug with keyserv. No fix as of yet.
They told us to run keyserv in debug mode. UGH!@(*&^#$(^ It seems to be
working ok for now without toooo much overhead.
Please let me know if you come up with anything else. Thanks for your
time...
Michael Hare
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:24 CDT