On Tue, Oct 14, 2014 at 09:33:56PM +0200, Wolfgang Schweer wrote: > On Tue, Oct 14, 2014 at 08:43:07AM -0700, Ryan Tandy wrote: > > > I have a main-server installed now, however I still have not > > encountered any instances of LDAP changes being lost. > > Thanks for investigating. It's really weird: After installing a main > server with a method similar to the one you've used, I'm unable to > reproduce the data loss. And I can't figure out why it failed before > (main server installed sept 14th) and not now. > > > (In case it matters: this particular tjener is a virtualbox VM.) > > Same here. After Debian Edu got a report from a user who wasn't able to log in with another user account than 'first user', I investigated this issue again. Main server installed as virtualbox VM, dbnosync set in /etc/ldap/slapd.conf: 1) As first user: create a new account, set password. 2) Log out of the gui, log in as the new user. Works. 3) Poweroff the VM (aka main server power loss?). 4) Start VM again and log in as the new user. Fails. Repeat these steps with dbnosync disabled. Login as new user works. Using 'Shutdown via ACPI event' (or similar, translated from German) instead of 'Poweroff' in 3) or rebooting the main server inside of the VM: No data loss with dbnosync enabled. (For some reason data loss occured in this case in the previous installation.) So I guess that there's no slapd bug but Debian Edu is better off to go with dbnosync disabled to avoid data loss in rare cases. Wolfgang
Attachment:
signature.asc
Description: Digital signature