[389-users] Re: 389 console is blank

Okay, I think you should remove the o=netscaperoot backend, and rerun the register script.   It's not finding your domain ou=northshore.edu in o=netscaperoot First remove the suffix and database configuration:

[389-users] Re: 389 console is blank

Can you provide the Directory Server's access log (/var/lod/dirsrv/slapd-YOUR_INSTANCE/access) content from the time you ran the register script? Worse case scenario, you can delete o=netscaperoot, and run the script again and it will create it from scratch.  Since your setup is corrupted

[389-users] Re: 389 console is blank

Hi Again, Tried running the register script and we are getting an error message that states "failed to register the configuration server info to the Configuration Directory Server..." (Screenshot below). Any ideas? [image: image.png] Cassandra Reed 978-762-4222 EDP Systems Analyst III North

[389-users] Re: 389 console is blank

:-)  There is no downtime it just does a bunch of ldapmodifies to add the o=netscapeoot suffix.  You might need to restart the admin server, but not DS. Here are some useful links:

[389-users] Re: 389 console is blank

Output it much better after including -x, screenshot below. If we run the register-ds-admin, will there be any downtime to the server? I just need to confirm that this will not affect the userroot database in any way, since classes start next week and I value my job :) [image: image.png]

[389-users] Re: 389 console is blank

Hey All, So if you haven't figured it out today Cassie and I work together and double team this environment. I ran the following and did get a response back. ldapsearch -D "uid=onecampus,ou=Tools,dc=northshore,dc=edu" -w "northshore-2018" -H ldap://389ds1.northshore.edu:389 -x -b

[389-users] Re: 389 console is blank

On 08/30/2018 03:35 PM, Cassandra Reed wrote: Thanks, Mark.  When executing the ldapsearch that you suggested, I am getting an error message: ldap_sasl_interactive_bind_s: Unknown authentication method (-6) additional info: SASL(-4): no mechanism available: Ugh sorry you need to add -x:

[389-users] Re: 389 console is blank

Thanks, Mark. When executing the ldapsearch that you suggested, I am getting an error message: ldap_sasl_interactive_bind_s: Unknown authentication method (-6) additional info: SASL(-4): no mechanism available: We have been replicating o=netscaperoot - I am not sure how up to date the replicas

[389-users] Re: 389 console is blank

On 08/30/2018 03:07 PM, Cassandra Reed wrote: Hi Mark, You are correct, it does appear that the o=netscaperoot suffix was removed. No, I think it's still there.  Try this search:     # ldapsearch -D "cn=directory manager" -W -b o=netscapeoot objectclass=* dn Maybe try restarting the