On Tue, Oct 07, 2014 at 01:38:08PM -0700, Ryan Tandy wrote: > On 14-10-07 03:46 AM, Wolfgang Schweer wrote: > >On Tue, Oct 07, 2014 at 10:34:06AM +0200, GALAMBOS Daniel wrote: > >>Do you have olcDbNoSync (or some equivalent setting in the bdb config > >>if you use that) set to true? If olcDbNoSync is set, then it could > >>result in dataloss, else the commited data should remain intact. > >> > >>What backend do you use? > > > >bdb, and yes: dbnosync is set > > I haven't been able to reproduce this, with BDB/HDB/MDB backends and > olcDbNoSync: TRUE. I'm running 'ldapadd -f mods.ldif && reboot' and > mods.ldif contains 10000 small entries. Can you provide any more details > about the steps I should follow to observe the data loss? Debian Edu uses GOsa² to manage user accounts, systems and groups. Adding a system via GOsa² to the (BDB) LDAP database succeeds, using ldapvi one can see the entries in LDAP. Rebooting the system just afterwards results in loss of the added data. Same happens if a user password is set via GOsa². The user password isn't valid after a server reboot. Stopping slapd manually before the reboot doesn't result in data loss. > BTW: As far as I can tell slapd is stopped properly on shutdown; after > rebooting I don't see any log messages about having to recover an unclean > database, or similar. Same here with systemd. > Does Debian Edu usually set olcDbNoSync? As far as I know: yes, since some time slapd.conf contains 'dbnosync'. s/dbnosync/#dbnosync/ avoids the described data loss. For testing I switched from systemd to sysvinit: same effect, same workarounds succeed to keep newly added data. One difference, though: under sysvinit there is no proper slapd stop during shutdown. Wolfgang
Attachment:
signature.asc
Description: Digital signature