SUMMARY: SDS problems
Robert Glover
I had only one reply from Graham Shedd regarding that the first problem. He
reported s similar problem in another application, due to the order of
starting the various processes in /etc/rc2.d. I have done some testing on
the startup order, so far without success. I have a feeling it may have more
to do with the number and order of the files in the
/opt/SUNWconn/license_dir than anything else.
In the meantime I have discovered that the dsservd process on our machine
grows in size by approximately 11 megabytes a day. Eventually you need to
reboot to get all the memory back.
Anyway I have reported all these problems to Sun support so will wait and
see if they can come up with any solutions.
Thank you
Rob Glover
> -----Original Message-----
>
>We have an E250 with Solaris 7 and Sun Directory Services 3.1
>installed with current patches.
>We have a 100,000 directory entry license installed for the
>SDS. We have about 7700 users.
>2 problems have arisen. The first problem has been logged as a
>fault with Sun but they haven't come back yet.
>Perhaps someone out there has seen something similar.
>
>1. When the E250 is rebooted it comes up normally with the
>Directory Services daemons starting and shortly after the
>License Manager and then about 30 seconds later dsservd dies.
>The messages file starts to show messages like "too many
>directory entries" and "you need a licence". Stopping and
>restarting the License Manager and then restarting dsservd
>will eventually get the server going again although it
>sometimes takes 2 or 3 goes to get dsservd to keep running. It
>will then be OK until rebooted again.
>We have about 22000 directory entries so are a long way from
>exceeding the license.
>
>2. About once a fortnight users are unable to change their
>passwords using the NIS gateway passwd command. The command
>takes a long time and then times out without changing the
>password. Examination of the problem shows that there are two
>dsyppasswdd processes running - the original one from when the
>machine was rebooted and another one. The second (new) one
>cannot be killed as it respawns, so it is necessary to kill
>both processes and then restart dsyppasswdd from the command
>line. Things are then back to normal for another week or two
>when it happens again.
>
>Any help greatly appreciated. Of course will summarise.
>
>Regards
>Rob Glover
>Unix System Administrator
>Western Australian Police Service
>r_gl...@wapol.gov.au