I have been running 2 masters for a number of years now. The packages I have installed currently are: 389-admin-1.1.23-1.fc16.x86_64 389-admin-console-1.1.8-2.fc16.noarch 389-admin-console-doc-1.1.8-2.fc16.noarch 389-adminutil-1.1.14-1.fc16.x86_64 389-console-1.1.7-1.fc16.noarch 389-ds-1.2.2-1.fc15.noarch 389-ds-base-1.2.10.2-1.fc16.x86_64 389-ds-base-devel-1.2.10.2-1.fc16.x86_64 389-ds-base-libs-1.2.10.2-1.fc16.x86_64 389-ds-console-1.2.6-1.fc16.noarch 389-ds-console-doc-1.2.6-1.fc16.noarch 389-dsgw-1.1.7-2.fc16.x86_64
The directory service itself has been and is now running fine on both masters. I haven't used 389-console in some time (like seven months). I am able to run 389-console just fine now on one of the masters, but I have a problem on the other master. When I log in I get the error:
Cannot connect to the directory server: netscape.ldap.LDAPException: error result (32): No such object
I know it's not a password problem. I am very sure of the password, and in fact, if I type in something else for the password, I get a different message: Cannot logon because of an incorrect User ID, Incorrect password or Directory problem. HttpException: Response: HTTP/1.1 401 Authorization Required Status: 401 URL: http://XXXX.org:PPPPP/admin-serv/authenticate
I also note that when I do "service dirsrv-admin start", in /var/log/dirsrv/admin-serv/error, I see the unnerving message: [crit] populate_tasks_from_server(): Unable to search [cn=admin-serv-XXXX, cn=389 Administration Server, cn=Server Group, cn=XXXX.org, ou=org, o=NetscapeRoot] for LDAPConnection [XXXX.org:389]
What can I do to run 389-console again?
On 02/29/2012 03:07 PM, Ldap Tester wrote:
I have been running 2 masters for a number of years now. The packages I have installed currently are: 389-admin-1.1.23-1.fc16.x86_64 389-admin-console-1.1.8-2.fc16.noarch 389-admin-console-doc-1.1.8-2.fc16.noarch 389-adminutil-1.1.14-1.fc16.x86_64 389-console-1.1.7-1.fc16.noarch 389-ds-1.2.2-1.fc15.noarch 389-ds-base-1.2.10.2-1.fc16.x86_64 389-ds-base-devel-1.2.10.2-1.fc16.x86_64 389-ds-base-libs-1.2.10.2-1.fc16.x86_64 389-ds-console-1.2.6-1.fc16.noarch 389-ds-console-doc-1.2.6-1.fc16.noarch 389-dsgw-1.1.7-2.fc16.x86_64
The directory service itself has been and is now running fine on both masters. I haven't used 389-console in some time (like seven months). I am able to run 389-console just fine now on one of the masters, but I have a problem on the other master. When I log in I get the error:
Cannot connect to the directory server: netscape.ldap.LDAPException: error result (32): No such object
I know it's not a password problem. I am very sure of the password, and in fact, if I type in something else for the password, I get a different message: Cannot logon because of an incorrect User ID, Incorrect password or Directory problem. HttpException: Response: HTTP/1.1 401 Authorization Required Status: 401 URL: http://XXXX.org:PPPPP/admin-serv/authenticate
I also note that when I do "service dirsrv-admin start", in /var/log/dirsrv/admin-serv/error, I see the unnerving message: [crit] populate_tasks_from_server(): Unable to search [cn=admin-serv-XXXX, cn=389 Administration Server, cn=Server Group, cn=XXXX.org, ou=org, o=NetscapeRoot] for LDAPConnection [XXXX.org:389]
What can I do to run 389-console again?
try running setup-ds-admin.pl -u on both masters
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
389-users@lists.fedoraproject.org