On 7/21/05, Anders Norrbring <lists@norrbring.se> wrote:
On 2005-07-21 14:19 Markus Natter wrote:
On 7/21/05, Anders Norrbring <lists@norrbring.se> wrote:
Sorry for x-posting, but someone here might have an idea? There are a lot more readers to this list..
On 2005-07-20 19:52 Anders Norrbring wrote:
Hiya all..
I'm trying to do a new installation on i386 with SP2. I boot up from SP2 CD1, and go on as usual. Configuring the CA, choosing LDAP as auth backend, etc, etc..
So far, so good. But then I start configuring things, all well while doing it. But when I reboot, EVERYTHING in the LDAP vanishes, there's not a trace of anything I've done!
Geez.. Is there something I'm missing in the picture? I did a fresh GA installation, modified just tha password settings in the LDAP scheme (max length to 18 and hash blowfish), saved it, rebooted and fine, everything was there.
Then I did a system update to SP2, and not a single LDAP modification is saved anymore! I can set up users, groups, mappings, etc. As long as I don't reboot, the data is in the database when I check with slapcat. Then I reboot, and every change is gone.
Is this just showing up on my system? If so, I must be doing something seriously wrong...
Anders.
Hello Anders,
I do not have such an issue, or at least I haven't met yet until the SLES9 SP2. But I just ask some things, which would lead to an bad db almost every time if not set.. (I assume you are using Berkeley DB as backend..)
1. Do you have switched on the db_recover check on, when starting up LDAP? This can be set in /etc/sysconfig/openldap setting the following option to yes:
OPENLDAP_RUN_DB_RECOVER="yes"
2. In your DB directory /var/lib/ldap, is there a DB_CONFIG file? Its content should somehow look like this:
set_cachesize 0 15000000 1 set_lg_bsize 2097152
A bit apart from DB stuff and just another idea, well I must admit really a bit far away, but if this just occurs on reboot.. are you using a journaled filesystem and maybe having troubles with it, e.g. loosing other filechanges after reboot?
Actually I haven't edited anything from outside YaST, which I presume does take care of things like that for me.
It should do, yes. But you are free to touch something manually and sometimes accidents happen.. ;)
I've reinstalled with SP1 right now, just to verify things, and here the DB_CONFIG looks alright. There is no OPENLDAP_RUN_DB_RECOVER at all in the sysconfig file entry, I can't say if SP2 alters anything, I didn't look there.. I'll do it next time.
well, I've got this option here since SLES9 RC5.. and neither SP! nor SP2 changes something here.. but the openldap2 version (now 2.2.24, due to syncrepl problems) you could try it manually first, like this: db_recover -h /var/lib/ldap But I found another interesting list entry here, which deals with similar ldap cache saving problems: http://www.openldap.org/lists/openldap-software/200412/msg00085.html markus