Re: [389-users] problem on Sparc with DS 1.3.2: Skipping entry ... which has no parent

[Carsten Grzemba]

Am 11.03.14 schrieb Rich Megginson  :
> On 03/11/2014 07:32 AM, Carsten Grzemba wrote:
> > Am 11.03.14 schrieb Rich Megginson   :
> > > On 03/11/2014 05:57 AM, Carsten Grzemba wrote:
> > > > interessting: it is only on 32bit build. 64bit build on Solaris10 Sparc works as expected.
> > >
> > > I'm not sure. I guess we could try to reproduce on Fedora 32-bit.
> >
> > the Solaris10 i386 build works without problems, only on Sparc.
>
> Then I suspect the slapi_counter code . . .

was there anything changed since 1.2.11.15? In 1.2.11.15 works also all fine.
> > > > --
> > > > 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

problem on Sparc with DS 1.3.2: Skipping entry ... which has no parent

[Rich Megginson]

On 03/11/2014 08:02 AM, Carsten Grzemba wrote:
> Am 11.03.14 schrieb *Rich Megginson * :
> > On 03/11/2014 07:32 AM, Carsten Grzemba wrote:
> > > Am 11.03.14 schrieb *Rich Megginson *  
> > > :
> > > > On 03/11/2014 05:57 AM, Carsten Grzemba wrote:
> > > > > interessting: it is only on 32bit build. 64bit build on Solaris10 
> > > > > Sparc works as expected.
> > > >
> > > > I'm not sure.  I guess we could try to reproduce on Fedora 32-bit.
> > >
> > > the Solaris10 i386 build works without problems, only on Sparc.
> >
> > Then I suspect the slapi_counter code . . .
>
> was there anything changed since 1.2.11.15? In 1.2.11.15 works also 
> all fine.

I'm not aware of any changes to the counter code.
> > > > > --
> > > > > 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

Importing database to new server

[Elizabeth Jones]

I'm having some problems trying to import an existing database into a new
server. I know I was able to do this in the past, but since I'm an idiot I
did not take notes on what I did and now I can't seem to recreate it.

The new server was built from scratch and I configured a vanilla 389DS on
it.  I know that somehow in the past I was able to use a backup of one of
my existing databases and import that into the new server, and I also know
that I had to do something to make it understand that this was a new
server (ldap2-clone) rather than ldap2.  But what would that step have
been?  As I am now, every time I import the ldap2 database into the clone
it ends up turning it into ldap2. I'm running
389-ds-base-1.2.11.25-1.el6.x86_64 on OEL 6.4.

thanks,

EJ

Importing database to new server

[Predrag Zečević - Technical Support Analyst]

Hi,

how did you make backup (export) of LDAP data?

Regards.

On 03/11/14 04:55 PM, Elizabeth Jones wrote:
> I'm having some problems trying to import an existing database into a new
> server. I know I was able to do this in the past, but since I'm an idiot I
> did not take notes on what I did and now I can't seem to recreate it.
>
> The new server was built from scratch and I configured a vanilla 389DS on
> it.  I know that somehow in the past I was able to use a backup of one of
> my existing databases and import that into the new server, and I also know
> that I had to do something to make it understand that this was a new
> server (ldap2-clone) rather than ldap2.  But what would that step have
> been?  As I am now, every time I import the ldap2 database into the clone
> it ends up turning it into ldap2. I'm running
> 389-ds-base-1.2.11.25-1.el6.x86_64 on OEL 6.4.
>
> thanks,
>
> EJ
>
> --
> 389 users mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/389-users

Importing database to new server

[Mark Reynolds]

On 03/11/2014 11:55 AM, Elizabeth Jones wrote:
> I'm having some problems trying to import an existing database into a new
> server. I know I was able to do this in the past, but since I'm an idiot I
> did not take notes on what I did and now I can't seem to recreate it.
>
> The new server was built from scratch and I configured a vanilla 389DS on
> it.  I know that somehow in the past I was able to use a backup of one of
> my existing databases and import that into the new server, and I also know
> that I had to do something to make it understand that this was a new
> server (ldap2-clone) rather than ldap2.  But what would that step have
> been?  As I am now, every time I import the ldap2 database into the clone
> it ends up turning it into ldap2. I'm running
> 389-ds-base-1.2.11.25-1.el6.x86_64 on OEL 6.4.

How are you taking a backup, and how are you doing the import?  What 
backend/database are you trying to restore?  What do you mean it turns 
into ldap2?  What is the exact problem as it sounds like the import is 
working?
> thanks,
>
> EJ
>
> --
> 389 users mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/389-users

Importing database to new server

[Elizabeth Jones]

> How are you taking a backup, and how are you doing the import?  What
> backend/database are you trying to restore?  What do you mean it turns
> into ldap2?  What is the exact problem as it sounds like the import is
> working?

I'm taking the backup off my production server with db2bak.pl script, then
copying the files from that over to my new server.  I am then trying to
import just userRoot (no NetscapeRoot) into my new server's instance.  I'm
using the import database task on 389-console.  But after I import and
then logout of 389-console and then log back in, my 389-console is trying
to connect me back to the original server (ldap2) that I made the backup
from, not my new server (ldap2-clone).

EJ

Importing database to new server

[Predrag Zečević - Technical Support Analyst]

Hi,

I cannot recall why, but I use pair of (export) db2ldif.pl and (import) 
ldif2db.pl tools, and that works fine (also importing JUST userRoot 
file). Actually, we do cloning (for testing purposes) of our production 
LDAP with those tools...

Also, I am not using GUI tools (389-console ?), but to me it looks like 
connecting back to original server is not logicla in any case, because 
console writes all into ~/.389-console/Console.*.Login.preferences file, 
and that one should NOT be affected by import.

If you try to use CLI tools (ldapsearch, for example), is everything OK?

Regards.

On 03/11/14 05:19 PM, Elizabeth Jones wrote:
> > How are you taking a backup, and how are you doing the import?  What
> > backend/database are you trying to restore?  What do you mean it turns
> > into ldap2?  What is the exact problem as it sounds like the import is
> > working?
>
> I'm taking the backup off my production server with db2bak.pl script, then
> copying the files from that over to my new server.  I am then trying to
> import just userRoot (no NetscapeRoot) into my new server's instance.  I'm
> using the import database task on 389-console.  But after I import and
> then logout of 389-console and then log back in, my 389-console is trying
> to connect me back to the original server (ldap2) that I made the backup
> from, not my new server (ldap2-clone).
>
> EJ
>
> --
> 389 users mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/389-users