So, if the backend indicates it, slapd write the the modification to the
replog. What kind of logging do you have turned on?

:wes

On 2/20/02 9:45 PM -0700 asparks@quris.com wrote:

Well, I've rebuilt the database many times... still chronically fails.
Removed slurpd.status before, also. I don;t think the problem is in
slurpd anyway -- shutting slurpd off and watching the replogs show no
change logs getting written. Until I restart slapd, that is.
-Alan

wes@umich.edu wrote:

Just a guess, but when I get systemic problems like this, I generally
have to rebuild the DB. Is it possible that your slurpd.status is
getting corrupted?

:wes

On 2/20/02 6:31 PM -0700 asparks@quris.com wrote:

> Still running 1.2.13, cuz of feature probs going to 2.0.x. Beside the
> point.
>
> I've been having a major problem with my master server on Solaris 7
> just stopping replication. It appears that the slapd accepts
> modifications, but just doesn't write them to the replog. A restart
> of the server clears the problem for a while, until it recurs in a day
> (or less).
>
> Has anyone had any experience with this happening, and found a
> solution?
>
> Compiled with GCC 2.95.2, with the following options:
> CPPFLAGS="-I/usr/local/include" \
> LDFLAGS="-L/usr/local/lib" \
> LIBS="-lgnuregex -lpthread -lposix4" \
> ./configure \
> --prefix=/opt/ldap \
> --with-threads \
> --enable-shared \
> --enable-phonetic \
> --enable-shell
>
> Thanks in advance for any advice.
> -Alan
>
> --
> Alan Sparks, Sr. UNIX Administrator asparks@quris.com
> Quris, Inc. (720) 836-2058