Replication fails: id2entry.db4 too large?

[Luigi Santangelo]

Hi,
I have configured two server (called A and B) in replica multimaster mode.
Server B is in read only mode. In server A I have configured
succesfully replication to B of my userRoot.

Today, the sync doesn't work: when A try to send replication data to
B, B crashes with no error log.
When I start the service on B, it works fine until the sync starts. If
I disable the syncronization, B works fine.

The problem could be the dimension of id2entry.db4? Now it is 10GB and
in the DB I have only 100.000 entry.
Can I reduce the dimension of the file? It seems too large for the
number of records inside.

Thanks in advance.
Best regards.

Luigi

[Rich Megginson]

On 03/05/2013 06:38 AM, Luigi Santangelo wrote:
> Hi,
> I have configured two server (called A and B) in replica multimaster mode.
> Server B is in read only mode. In server A I have configured
> succesfully replication to B of my userRoot.

What is the platform for A and B?  What are the 389-ds-base versions on 
A and B?
> Today, the sync doesn't work: when A try to send replication data to
> B, B crashes with no error log.

What about A?  Any clues in the A errors log?
> When I start the service on B, it works fine until the sync starts. If
> I disable the syncronization, B works fine.

Do you have any core dumps/stack traces?
http://port389.org/wiki/FAQ#Debugging_Crashes
> The problem could be the dimension of id2entry.db4? Now it is 10GB and
> in the DB I have only 100.000 entry.
> Can I reduce the dimension of the file? It seems too large for the
> number of records inside.

Let's see a stack trace first.
> Thanks in advance.
> Best regards.
> Luigi
>
> 389 users mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/389-users

[Luigi Santangelo]

> What is the platform for A and B?  What are the 389-ds-base versions on A
> and B?

A and B are Red Hat Enterprise Linux Server release 5.5 (Tikanga);
389-ds-base are 389 Directory Server version 1.2.5
> What about A?  Any clues in the A errors log?

The service is online, we have disabled the sycn process and then we
can't reproduce  the problem now.
> Do you have any core dumps/stack traces?
> http://port389.org/wiki/FAQ#Debugging_Crashes

No, we haven't, we try to install the package as soon as possibile and
give you the stack trace.
> > The problem could be the dimension of id2entry.db4? Now it is 10GB and
> > in the DB I have only 100.000 entry.
> > Can I reduce the dimension of the file? It seems too large for the
> > number of records inside.
>
> Let's see a stack trace first.
> > Thanks in advance.
> > Best regards.
> > Luigi
> >
> > 389 users mailing list
> > [e-mail]
> > https://admin.fedoraproject.org/mailman/listinfo/389-users

[Rich Megginson]

On 03/05/2013 07:58 AM, Luigi Santangelo wrote:
> > What is the platform for A and B?  What are the 389-ds-base versions on A
> > and B?
>
> A and B are Red Hat Enterprise Linux Server release 5.5 (Tikanga);
> 389-ds-base are 389 Directory Server version 1.2.5

Note that it is going to be very difficult to support 1.2.5.  There is 
1.2.10.x available for EPEL5

http://port389.org/wiki/Download
> > What about A?  Any clues in the A errors log?
>
> The service is online, we have disabled the sycn process and then we
> can't reproduce  the problem now.
> > Do you have any core dumps/stack traces?
> > http://port389.org/wiki/FAQ#Debugging_Crashes
>
> No, we haven't, we try to install the package as soon as possibile and
> give you the stack trace.
> > > The problem could be the dimension of id2entry.db4? Now it is 10GB and
> > > in the DB I have only 100.000 entry.
> > > Can I reduce the dimension of the file? It seems too large for the
> > > number of records inside.
> >
> > Let's see a stack trace first.
> > > Thanks in advance.
> > > Best regards.
> > > Luigi
> > >
> > > 389 users mailing list
> > > [e-mail]
> > > https://admin.fedoraproject.org/mailman/listinfo/389-users
>
> --
> 389 users mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/389-users