July 25, 2008 07:13pm pdt

1. adrpo 2,000
1. shivaspk 2,000
3. gheist 750
3. Syngin9 750
5. Smart_Man 340
6. johnsone 332
6. fridom 332
6. sdstuber 332
6. sujith80 332
6. dbmullen 332

1. fridom 21,532
2. slyong 2,500
3. jdfox 2,000
3. Lowfatsp... 2,000
3. shivaspk 2,000
3. outerJoin 2,000
3. melanikaya 2,000
3. cbunner 2,000
3. irefay 2,000
3. adrpo 2,000
11. nrohan 1,530
12. kalosi 875
13. gheist 750
13. Syngin9 750
15. catbutt 525

07.29.2005 at 04:34PM PDT, ID: 21509692

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0

LDAP and BDB fail after reboot

Zone: Berkeley DB

Tags: environment, version, requires

This has happened to me twice now, having rebuilt the machine in between.

I'm running SuSe 9.3, with a minimal system to start with as I wanted to build in services one by one. The first, so I can get users logging in, was LDAP. So I selected OpenLDAP 2.2.23 during installation and it selected BDB 4.3..27 as a dependency.

I carefully got it to work, and managed to get a client machine to use the LDAP service to log a user in no problem. I have not consciously done any software changes, just configuration changes and the vast majority of those, with the exception of configuring /etc/openldap/slapd.conf and ldapadd-ing the root of the LDAP tree, in YAST.

But then I rebooted the LDAP server machine and it all fails. Trying to start slapd afterwards (again through the YAST runlevel editor) and investigating logs I get the following:

Jul 30 00:10:20 server3 slapd[7387]: @(#) $OpenLDAP: slapd 2.2.23 (Mar 19 2005 20:43:26) $ abuild@salam:/usr/src/packages/BUILD/openldap-2.2.23/servers/slapd
Jul 30 00:10:20 server3 slapd[7387]: bdb_back_initialize: Sleepycat Software: Berkeley DB 4.3.27: (June 1, 2005)
Jul 30 00:10:20 server3 slapd[7387]: bdb_db_init: Initializing BDB database
Jul 30 00:10:20 server3 slapd[7388]: bdb(dc=mydomain,dc=co,dc=uk): Program version 4.3 doesn't match environment version
Jul 30 00:10:20 server3 slapd[7388]: bdb_db_open: dbenv_open failed: DB_VERSION_MISMATCH: Database environment version mismatch (-30974)
Jul 30 00:10:20 server3 slapd[7388]: backend_startup: bi_db_open failed! (-30974)
Jul 30 00:10:20 server3 slapd[7388]: bdb(dc=mydomain,dc=co,dc=uk): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem
Jul 30 00:10:20 server3 slapd[7388]: bdb(dc=mydomain,dc=co,dc=uk): txn_checkpoint interface requires an environment configured for the transaction subsystem
Jul 30 00:10:20 server3 slapd[7388]: bdb_db_destroy: txn_checkpoint failed: Invalid argument (22)
Jul 30 00:10:20 server3 slapd[7388]: slapd stopped.
Jul 30 00:10:20 server3 slapd[7388]: connections_destroy: nothing to destroy.

Does anyone have any ideas what's going on here? I googled extensively for combinations of some of the key phrases in these log entries but with little success. I'm desperate. I can't make any further headway with getting my system back up and running till I can get LDAP running consistently.

Start your free trial to view this solution

Question Stats

Zone: Database

Question Asked By: jockox3

Solution Provided By: jdfox

Participating Experts: 2

Solution Grade: A

Translate:

Loading Advertisement...

20080236-EE-VQP-29