This is a bit embarrassing. I was playing with a test FDS VM before the Holidays, and am just now getting back to it, and I cannot remember the admin password to get back into the console. How can I reset it?
Currently we are attempting to roll-out some opensuse 11.0 machines
using FDS. When I configure the client, I add the required entries for
server, base dn, users, password, groups. Under advanced configuration
though, There is ConfigurationBase DN. Can someone explain to me what
i see that OpenLDAP has a plugin called yast.schema. However, I am a
bit fuzzy a) does FDS need some sort of plugin to allow us to use the
Configuration Base DN, and b) What exactly is it used for. The
Opensuse docs is sort of thin regarding the ldap client.
Can any of you shed a bit of light on this so we can make a decision if
it is something that we would like to use.
if you could give schema examples that would be great.
We have a consumer read only replica at a remote site. We have a Master
read/write replica in our data center.
We have an issue with our referrals or updates failing when we submit
updates to the read only replica from the command line. From the console
if we update the read only replica, it properly refers the update to the
master and the master replicates it back down.
>From the command line however these updates fail and the log shows
I see another post regarding this but no resolution was posted. It
mentions spaces as being an issue??
The referrals field on the read only replica shows as...
The replication agreement is set using SSL/simple or SSL with a binddn
as opposed to SSL certificate based authentication. I mention this
because I am unsure if it impacts the situation or not.
Is there something I am missing? Not sure why the console refers updates
but the command line does not.
This e-mail message and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail message, you are hereby notified that any dissemination, distribution or copying of this e-mail message, and any attachments thereto, is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender and permanently delete the original and any copies of this email and any prints thereof.
ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the Uniform Electronic Transactions Act or the applicability of any other law of similar substance and effect, absent an express statement to the contrary hereinabove, this e-mail message its contents, and any attachments hereto are not intended to represent an offer or acceptance to enter into a contract and are not otherwise intended to bind the sender, Sanmina-SCI Corporation (or any of its subsidiaries), or any other person or entity.
I recently installed Fedora DS 1.1.3 on my system and ran the
setup-ds-admin script with no problems. Everything worked very
well--until I rebooted!
Upon reboot, the directory server refused to start. Below are the
relevant lines from the /dirsrv/slapd-host/errors file:
02/Feb/2009:00:11:33 -0600] - Waiting for 4 database threads to stop
[02/Feb/2009:00:11:33 -0600] - All database threads now stopped
[02/Feb/2009:00:11:33 -0600] - slapd stopped.
[02/Feb/2009:00:12:51 -0600] - Fedora-Directory/1.1.3 B2009.031.2025
[02/Feb/2009:00:13:56 -0600] - Fedora-Directory/1.1.3 B2009.031.2025
[02/Feb/2009:00:14:02 -0600] - slapd started. Listening on All Interfaces
port 389 for LDAP requests
[02/Feb/2009:00:14:24 -0600] - slapd shutting down - signaling operation
[02/Feb/2009:00:14:24 -0600] - slapd shutting down - closing down internal
subsystems and plugins
[02/Feb/2009:00:14:29 -0600] - Waiting for 4 database threads to stop
[02/Feb/2009:00:14:30 -0600] - All database threads now stopped
[02/Feb/2009:00:14:30 -0600] - slapd stopped.
[02/Feb/2009:00:16:07 -0600] - Shutting down due to possible conflicts
with other slapd processes
[02/Feb/2009:00:20:11 -0600] - Shutting down due to possible conflicts
with other slapd processes
And it continues to print "Shutting down due to possible conflicts with
other slapd processes" every single time I try to start the directory
server. No other messages are printed to the error log, all permissions
are OK, and the directory admin server starts with no problem.
Befuddled, I tried re-running the setup-ds-admin script. Again, the
directory server came online and worked perfectly upon completion of that
script, but it failed upon reboot as before.
There are no other LDAP servers running on this machine. A process scan
showed no slapd processes running, and the LDAP port does not have a
process glommed onto it.
Any assistance you can provide would be appreciated!