On Fri, Apr 15, 2005 at 12:09:19PM +0900, Christian Balzer wrote: > This is basically the same as #303826 (why this got classified as normal > and 2.2.23 got pushed into sarge is beyond me).
> I have a LARGE (>60k users) users/mailsettings database in LDAP, > on two identical servers running sarge. > They have been rock stable like that for over a year. > Changes are generated by ldifsort.pl/ldifdiff.pl and then applied with > ldapmodify for a low impact and smooth operation, using ldbm as > backend. > Since the update of slapd in sarge 2 days ago I have been getting > an increasing number of reports of user settings "vanishing" from > the system. As with #303826 a full dump of the DB WILL show that > these records are present, but a specific search for them will fail. > So this hints very much at index corruption of some sort, as a > stop/start of slapd does not change things. However a delete/add > of that entire record tends to fix things and so far it seems only > records that were touched with modify have been affected. > Unfortunately this is not deterministic in the least, while one > slapd instance on one server will happily return the correct data > for a specific query the other one might not or vice versa. > I urge you (in case this can't be fixed in a time frame of 1-2 days) > to back out this "update" and revert to the previous version. The previous version of slapd *also* had corruption issues, and this is the driving reason for putting slapd 2.2 in sarge. Which LDAP backend are you using for this directory? -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
