Jens Ådne Rydland wrote:
recently our LDAP server (CentOS 5.4) got upgraded, so we no longer have
the command fedora-idm-console, but instead have gotten 389-console. The
LDAP service it self works flawlessly, but when trying to open the admin
console it fails with
"netscape.ldap.LDAPException: error result (32); No such object"
Running "service dirsrv-admin status" returns that the admin server is
running, and running 389-console with -D indicates that the server
So, is there some extra configuration needed after upgrading, such as
running setup-ds-admin.pl again?
Yes. You always have to run setup-ds-admin.pl -u
after an upgrade, to
refresh the console information.
Note that 389-ds-base 1.2.2 and 389-admin 1.1.8 and earlier have a bug
in that they do not update the console information properly. If you run
into this problem, you might consider upgrading to 389-ds-base 1.2.3 and
389-admin 1.1.9 which you can find in the testing repo.
If so, where can I look up the
information provided on the initial setup?
This is using 389-ds version 1.1.3, CentOS 5.4, Java 1.6.0 (OpenJDK
Runtime Environment (build 1.6.0-b09))