Unable to log into Directory Console

Question

Hi,
I am using Directory server 5.2.
When I try to login to my directory console , I keep getting HttpException: Response: HTTP/1.1 500 Server Error . I tried both admin and directory manager. I am sure that my user id, password and port is correct, and the admin server is running. I notice some warnings in the admin server logs, but do not know what to make out of it.
[11/Sep/2004:10:36:11] info ( 6194): successful server startup
[11/Sep/2004:10:36:11] info ( 6194): SunONE-WebServer-Enterprise/6.0SP3 B05/14/2003 17:58
[11/Sep/2004:10:36:11] warning ( 6194): admin40_check_ds_availability_init(): WARNING: Unable to determine the location of the User and Group DS (unable to set User/Group baseDN)
[11/Sep/2004:10:36:11] failure ( 6194): Warning! admin40_task_eval_init(): unable to build User Group Info (unable to set User/Group baseDN)
[11/Sep/2004:10:36:11] failure ( 6194): admin40_host_ip_init(): PSET failure: Failed to create PSET handle (pset error = Authentication failed)
[11/Sep/2004:10:36:11] info ( 6196): Installing a new configuration
[11/Sep/2004:10:36:11] info ( 6196): [LS ls1] http://ldap.mic.com, port 390 ready to accept requests
[11/Sep/2004:10:36:11] info ( 6196): A new configuration was successfully installed
[11/Sep/2004:10:36:12] info ( 6196): Using the Java HotSpot(TM) Server VM v1.4.1_01a from Sun Microsystems Inc.
[11/Sep/2004:10:36:12] info ( 6196): Loading IWSSessionManager by default.
[11/Sep/2004:10:36:12] info ( 6196): IWSSessionManager: Maximum number of sessions is 1000
[11/Sep/2004:10:36:12] security ( 6196): for host 0.0.0.0 trying to GET /, admin40_host_ip_check reports: Unauthorized host ip=0.0.0.0, connection rejected
[11/Sep/2004:10:36:57] security ( 6196): for host ldap. trying to GET /admin-serv/authenticate, admin40_host_ip_check reports: Unauthorized host ip=::ffff:192.168.176.12, connection rejected
Any advice is much appreciated.
Thanks.

Answer 1

here is solution:
Sunsolve.sun.com
Document ID:     75322
Resolution:     Top
The reason you cannot log in to the console is because a password
has expired. That password belongs to the admin-serv-<hostname>
user.  Don't confuse this user with the normal
admin user in LDAP.  Unfortunately, the admin-serv-<hostname>
user is not like the Directory Manager; that is, the password for the
admin-serv-<hostname> user will expire unless you take some
corrective action beforehand, such as adding the user to a group with
passwords that never expire or adding a specific password policy
to the user.
Every time a user (Directory Manager, Admin, and so on) logs in to the
console, the user (admin-serv-<hostname>) needs to successfully bind
to the directory server.  If the password has expired, that bind cannot
happen.
To find the user (admin-serv-<hostname>), perform the following steps.
Step 1:  Locate the User With the Expired Password
Search for the user (admin-serv-<hostname>) using the following
syntax as an example:
root/edog# ldapsearch -D "cn=Directory Manager" -w <password> -h <hostname>
-p <port> -b o=netscaperoot "cn=admin-serv-*"
The following provides an example of an search for the user:
   root/edog# ldapsearch -D "cn=Directory Manager" -w dirmanager -b
   o=netscaperoot cn=admin-serv-edog
   cn=admin-serv-edog, cn=Netscape Administration Server, cn=Server Group,
   cn=edog.labnet.east.sun.com, ou=labnet.east.sun.com, o=NetscapeRoot
   objectClass=top
   objectClass=netscapeServer
   objectClass=nsAdminServer
   objectClass=nsResourceRef
   objectClass=groupOfUniqueNames
   cn=admin-serv-edog
   nsServerID=admin-serv
   serverRoot=/usr/iplanet/ds5
   serverProductName=Administration Server
   serverHostName=edog.labnet.east.sun.com
   uniqueMember=cn=admin-serv-edog, cn=Netscape Administration Server,
   cn=Server Group, cn=edog.labnet.east.sun.com, ou=labnet.east.sun.com,
   o=NetscapeRoot
   installationTimeStamp=20021218212731Z
   userPassword={SSHA}kZeUzbMMbisvxMnALP3tjk3KGaNmIb8Ih29ddw==
Step 2:  Manually Change the User's Password
a) Use the Directory Manager to change the user password attribute in
   the following entry (returned by the command in Step 1).
   cn=admin-serv-edog, cn=Netscape Administration Server, cn=Server Group,
   cn=edog.labnet.east.sun.com, ou=labnet.east.sun.com, o=NetscapeRoot
b) Use the ldapmodify command, as in the following example, with a new
   password, such as "abcd1234":
   ./ldapmodify -D "cn=Directory Manager" -w dirmanager -h <hostname> -p
   <port>
   dn: cn=admin-serv-edog, cn=Netscape Administration Server, cn=Server
   Group,
   cn=edog.labnet.east.sun.com, ou=labnet.east.sun.com, o=NetscapeRoot
   changetype:modify
   replace:userpassword
   userpassword: abcd1234
Step 3: Edit the adm.conf File (<server root>/adm-serv/config)
a) Stop the Administration Server:
   ./stop-admin
Now, change the password in the Administration Server's
adm.conf file so it knows to use the new password to bind
to the directory server.
b) Change the directory:
    cd <server root>/admin-serv/config
c) Use the vi text editor in the adm.conf file to find a line that is
   similar to the following:
    siepid:   admin
d) Edit the adm.conf file so the siepid value matches the new password
    that you created Step 2:
    siepid:   abcd1234
e) Start the Administration Server and make certain that you see no
   "PSET failed" errors in the errors log.  These errors indicate that
   there was a problem loading the o=netscaperoot information.
Now, you should have no problem logging into the console.