Kristen, please stay on the mailing list you started the thread. Don't e-mail me solely personally.
Kristen Walker wrote:
Thanks for your help. I can't seem to be able to start the server with the -d flag. Here is what I tried:
su root -c /usr/local/libexec/slapd -d 65535
I also tried:
su root -d 65535 -c /usr/local/libexec/slapd
And it complains in both cases that -d is an invalid option.
Using -d works for me. Which version of OpenLDAP is this?
Can you post any output it produces?
Ciao, Michael.
Kristen, please stay on the mailing list you started the thread. Don't e-mail me solely personally.
Sorry about that.
Kristen Walker wrote:
Thanks for your help. I can't seem to be able to start the server with the -d flag. Here is what I tried:
su root -c /usr/local/libexec/slapd -d 65535
I also tried:
su root -d 65535 -c /usr/local/libexec/slapd
And it complains in both cases that -d is an invalid option.
Using -d works for me. Which version of OpenLDAP is this?
Can you post any output it produces?
I am using openldap-2.3.39 on Ubuntu.
Here is the output:
su root -d 65535 -c /usr/local/libexec/slapd su: invalid option -- d Usage: su [options] [LOGIN]
Options: -c, --command COMMAND pass COMMAND to the invoked shell -h, --help display this help message and exit -, -l, --login make the shell a login shell -m, -p, --preserve-environment do not reset environment variables, and keep the same shell -s, --shell SHELL use SHELL instead of the default in passwd
Thanks, Kristen
-- Kristen Walker
Digital Media Resources Developer Instructional Media Services Santa Barbara County Education Office 4400 Cathedral Oaks Road P.O. Box 6307 Santa Barbara, CA 93160-6307 (805)964-4711 ext. 5244/FAX (805)683-3597 kwalker@sbceo.org http://www.sbceoportal.org
su root -c "/usr/local/libexec/slapd -d 65535"
--Quanah
--On August 14, 2008 4:03:24 PM -0700 Kristen Walker kwalker@sbceo.org wrote:
Kristen, please stay on the mailing list you started the thread. Don't e-mail me solely personally.
Sorry about that.
Kristen Walker wrote:
Thanks for your help. I can't seem to be able to start the server with the -d flag. Here is what I tried:
su root -c /usr/local/libexec/slapd -d 65535
I also tried:
su root -d 65535 -c /usr/local/libexec/slapd
And it complains in both cases that -d is an invalid option.
Using -d works for me. Which version of OpenLDAP is this?
Can you post any output it produces?
I am using openldap-2.3.39 on Ubuntu.
Here is the output:
su root -d 65535 -c /usr/local/libexec/slapd su: invalid option -- d Usage: su [options] [LOGIN]
Options: -c, --command COMMAND pass COMMAND to the invoked shell -h, --help display this help message and exit -, -l, --login make the shell a login shell -m, -p, --preserve-environment do not reset environment variables, and keep the same shell -s, --shell SHELL use SHELL instead of the default in passwd
Thanks, Kristen
-- Kristen Walker
Digital Media Resources Developer Instructional Media Services Santa Barbara County Education Office 4400 Cathedral Oaks Road P.O. Box 6307 Santa Barbara, CA 93160-6307 (805)964-4711 ext. 5244/FAX (805)683-3597 kwalker@sbceo.org http://www.sbceoportal.org
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Okay, progress . . .
su root -c "/usr/local/libexec/slapd -d 65535"
Thanks so much, this command worked!
From the output, this looks like the interesting part:
bdb_db_open: dc=example,dc=com bdb_db_open: Warning - No DB_CONFIG file found in directory /usr/local/var/openldap-data: (2) Expect poor performance for suffix dc=example,dc=com. bdb_db_open: dbenv_open(/usr/local/var/openldap-data) bdb(dc=example,dc=com): Ignoring log file: /usr/local/var/openldap-data/log.0000000001: magic number 0, not 40988 bdb(dc=example,dc=com): Invalid log file: log.0000000001: Invalid argument bdb(dc=example,dc=com): PANIC: Invalid argument bdb(dc=example,dc=com): PANIC: DB_RUNRECOVERY: Fatal error, run database recovery bdb_db_open: Database cannot be opened, err -30978. Restore from backup! ====> bdb_cache_release_all bdb(dc=example,dc=com): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem bdb(dc=example,dc=com): txn_checkpoint interface requires an environment configured for the transaction subsystem bdb_db_close: txn_checkpoint failed: Invalid argument (22) backend_startup_one: bi_db_open failed! (-30978)
If anyone can tell me how I can recover from this, I will do back flips. I don't care about throwing the whole database away at this point and starting over. I have re-installed openldap but continue to have this problem.
Thanks so much and sorry for my faux pas on the list and my extreme newbie-ness - I sincerely appreciate the help I have gotten from this list and would not have gotten this far without it.
-Kristen
--Quanah
--On August 14, 2008 4:03:24 PM -0700 Kristen Walker kwalker@sbceo.org wrote:
Kristen, please stay on the mailing list you started the thread. Don't e-mail me solely personally.
Sorry about that.
Kristen Walker wrote:
Thanks for your help. I can't seem to be able to start the server with the -d flag. Here is what I tried:
su root -c /usr/local/libexec/slapd -d 65535
I also tried:
su root -d 65535 -c /usr/local/libexec/slapd
And it complains in both cases that -d is an invalid option.
Using -d works for me. Which version of OpenLDAP is this?
Can you post any output it produces?
I am using openldap-2.3.39 on Ubuntu.
Here is the output:
su root -d 65535 -c /usr/local/libexec/slapd su: invalid option -- d Usage: su [options] [LOGIN]
Options: -c, --command COMMAND pass COMMAND to the invoked shell -h, --help display this help message and exit -, -l, --login make the shell a login shell -m, -p, --preserve-environment do not reset environment variables, and keep the same shell -s, --shell SHELL use SHELL instead of the default in passwd
Thanks, Kristen
-- Kristen Walker
Digital Media Resources Developer Instructional Media Services Santa Barbara County Education Office 4400 Cathedral Oaks Road P.O. Box 6307 Santa Barbara, CA 93160-6307 (805)964-4711 ext. 5244/FAX (805)683-3597 kwalker@sbceo.org http://www.sbceoportal.org
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
-- Kristen Walker
Digital Media Resources Developer Instructional Media Services Santa Barbara County Education Office 4400 Cathedral Oaks Road P.O. Box 6307 Santa Barbara, CA 93160-6307 (805)964-4711 ext. 5244/FAX (805)683-3597 kwalker@sbceo.org http://www.sbceoportal.org
Kristen Walker wrote:
If anyone can tell me how I can recover from this, I will do back flips. I don't care about throwing the whole database away at this point and starting over.
Just remove all files from directory /usr/local/var/openldap-data/ except file DB_CONFIG.
BTW: You should also check ownership and permissions of the files. If slapd is normally started as another user (check the start/stop script normally used) you should not start it as root and let it create the DB files as root.
Ciao, Michael.
Just remove all files from directory /usr/local/var/openldap-data/ except file DB_CONFIG.
I did not have DB_CONFIG anymore, but I copied DB_CONFIG example over and deleted the other files and I now have a working openLDAP directory with over 5700 users as of this morning and I could not be happier! Thanks so much for all your help! This LDAPserver is going to benefit a lot of teachers and students who use Moodle, Elgg, and other tools that we offer.
-Kristen
-- Kristen Walker
Digital Media Resources Developer Instructional Media Services Santa Barbara County Education Office 4400 Cathedral Oaks Road P.O. Box 6307 Santa Barbara, CA 93160-6307 (805)964-4711 ext. 5244/FAX (805)683-3597 kwalker@sbceo.org http://www.sbceoportal.org
I have encountered this error in our event log here. I am using the cygwin version of OpenLDAP v2.3.39-1 with cygdb-4.5 on Windows 2000 This has been working swimmingly for a couple of months now (although restarts automatically every weekend for an import). A user rang me to say that it wasn't working anymore, and Outlook was complaining there was a MAPI error. On further investigation, I saw several attempts to search in the event log:
conn=1986 op=1 SRCH base="cn=wwwww,dc=XXXX,dc=YYYY,dc=ZZZZ" scope=0 deref=3 filter="(objectClass=*)". conn=1986 op=1 SRCH attr=cn commonName mail roleOccupant display-name displayname sn surname co organizationName o givenName legacyExchangeDN objectClass uid mailNickname title company physicalDeliveryOfficeName telephoneNumber. bdb(dc=XXXX,dc=YYYY,dc=ZZZZ): PANIC: fatal region error detected; run recovery. conn=1986 op=1 SEARCH RESULT tag=101 err=80 nentries=0 text=internal error. conn=1986 op=2 UNBIND. conn=1986 fd=25 closed.
from various users, (including myself when I was doing some troubleshooting). Restarting the service (without doing a "run recovery") has cleared this problem. It happened once before I had completely implemented it, but just put it down to a one-off as I was doing a lot of changes.
It sounds like it's a database error rather than an OpenLDAP error as such. Has anyone else encountered this before and knows why it happens?
Thank you,
Chris
openldap-technical@openldap.org
-
Clemson, Chris (IHG) -
Kristen Walker -
Michael Ströder -
Quanah Gibson-Mount