Thanks for replying Mark, The admin server was running in another datacenter and unfortunately it has gone away. The server that went away had all of my Ldap servers registered to it and was my single pane of glass to managing all of my other servers in other datacenters. So I am trying to get all of the existing LDAP servers registered to another server. Here are the processes that are running on the server that I want to register all of my LDAP servers too: ~ # ps -ef | grep -E "admin|slap" | grep -v grep root 2175 1 0 11:39 ? 00:00:00 /usr/sbin/nss_pcache 393220 off /etc/dirsrv/admin-serv root 2176 1 0 11:39 ? 00:00:01 /usr/sbin/httpd.worker -k start -f /etc/dirsrv/admin-serv/httpd.conf root 2181 2176 0 11:39 ? 00:00:00 /usr/sbin/httpd.worker -k start -f /etc/dirsrv/admin-serv/httpd.conf ldapuser 2182 2176 0 11:39 ? 00:00:00 /usr/sbin/httpd.worker -k start -f /etc/dirsrv/admin-serv/httpd.conf ldapuser 31881 1 11 10:10 ? 01:22:39 ./ns-slapd -D /etc/dirsrv/slapd-super-name-01 -i /var/run/dirsrv/slapd-super-name-01.pid -w /var/run/dirsrv/slapd-super-name-01.startpid ~ # While not having a "o=NetscapeRoot" its is definitely up and resolving authentication requests. I thought that "setup-ds.pl" was used to set up the directory server and the "setup-ds-admin.pl" script was for setting up the admin server. It has been a long time since I have set up server. Basically I want to set up a new single pane of glass to manage all of my existing LDAP servers. Would I use the "setup-ds.pl -u" to achive that? Just run it on all of my existing LDAP servers? Would I still need to manually edit the /etc/dirsrv/admin-serv/adm.conf file on all existing servers since the "ldapurl" is still pointing to now non-existing server? Example of current setting in all of the existing adm.conf files: ldapurl: ldap://now-nonexistent-server.my.domain.com:389/o=NetscapeRoot Thank you again for your help! _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
