> This generally indicates a permission issue. If, for example, you run
slapd as root and then later try to run it as another user, or if you change what user you're running slapd as, you need to change the ownership of all of the files in /var/lib/ldap to match the user you're running slapd as.
It's strange, yes, some files are created by openldap user, while others are root's. However, I don't know, why should slapd have any problems with root's files. We run slapd by custom script (because of bug 416272), that contains just /usr/bin/slapd, thus it should run as root, shouldn't? And we met the problems also when running slapd manually from root's console.
All in all, I'd expect, that problems with file permissions should the slapd report in meaningful way, not the "database is corrupted" one.
Could you check and see if that's the problem that you're having? (And was this also the source of the problem you reported in #416272, to which I just responded?)
I'll try, however this is a production system, it's quite hard to stop slapd. I'll try building other machine and moving the files there to see. Probably in next 2 weeks.
Sincerely Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
