On Tue, 2006-01-10 at 17:19 +0800, JM Ibanez wrote:
> On 1/10/06, Glenn Remot <[EMAIL PROTECTED]> wrote:
> >
> > i'm using openldap on top of RHEL 4 and FreeBSD 5.3 and i experienced
> > the problem on both.
> > my encounters were from a simple password changing to adding an entry.
> > Hardware issues pertinent to processor and ram would be unlikely. I'm
> > using RHEL 4 on top of an HP blade G2, 2.4 GHz w/ 1G RAM and the BSD on
> > a lowly P3 600 w/ 256 MB ram. Right now, my eyes are on disabling
> > replication and see if it has got something to do with it...or maybe Perl?
> >
> 
> This is a side issue: considering that BDB is built so that it is safe
> when accessed by multiple processes (but not multiple users--
> permission issues come up etc., as evidenced by Subversion's use of
> BDB), maybe you had a lock issue? Not a db corruption issue?
> 

Actually, it is safe only until one copy of the DbEnv on either process
changes, and then tries to commit the changes while another process is
maintaining a stale/old/broken environment (or DB handle), and then
tries to sync it after the other process cleans up successfully.

If you're using the same DbEnv on either process (which is almost
impossible without using icky System V IPC mechanisms i.e. shared
memory) or threads, then you enjoy the thread-safeness of the
transactional BerkeleyDB backends. Otherwise, if you have multiple
processes changing the same database at any given time, then you're
bound to experience DB corruption in even very simple cases.

> IN any case, you might like to try recovering the BDB environment
> using the BDB tools?
> 

This may be done only when no other process is holding a lock/handle on
the BDB environment -- which means you have to kill all the processes
that use that environment. Hardly a good administrative day anytime that
happens.

-- 
Dean Michael C. Berris
Mobile +639287291459
URL http://mikhailberis.blogspot.com
YMID: mikhailberis

_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph

Reply via email to