Restart the Directory Server.This should solve the issue.
/opt/SUNWdsee/ds6/dsadm stop /var/opt/SUNWdsee/dsins1
/opt/SUNWdsee/ds6/dsadm start /var/opt/SUNWdsee/dsins1
If Directory Server is hanged, the following message is displayed: "Waiting for server to stop...." After some time, the following message is displayed: "Server still running!! Failed to stop the ns-slapd process: process-ID" In this case, you need to kill the process and restart Directory Server.
kill -9 process-ID
/opt/SUNWdsee/ds6/dsadm stop /var/opt/SUNWdsee/dsins1
/opt/SUNWdsee/ds6/dsadm start /var/opt/SUNWdsee/dsins1
I do not recommend killing directory server with the -9. Better to wait for the process to finish after you issue the dsadm stop. Most likely it's finishing up with existing client threads and connections. Killing with the -9 (uncatchable by a UNIX process) may result in database corruption.
Posted by TerryG on May 21, 2008 at 04:39 AM PDT #
Thanks a lot for the information. But I am sure that Directory Server is hanged and even after waiting for hours i did not get any other messages other than "Failed to stop the process." Any idea what went wrong?
Once again, thanks a lot,
Sunil
Posted by Sunil on May 22, 2008 at 04:51 AM PDT #
Killing Directory Server because an application is blocked looks like the wrong way to troubleshoot.
I think it would be more appropriate to figure out what in Convergence login is actually not returning from the directory server!
It's like saying that if you cannot access your home server, reboot it (and forget about all other users and applications).
Posted by Ludo on May 22, 2008 at 08:07 AM PDT #