[389-users] Re: Need to re-register 389ds servers

On 06/06/2017 11:16 AM, wudadin2003@gmail.com wrote:
> Mark,
> Ok, I ran the new register-ds-admin.pl -u command on the LDAP server that I wish to be the new single pane of glass config server but it looks like it is not able to clean up the old config
> or maybe it is failing to connect to the localhost that the script is running on.
>
> Can I delete everything in /etc/dirserv/admin-serv and just recreate it without hurting or destroying the current running LDAP database located in /etc/dirserv/slapd-my-server-01 ?
Do NOT do that. It will hose your admin server.
> [root@my-server-01 ldap]# register-ds-admin.pl -ddd -u
These options do not do anything, just run "register-ds-admin.pl"
> Beginning registration of the Directory Server
> ==============================================================================
> The Directory Server locates its configuration file (dse.ldif) at /etc/dirsrv/slapd-ID, by default. If you have Directory Server(s) which configuration file is put at the other location, you need to input it to register the server.
>
> If you have such Directory Server, type the full path that stores the configuration file.
>
> If you don't, type return.
> [configuration directory path or return]:
>
>
> ==============================================================================
> Candidate servers to register:
> /etc/dirsrv/slapd-my-server-01
>
> ==============================================================================
> Do you want to use this server as Configuration Directory Server?
>
> Directory server identifier: my-server-01
>
> ==============================================================================
> Cleaning up old Config DS:
>
> ==============================================================================
> Please input the password for the Administrator User uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot:
> +++Attempting connection to my-server-01.my.domain.com:389 certdir configdir /etc/dirsrv/admin-serv
> Error: failed to clean up the configuration info from the old Configuration
Why is this failing? Check the access logs.

Is there even an admin server(o=netscaperoot) on this system?

I think you should try the silent install file as described on the wiki
page, instead of the interactive mode. It will make this easier to
troubleshoot, but I suspect you are running the script on an instance
without an admin server, or you are using the wrong admin password.
Either way the access log will tell us what went wrong.

> Directory Server .
>
> ==============================================================================
> Please input the password for the Administrator User uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot:
> [root@my-server-01 ldap]#
>
> Thanks!
> _______________________________________________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org