Hi,

I'm using openLDAP server with berkeley sleepycat as dabase backend with
more than 150GBytes of information.

I'm having some problems when I'm adding information to LDAP server and
the connection suddenly went down despite net failure or other similar
problem.

After that, I supect that the database backend becomes
innacessible/corrupt????

If I try to access the ldap server using for example LdapBrowser the
server doesn't response and is like it didn't exist.

When I go to the linux server I check the slapd process and it is up.
I stop the ldap server process and restart it in debug mode with "slapd -d
-1". It starts normaly without any errors messages.
But if I go to the LdapBrowser it appears that the server doesn't exist
and my application doesn't work properly.

1 - The first attempt to restart correctly the LDAP server I need to
remove the last log files and restart the service slapd.

If I do this the ldap server starts to response and everything seems to go
right BUT if I consult the last node inserted the service went down again.

2 - The second attempt I try to recover the Database backend with
db_recover command but doesn't succed and takes a long time.

3 - The thirth attempt I backup the Ldap server with slapdcat command to a
file and then slapadd command from the same file. That is the only
solution that gives

me the system correctly recover and running properly, but the last node is
lost during this proccess. This proccess takes much time and the server is
down during

that time.

4 - The forth attempt that I haven't try this but I read in some foruns
and that is possible to go to the id2entry.bdb with an editor and truncate

last non-multiple block. Restart the service and it seems to starts
correctly.

I know that openLDAP doesn't have transactions. 

A - Is there anyway of workaround this limitation during runtime
insertions to avoid corruption?

B - Or is there any easier way of recovering the DB if this problem
occours?

Thks in advance and for your pacience

Ricardo Ferreira

[EMAIL PROTECTED]


---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the 
SUBJECT of the message.

Reply via email to