[389-users] Admin-console doesn't work after upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, 
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
indeed replies. 

So, is there some extra configuration needed after upgrading, such as
running setup-ds-admin.pl again? 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))

-- 
mvh Jens Ådne Rydland

--
389 users mailing list
389-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux