In case where the Directory Server appears to be hang try to run a
monitor search ...
if you get a error something like "cant contact directory server"
please check the following ...
The ulimit settings on the system might not allow the Directory Server
to accept connections beyond the default settings.
To see the current settings please run ulimit -a command
Sample output of the command ..
bash-2.05a# ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max memory size (kbytes, -m) 32768
open files (-n) 256
pipe size (512 bytes, -p) 64
stack size (kbytes, -s) 32768
cpu time (seconds, -t) unlimited
max user processes (-u) 262144
virtual memory (kbytes, -v) unlimited
notice the open files (-n) which is 256 this means that the maximum
files a process can open is 256 now a socket also has a file
descriptor so our connections will be limited upto 256.
If your open files ulimit -n is too small and you have the required
system access you might want to change the ulimit -n settings ...
One can change the ulimit settings as ... ulimit -n 1024
Thanks,
Sujay.
-- C
You can find the ITDS support site here, including links to download the
current fixpack level:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMDirectoryServer.html
John