FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Directory

 
 
LinkBack Thread Tools
 
Old 02-18-2011, 10:35 AM
Utkarsh Sengar
 
Default Moving from FDS to 389DS

Hi Guys,

I am trying to move an old fedora DS to the current version. (I wish I could tell you the versions, but I am not able to figure out how to get the version numbers).

Anyway, I exported the ldif from the old server and imported into the new server:


./ldif2db -n NetscapeRoot -i /ldap/NetscapeRoot.ldif
./ldif2db -n userRoot -i /dap/userRoot.ldif
I see a lot of warnings when I import userRoot.ldif about bad entry, skipping. And when I browse the new setup, I do not see the entries.



So, my question is: How can I move my existing FDS to a new FDS.

--
Thanks,
Utkarsh Sengar

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 02-18-2011, 01:19 PM
Rich Megginson
 
Default Moving from FDS to 389DS

On 02/18/2011 04:35 AM, Utkarsh Sengar wrote:
Hi Guys,



I am trying to move an old fedora DS to the current version. (I
wish I could tell you the versions, but I am not able to figure
out how to get the version numbers).


rpm -qi 389-ds-base

older - cd /opt/fedora-ds/bin/slapd/server ; ./ns-slapd -v



Anyway, I exported the ldif from the old server and imported into
the new server:

./ldif2db -n NetscapeRoot -i /ldap/NetscapeRoot.ldif

./ldif2db -n userRoot -i /dap/userRoot.ldif


I see a lot of warnings when I import userRoot.ldif about bad
entry, skipping. And when I browse the new setup, I do not see the
entries.


It is probably schema related - you didn't move your old schema, if
you had custom schema - or you are running into the fact that newer
389 is much stricter about schema and syntax checking.* It will be
most helpful if you could post some excerpts from your logs about
the error.




So, my question is: How can I move my existing FDS to a new FDS.



--

Thanks,

Utkarsh Sengar



--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users





--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 02-18-2011, 06:46 PM
Utkarsh Sengar
 
Default Moving from FDS to 389DS

New DS Version:
Name******* : 389-ds-base***************** Relocations: (not relocatable)
Version**** : 1.2.7.5************************** Vendor: Fedora Project
Release**** : 1.fc13*********************** Build Date: Thu 16 Dec 2010 11:25:26 AM CST


Install Date: Thu 17 Feb 2011 04:40:52 AM CST***** Build Host: x86-01.phx2.fedoraproject.org
Group****** : System Environment/Daemons*** Source RPM: 389-ds-base-1.2.7.5-1.fc13.src.rpm



Old DS Version:
./ns-slapd -v
None of the commands are working.
./migrate/opt/fedora-ds/bin/slapd/server/ns-slapd: error while loading shared libraries: libslapd.so: cannot open shared object file: No such file or directory




Please see my comments inline for logs. I hope the log excerpt helps.

On Fri, Feb 18, 2011 at 6:19 AM, Rich Megginson <rmeggins@redhat.com> wrote:









On 02/18/2011 04:35 AM, Utkarsh Sengar wrote:
Hi Guys,



I am trying to move an old fedora DS to the current version. (I
wish I could tell you the versions, but I am not able to figure
out how to get the version numbers).


rpm -qi 389-ds-base

older - cd /opt/fedora-ds/bin/slapd/server ; ./ns-slapd -v



Anyway, I exported the ldif from the old server and imported into
the new server:

./ldif2db -n NetscapeRoot -i /ldap/NetscapeRoot.ldif

./ldif2db -n userRoot -i /dap/userRoot.ldif


I see a lot of warnings when I import userRoot.ldif about bad
entry, skipping. And when I browse the new setup, I do not see the
entries.


It is probably schema related - you didn't move your old schema, if
you had custom schema - or you are running into the fact that newer
389 is much stricter about schema and syntax checking.* It will be
most helpful if you could post some excerpts from your logs about
the error.


Yes, I have custom schema and I have not moved them (how can I migrate the schema?). Here is the log file. Error in /var/slapd-instance/error.log

........
There are 4000+ WARNING: "bad entry" warnings.



[18/Feb/2011:04:58:26 -0600] - import userRoot: WARNING: bad entry: ID 863
[18/Feb/2011:04:58:26 -0600] - import userRoot: WARNING: bad entry: ID 864
[18/Feb/2011:04:58:26 -0600] - import userRoot: Workers finished; cleaning up...


[18/Feb/2011:04:58:26 -0600] - import userRoot: Workers cleaned up.[18/Feb/2011:04:58:26 -0600] - import userRoot: Cleaning up producer thread...
[18/Feb/2011:04:58:26 -0600] - import userRoot: Indexing complete.* Post-processing...[18/Feb/2011:04:58:26 -0600] - import userRoot: Flushing caches...


[18/Feb/2011:04:58:26 -0600] - import userRoot: Closing files...
[18/Feb/2011:04:58:26 -0600] - All database threads now stopped[18/Feb/2011:04:58:26 -0600] - import userRoot: Import complete.* Processed 864 entries (4669 were skipped) in 80 seconds. (10.80 entries/sec)


[18/Feb/2011:04:58:39 -0600] - 389-Directory/1.2.7.5 B2010.350.1724 starting up[18/Feb/2011:04:58:39 -0600] - I'm resizing my cache now...cache was 839491584 and is now 8000000
[18/Feb/2011:04:58:39 -0600] - slapd started.* Listening on All Interfaces port 389 for LDAP requests


[18/Feb/2011:04:59:44 -0600] - slapd shutting down - signaling operation threads
[18/Feb/2011:04:59:44 -0600] - slapd shutting down - closing down internal subsystems and plugins
[18/Feb/2011:04:59:44 -0600] - Waiting for 4 database threads to stop


[18/Feb/2011:04:59:45 -0600] - All database threads now stopped
[18/Feb/2011:04:59:45 -0600] - slapd stopped.

attr_syntax_create - Error: the EQUALITY matching rule [caseIgnoreIA5Match] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreIA5SubstringsMatch] is not compatible with the syntax
for the attribute [dc]

dse - The entry cn=schema in file /etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid, error code 21 (Invalid syntax) - attribute type nsAIMid: Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems and then restart the server.

attr_syntax_create - Error: the EQUALITY matching rule [caseIgnoreIA5Match] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreIA5SubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]

dse - The entry cn=schema in file /etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid, error code 21 (Invalid syntax) - attribute type nsAIMid: Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems and then restart the server.

attr_syntax_create - Error: the EQUALITY matching rule [caseIgnoreIA5Match] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreIA5SubstringsMatch] is not compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]

dse - The entry cn=schema in file /etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid, error code 21 (Invalid syntax) - attribute type nsAIMid: Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems and then restart the server.

attr_syntax_create - Error: the EQUALITY matching rule is not compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule [caseIgnoreIA5SubstringsMatch] is not
compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]

dse - The entry cn=schema in file /etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid, error code 21 (Invalid syntax) - attribute type nsAIMid: Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems and then restart the server.
389-Directory/1.2.7.5 B2010.350.1724 starting up
........
*





So, my question is: How can I move my existing FDS to a new FDS.



--

Thanks,

Utkarsh Sengar


--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users







--
Regards,
Utkarsh Sengar
utkarshsengar.com

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 02-18-2011, 08:01 PM
Rich Megginson
 
Default Moving from FDS to 389DS

On 02/18/2011 12:46 PM, Utkarsh Sengar wrote:
New DS Version:

Name******* : 389-ds-base***************** Relocations: (not
relocatable)

Version**** : 1.2.7.5************************** Vendor: Fedora
Project

Release**** : 1.fc13*********************** Build Date: Thu 16 Dec
2010 11:25:26 AM CST

Install Date: Thu 17 Feb 2011 04:40:52 AM CST***** Build Host: x86-01.phx2.fedoraproject.org

Group****** : System Environment/Daemons*** Source RPM:
389-ds-base-1.2.7.5-1.fc13.src.rpm



Old DS Version:

./ns-slapd -v

None of the commands are working.

./migrate/opt/fedora-ds/bin/slapd/server/ns-slapd: error while
loading shared libraries: libslapd.so: cannot open shared object
file: No such file or directory


Right.* It will not work unless you change to that directory first,
because the libraries are loaded using relative paths, so

cd migrate/opt/fedora-ds/bin/slapd/server

./ns-slapd -v



Have you tried the migrate-ds-admin.pl command?* Also try removing
the old 10presence.ldif schema file before migrating.






Please see my comments inline for logs. I hope the log excerpt
helps.



On Fri, Feb 18, 2011 at 6:19 AM, Rich
Megginson <rmeggins@redhat.com>
wrote:



On 02/18/2011 04:35 AM, Utkarsh Sengar
wrote:
Hi Guys,



I am trying to move an old fedora DS to the current
version. (I wish I could tell you the versions, but I am
not able to figure out how to get the version numbers).



rpm -qi 389-ds-base

older - cd /opt/fedora-ds/bin/slapd/server ; ./ns-slapd -v




Anyway, I exported the ldif from the old server and
imported into the new server:

./ldif2db -n NetscapeRoot -i /ldap/NetscapeRoot.ldif

./ldif2db -n userRoot -i /dap/userRoot.ldif


I see a lot of warnings when I import userRoot.ldif
about bad entry, skipping. And when I browse the new
setup, I do not see the entries.



It is probably schema related - you didn't move your old
schema, if you had custom schema - or you are running into
the fact that newer 389 is much stricter about schema and
syntax checking.* It will be most helpful if you could post
some excerpts from your logs about the error.







Yes, I have custom schema and I have not moved them (how can I
migrate the schema?). Here is the log file. Error in
/var/slapd-instance/error.log



........

There are 4000+ WARNING: "bad entry" warnings.



[18/Feb/2011:04:58:26 -0600] - import userRoot: WARNING: bad
entry: ID 863

[18/Feb/2011:04:58:26 -0600] - import userRoot: WARNING: bad
entry: ID 864

[18/Feb/2011:04:58:26 -0600] - import userRoot: Workers
finished; cleaning up...

[18/Feb/2011:04:58:26 -0600] - import userRoot: Workers
cleaned up.[18/Feb/2011:04:58:26 -0600] - import userRoot:
Cleaning up producer thread...

[18/Feb/2011:04:58:26 -0600] - import userRoot: Indexing
complete.* Post-processing...[18/Feb/2011:04:58:26 -0600] -
import userRoot: Flushing caches...

[18/Feb/2011:04:58:26 -0600] - import userRoot: Closing
files...

[18/Feb/2011:04:58:26 -0600] - All database threads now
stopped[18/Feb/2011:04:58:26 -0600] - import userRoot: Import
complete.* Processed 864 entries (4669 were skipped) in 80
seconds. (10.80 entries/sec)

[18/Feb/2011:04:58:39 -0600] - 389-Directory/1.2.7.5
B2010.350.1724 starting up[18/Feb/2011:04:58:39 -0600] - I'm
resizing my cache now...cache was 839491584 and is now 8000000

[18/Feb/2011:04:58:39 -0600] - slapd started.* Listening on
All Interfaces port 389 for LDAP requests

[18/Feb/2011:04:59:44 -0600] - slapd shutting down - signaling
operation threads

[18/Feb/2011:04:59:44 -0600] - slapd shutting down - closing
down internal subsystems and plugins

[18/Feb/2011:04:59:44 -0600] - Waiting for 4 database threads
to stop

[18/Feb/2011:04:59:45 -0600] - All database threads now
stopped

[18/Feb/2011:04:59:45 -0600] - slapd stopped.



attr_syntax_create - Error: the EQUALITY matching rule
[caseIgnoreIA5Match] is not compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule
[caseIgnoreIA5SubstringsMatch] is not compatible with the
syntax

for the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid,
error code 21 (Invalid syntax) - attribute type nsAIMid:
Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems
and then restart the server.



attr_syntax_create - Error: the EQUALITY matching rule
[caseIgnoreIA5Match] is not compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule
[caseIgnoreIA5SubstringsMatch] is not compatible with the
syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid,
error code 21 (Invalid syntax) - attribute type nsAIMid:
Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems
and then restart the server.



attr_syntax_create - Error: the EQUALITY matching rule
[caseIgnoreIA5Match] is not compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule
[caseIgnoreIA5SubstringsMatch] is not compatible with the
syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid,
error code 21 (Invalid syntax) - attribute type nsAIMid:
Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems
and then restart the server.



attr_syntax_create - Error: the EQUALITY matching rule is not
compatible with the syntax

[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule
[caseIgnoreIA5SubstringsMatch] is not

compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for
the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid,
error code 21 (Invalid syntax) - attribute type nsAIMid:
Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems
and then restart the server.

389-Directory/1.2.7.5
B2010.350.1724 starting up

........

*





So, my question is: How can I move my existing FDS to a
new FDS.



--

Thanks,

Utkarsh Sengar



--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users











--

Regards,

Utkarsh Sengar

utkarshsengar.com






--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 02-18-2011, 08:39 PM
Utkarsh Sengar
 
Default Moving from FDS to 389DS

Comments inline.

On Fri, Feb 18, 2011 at 1:01 PM, Rich Megginson <rmeggins@redhat.com> wrote:








On 02/18/2011 12:46 PM, Utkarsh Sengar wrote:
New DS Version:

Name******* : 389-ds-base***************** Relocations: (not
relocatable)

Version**** : 1.2.7.5************************** Vendor: Fedora
Project

Release**** : 1.fc13*********************** Build Date: Thu 16 Dec
2010 11:25:26 AM CST

Install Date: Thu 17 Feb 2011 04:40:52 AM CST***** Build Host: x86-01.phx2.fedoraproject.org

Group****** : System Environment/Daemons*** Source RPM:
389-ds-base-1.2.7.5-1.fc13.src.rpm



Old DS Version:

./ns-slapd -v

None of the commands are working.

./migrate/opt/fedora-ds/bin/slapd/server/ns-slapd: error while
loading shared libraries: libslapd.so: cannot open shared object
file: No such file or directory


Right.* It will not work unless you change to that directory first,
because the libraries are loaded using relative paths, so

cd migrate/opt/fedora-ds/bin/slapd/server

./ns-slapd -v
*

Old fedora LDAP (rpm -qi 389-ds-base worked there too):
Name : 389-ds-base Relocations: (not relocatable)
Version : 1.2.2 Vendor: Fedora Project
Release : 1.fc10 Build Date: Tue 25 Aug 2009 04:08:07 PM EDT
Install Date: Sun 27 Sep 2009 11:39:56 PM EDT Build Host: x86-4.fedora.phx.redhat.com
Group : System Environment/Daemons Source RPM: 389-ds-base-1.2.2-1.fc10.src.rpm


*So, basically I am trying to migrate between 1.2.2 to 1.2.7.




Have you tried the migrate-ds-admin.pl command?* Also try removing
the old 10presence.ldif schema file before migrating.

I don't have migrate-ds-admin.pl on 1.2.2 installation, but it's there in 1.2.7 at ./usr/sbin/migrate-ds-admin.pl.



*
*







Please see my comments inline for logs. I hope the log excerpt
helps.



On Fri, Feb 18, 2011 at 6:19 AM, Rich
Megginson <rmeggins@redhat.com>
wrote:



On 02/18/2011 04:35 AM, Utkarsh Sengar
wrote:
Hi Guys,



I am trying to move an old fedora DS to the current
version. (I wish I could tell you the versions, but I am
not able to figure out how to get the version numbers).



rpm -qi 389-ds-base

older - cd /opt/fedora-ds/bin/slapd/server ; ./ns-slapd -v




Anyway, I exported the ldif from the old server and
imported into the new server:

./ldif2db -n NetscapeRoot -i /ldap/NetscapeRoot.ldif

./ldif2db -n userRoot -i /dap/userRoot.ldif


I see a lot of warnings when I import userRoot.ldif
about bad entry, skipping. And when I browse the new
setup, I do not see the entries.



It is probably schema related - you didn't move your old
schema, if you had custom schema - or you are running into
the fact that newer 389 is much stricter about schema and
syntax checking.* It will be most helpful if you could post
some excerpts from your logs about the error.







Yes, I have custom schema and I have not moved them (how can I
migrate the schema?). Here is the log file. Error in
/var/slapd-instance/error.log



........

There are 4000+ WARNING: "bad entry" warnings.



[18/Feb/2011:04:58:26 -0600] - import userRoot: WARNING: bad
entry: ID 863

[18/Feb/2011:04:58:26 -0600] - import userRoot: WARNING: bad
entry: ID 864

[18/Feb/2011:04:58:26 -0600] - import userRoot: Workers
finished; cleaning up...

[18/Feb/2011:04:58:26 -0600] - import userRoot: Workers
cleaned up.[18/Feb/2011:04:58:26 -0600] - import userRoot:
Cleaning up producer thread...

[18/Feb/2011:04:58:26 -0600] - import userRoot: Indexing
complete.* Post-processing...[18/Feb/2011:04:58:26 -0600] -
import userRoot: Flushing caches...

[18/Feb/2011:04:58:26 -0600] - import userRoot: Closing
files...

[18/Feb/2011:04:58:26 -0600] - All database threads now
stopped[18/Feb/2011:04:58:26 -0600] - import userRoot: Import
complete.* Processed 864 entries (4669 were skipped) in 80
seconds. (10.80 entries/sec)

[18/Feb/2011:04:58:39 -0600] - 389-Directory/1.2.7.5
B2010.350.1724 starting up[18/Feb/2011:04:58:39 -0600] - I'm
resizing my cache now...cache was 839491584 and is now 8000000

[18/Feb/2011:04:58:39 -0600] - slapd started.* Listening on
All Interfaces port 389 for LDAP requests

[18/Feb/2011:04:59:44 -0600] - slapd shutting down - signaling
operation threads

[18/Feb/2011:04:59:44 -0600] - slapd shutting down - closing
down internal subsystems and plugins

[18/Feb/2011:04:59:44 -0600] - Waiting for 4 database threads
to stop

[18/Feb/2011:04:59:45 -0600] - All database threads now
stopped

[18/Feb/2011:04:59:45 -0600] - slapd stopped.



attr_syntax_create - Error: the EQUALITY matching rule
[caseIgnoreIA5Match] is not compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule
[caseIgnoreIA5SubstringsMatch] is not compatible with the
syntax

for the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid,
error code 21 (Invalid syntax) - attribute type nsAIMid:
Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems
and then restart the server.



attr_syntax_create - Error: the EQUALITY matching rule
[caseIgnoreIA5Match] is not compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule
[caseIgnoreIA5SubstringsMatch] is not compatible with the
syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid,
error code 21 (Invalid syntax) - attribute type nsAIMid:
Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems
and then restart the server.



attr_syntax_create - Error: the EQUALITY matching rule
[caseIgnoreIA5Match] is not compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule
[caseIgnoreIA5SubstringsMatch] is not compatible with the
syntax [1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid,
error code 21 (Invalid syntax) - attribute type nsAIMid:
Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems
and then restart the server.



attr_syntax_create - Error: the EQUALITY matching rule is not
compatible with the syntax

[1.3.6.1.4.1.1466.115.121.1.15] for the attribute [dc]



attr_syntax_create - Error: the SUBSTR matching rule
[caseIgnoreIA5SubstringsMatch] is not

compatible with the syntax [1.3.6.1.4.1.1466.115.121.1.15] for
the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif is invalid,
error code 21 (Invalid syntax) - attribute type nsAIMid:
Unknown attribute syntax OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported problems
and then restart the server.

389-Directory/1.2.7.5
B2010.350.1724 starting up

........

*





So, my question is: How can I move my existing FDS to a
new FDS.



--

Thanks,

Utkarsh Sengar



--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users











--

Regards,

Utkarsh Sengar

utkarshsengar.com








--
Regards,
Utkarsh Sengar
utkarshsengar.com

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 02-18-2011, 08:48 PM
Rich Megginson
 
Default Moving from FDS to 389DS

On 02/18/2011 02:39 PM, Utkarsh Sengar wrote:
Comments inline.



On Fri, Feb 18, 2011 at 1:01 PM, Rich
Megginson <rmeggins@redhat.com>
wrote:



On 02/18/2011 12:46 PM, Utkarsh Sengar
wrote:
New DS Version:

Name******* : 389-ds-base***************** Relocations:
(not relocatable)

Version**** : 1.2.7.5************************** Vendor:
Fedora Project

Release**** : 1.fc13*********************** Build Date:
Thu 16 Dec 2010 11:25:26 AM CST

Install Date: Thu 17 Feb 2011 04:40:52 AM CST***** Build
Host: x86-01.phx2.fedoraproject.org

Group****** : System Environment/Daemons*** Source RPM:
389-ds-base-1.2.7.5-1.fc13.src.rpm



Old DS Version:

./ns-slapd -v

None of the commands are working.

./migrate/opt/fedora-ds/bin/slapd/server/ns-slapd: error
while loading shared libraries: libslapd.so: cannot open
shared object file: No such file or directory



Right.* It will not work unless you change to that directory
first, because the libraries are loaded using relative
paths, so

cd migrate/opt/fedora-ds/bin/slapd/server

./ns-slapd -v

*





Old fedora LDAP (rpm -qi 389-ds-base worked there too):

Name : 389-ds-base Relocations: (not relocatable)
Version : 1.2.2 Vendor: Fedora Project
Release : 1.fc10 Build Date: Tue 25 Aug 2009 04:08:07 PM EDT
Install Date: Sun 27 Sep 2009 11:39:56 PM EDT Build Host: x86-4.fedora.phx.redhat.com
Group : System Environment/Daemons Source RPM: 389-ds-base-1.2.2-1.fc10.src.rpm




*So, basically I am trying to migrate between 1.2.2 to 1.2.7.




??? 389-ds-base 1.2.2 did not use /opt/fedora-ds????

It would appear that you have installed 389-ds-base on a system on
which you had an old version of fedora-ds . . .







Have you tried the migrate-ds-admin.pl command?* Also try
removing the old 10presence.ldif schema file before
migrating.





I don't have migrate-ds-admin.pl on
1.2.2 installation, but it's there in 1.2.7 at ./usr/sbin/migrate-ds-admin.pl.




Right.* Use the one that comes with 1.2.7.5






*





*











Please see my comments inline for logs. I hope the log
excerpt helps.



On Fri, Feb 18, 2011 at 6:19
AM, Rich Megginson <rmeggins@redhat.com>
wrote:



On 02/18/2011 04:35 AM, Utkarsh Sengar
wrote:
Hi Guys,



I am trying to move an old fedora DS to the
current version. (I wish I could tell you
the versions, but I am not able to figure
out how to get the version numbers).



rpm -qi 389-ds-base

older - cd /opt/fedora-ds/bin/slapd/server ;
./ns-slapd -v




Anyway, I exported the ldif from the old
server and imported into the new server:

./ldif2db -n NetscapeRoot -i
/ldap/NetscapeRoot.ldif

./ldif2db -n userRoot -i /dap/userRoot.ldif



I see a lot of warnings when I import
userRoot.ldif about bad entry, skipping. And
when I browse the new setup, I do not see
the entries.



It is probably schema related - you didn't move
your old schema, if you had custom schema - or
you are running into the fact that newer 389 is
much stricter about schema and syntax checking.*
It will be most helpful if you could post some
excerpts from your logs about the error.







Yes, I have custom schema and I have not moved
them (how can I migrate the schema?). Here is the
log file. Error in /var/slapd-instance/error.log



........

There are 4000+ WARNING: "bad entry" warnings.



[18/Feb/2011:04:58:26 -0600] - import userRoot:
WARNING: bad entry: ID 863

[18/Feb/2011:04:58:26 -0600] - import userRoot:
WARNING: bad entry: ID 864

[18/Feb/2011:04:58:26 -0600] - import userRoot:
Workers finished; cleaning up...

[18/Feb/2011:04:58:26 -0600] - import userRoot:
Workers cleaned up.[18/Feb/2011:04:58:26 -0600] -
import userRoot: Cleaning up producer thread...

[18/Feb/2011:04:58:26 -0600] - import userRoot:
Indexing complete.*
Post-processing...[18/Feb/2011:04:58:26 -0600] -
import userRoot: Flushing caches...

[18/Feb/2011:04:58:26 -0600] - import userRoot:
Closing files...

[18/Feb/2011:04:58:26 -0600] - All database
threads now stopped[18/Feb/2011:04:58:26 -0600] -
import userRoot: Import complete.* Processed 864
entries (4669 were skipped) in 80 seconds. (10.80
entries/sec)

[18/Feb/2011:04:58:39 -0600] - 389-Directory/1.2.7.5 B2010.350.1724
starting up[18/Feb/2011:04:58:39 -0600] - I'm
resizing my cache now...cache was 839491584 and is
now 8000000

[18/Feb/2011:04:58:39 -0600] - slapd started.*
Listening on All Interfaces port 389 for LDAP
requests

[18/Feb/2011:04:59:44 -0600] - slapd shutting down
- signaling operation threads

[18/Feb/2011:04:59:44 -0600] - slapd shutting down
- closing down internal subsystems and plugins

[18/Feb/2011:04:59:44 -0600] - Waiting for 4
database threads to stop

[18/Feb/2011:04:59:45 -0600] - All database
threads now stopped

[18/Feb/2011:04:59:45 -0600] - slapd stopped.



attr_syntax_create - Error: the EQUALITY matching
rule [caseIgnoreIA5Match] is not compatible with
the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the
attribute [dc]



attr_syntax_create - Error: the SUBSTR matching
rule [caseIgnoreIA5SubstringsMatch] is not
compatible with the syntax

for the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif
is invalid, error code 21 (Invalid syntax) -
attribute type nsAIMid: Unknown attribute syntax
OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported
problems and then restart the server.



attr_syntax_create - Error: the EQUALITY matching
rule [caseIgnoreIA5Match] is not compatible with
the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the
attribute [dc]



attr_syntax_create - Error: the SUBSTR matching
rule [caseIgnoreIA5SubstringsMatch] is not
compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute
[dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif
is invalid, error code 21 (Invalid syntax) -
attribute type nsAIMid: Unknown attribute syntax
OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported
problems and then restart the server.



attr_syntax_create - Error: the EQUALITY matching
rule [caseIgnoreIA5Match] is not compatible with
the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the
attribute [dc]



attr_syntax_create - Error: the SUBSTR matching
rule [caseIgnoreIA5SubstringsMatch] is not
compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute
[dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif
is invalid, error code 21 (Invalid syntax) -
attribute type nsAIMid: Unknown attribute syntax
OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported
problems and then restart the server.



attr_syntax_create - Error: the EQUALITY matching
rule is not compatible with the syntax

[1.3.6.1.4.1.1466.115.121.1.15] for the attribute
[dc]



attr_syntax_create - Error: the SUBSTR matching
rule [caseIgnoreIA5SubstringsMatch] is not

compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute
[dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif
is invalid, error code 21 (Invalid syntax) -
attribute type nsAIMid: Unknown attribute syntax
OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported
problems and then restart the server.

389-Directory/1.2.7.5
B2010.350.1724 starting up

........

*





So, my question is: How can I move my
existing FDS to a new FDS.



--

Thanks,

Utkarsh Sengar



--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users











--

Regards,

Utkarsh Sengar

utkarshsengar.com














--

Regards,

Utkarsh Sengar

utkarshsengar.com






--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 02-18-2011, 09:00 PM
Utkarsh Sengar
 
Default Moving from FDS to 389DS

On Fri, Feb 18, 2011 at 1:48 PM, Rich Megginson <rmeggins@redhat.com> wrote:








On 02/18/2011 02:39 PM, Utkarsh Sengar wrote:
Comments inline.



On Fri, Feb 18, 2011 at 1:01 PM, Rich
Megginson <rmeggins@redhat.com>
wrote:



On 02/18/2011 12:46 PM, Utkarsh Sengar
wrote:
New DS Version:

Name******* : 389-ds-base***************** Relocations:
(not relocatable)

Version**** : 1.2.7.5************************** Vendor:
Fedora Project

Release**** : 1.fc13*********************** Build Date:
Thu 16 Dec 2010 11:25:26 AM CST

Install Date: Thu 17 Feb 2011 04:40:52 AM CST***** Build
Host: x86-01.phx2.fedoraproject.org

Group****** : System Environment/Daemons*** Source RPM:
389-ds-base-1.2.7.5-1.fc13.src.rpm



Old DS Version:

./ns-slapd -v

None of the commands are working.

./migrate/opt/fedora-ds/bin/slapd/server/ns-slapd: error
while loading shared libraries: libslapd.so: cannot open
shared object file: No such file or directory



Right.* It will not work unless you change to that directory
first, because the libraries are loaded using relative
paths, so

cd migrate/opt/fedora-ds/bin/slapd/server

./ns-slapd -v

*





Old fedora LDAP (rpm -qi 389-ds-base worked there too):

Name : 389-ds-base Relocations: (not relocatable)
Version : 1.2.2 Vendor: Fedora Project
Release : 1.fc10 Build Date: Tue 25 Aug 2009 04:08:07 PM EDT
Install Date: Sun 27 Sep 2009 11:39:56 PM EDT Build Host: x86-4.fedora.phx.redhat.com
Group : System Environment/Daemons Source RPM: 389-ds-base-1.2.2-1.fc10.src.rpm




*So, basically I am trying to migrate between 1.2.2 to 1.2.7.




??? 389-ds-base 1.2.2 did not use /opt/fedora-ds????

It would appear that you have installed 389-ds-base on a system on
which you had an old version of fedora-ds . . .*Well, that might be the case. I am not sure, I was not around the old server was setup.










Have you tried the migrate-ds-admin.pl command?* Also try
removing the old 10presence.ldif schema file before
migrating.





I don't have migrate-ds-admin.pl on
1.2.2 installation, but it's there in 1.2.7 at ./usr/sbin/migrate-ds-admin.pl.




Right.* Use the one that comes with 1.2.7.5

Okay, so I will do the following:
1. Copy migrate-ds-admin.pl from server which has 1.2.7 to 1.2.2


2. Run migrate-ds-admin.pl to export the schema+ldif from 1.2.2
3. Import the schema+ldif to 1.2.7

I am not sure how migrate-ds-admin.pl works, I will take a look at it and if I have any problems with it, will get back to the mailing list!



Thanks for your help!

**







*





*











Please see my comments inline for logs. I hope the log
excerpt helps.



On Fri, Feb 18, 2011 at 6:19
AM, Rich Megginson <rmeggins@redhat.com>
wrote:



On 02/18/2011 04:35 AM, Utkarsh Sengar
wrote:
Hi Guys,



I am trying to move an old fedora DS to the
current version. (I wish I could tell you
the versions, but I am not able to figure
out how to get the version numbers).



rpm -qi 389-ds-base

older - cd /opt/fedora-ds/bin/slapd/server ;
./ns-slapd -v




Anyway, I exported the ldif from the old
server and imported into the new server:

./ldif2db -n NetscapeRoot -i
/ldap/NetscapeRoot.ldif

./ldif2db -n userRoot -i /dap/userRoot.ldif



I see a lot of warnings when I import
userRoot.ldif about bad entry, skipping. And
when I browse the new setup, I do not see
the entries.



It is probably schema related - you didn't move
your old schema, if you had custom schema - or
you are running into the fact that newer 389 is
much stricter about schema and syntax checking.*
It will be most helpful if you could post some
excerpts from your logs about the error.







Yes, I have custom schema and I have not moved
them (how can I migrate the schema?). Here is the
log file. Error in /var/slapd-instance/error.log



........

There are 4000+ WARNING: "bad entry" warnings.



[18/Feb/2011:04:58:26 -0600] - import userRoot:
WARNING: bad entry: ID 863

[18/Feb/2011:04:58:26 -0600] - import userRoot:
WARNING: bad entry: ID 864

[18/Feb/2011:04:58:26 -0600] - import userRoot:
Workers finished; cleaning up...

[18/Feb/2011:04:58:26 -0600] - import userRoot:
Workers cleaned up.[18/Feb/2011:04:58:26 -0600] -
import userRoot: Cleaning up producer thread...

[18/Feb/2011:04:58:26 -0600] - import userRoot:
Indexing complete.*
Post-processing...[18/Feb/2011:04:58:26 -0600] -
import userRoot: Flushing caches...

[18/Feb/2011:04:58:26 -0600] - import userRoot:
Closing files...

[18/Feb/2011:04:58:26 -0600] - All database
threads now stopped[18/Feb/2011:04:58:26 -0600] -
import userRoot: Import complete.* Processed 864
entries (4669 were skipped) in 80 seconds. (10.80
entries/sec)

[18/Feb/2011:04:58:39 -0600] - 389-Directory/1.2.7.5 B2010.350.1724
starting up[18/Feb/2011:04:58:39 -0600] - I'm
resizing my cache now...cache was 839491584 and is
now 8000000

[18/Feb/2011:04:58:39 -0600] - slapd started.*
Listening on All Interfaces port 389 for LDAP
requests

[18/Feb/2011:04:59:44 -0600] - slapd shutting down
- signaling operation threads

[18/Feb/2011:04:59:44 -0600] - slapd shutting down
- closing down internal subsystems and plugins

[18/Feb/2011:04:59:44 -0600] - Waiting for 4
database threads to stop

[18/Feb/2011:04:59:45 -0600] - All database
threads now stopped

[18/Feb/2011:04:59:45 -0600] - slapd stopped.



attr_syntax_create - Error: the EQUALITY matching
rule [caseIgnoreIA5Match] is not compatible with
the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the
attribute [dc]



attr_syntax_create - Error: the SUBSTR matching
rule [caseIgnoreIA5SubstringsMatch] is not
compatible with the syntax

for the attribute [dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif
is invalid, error code 21 (Invalid syntax) -
attribute type nsAIMid: Unknown attribute syntax
OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported
problems and then restart the server.



attr_syntax_create - Error: the EQUALITY matching
rule [caseIgnoreIA5Match] is not compatible with
the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the
attribute [dc]



attr_syntax_create - Error: the SUBSTR matching
rule [caseIgnoreIA5SubstringsMatch] is not
compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute
[dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif
is invalid, error code 21 (Invalid syntax) -
attribute type nsAIMid: Unknown attribute syntax
OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported
problems and then restart the server.



attr_syntax_create - Error: the EQUALITY matching
rule [caseIgnoreIA5Match] is not compatible with
the syntax [1.3.6.1.4.1.1466.115.121.1.15] for the
attribute [dc]



attr_syntax_create - Error: the SUBSTR matching
rule [caseIgnoreIA5SubstringsMatch] is not
compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute
[dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif
is invalid, error code 21 (Invalid syntax) -
attribute type nsAIMid: Unknown attribute syntax
OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported
problems and then restart the server.



attr_syntax_create - Error: the EQUALITY matching
rule is not compatible with the syntax

[1.3.6.1.4.1.1466.115.121.1.15] for the attribute
[dc]



attr_syntax_create - Error: the SUBSTR matching
rule [caseIgnoreIA5SubstringsMatch] is not

compatible with the syntax
[1.3.6.1.4.1.1466.115.121.1.15] for the attribute
[dc]



dse - The entry cn=schema in file
/etc/dirsrv/slapd-irisp1cl/schema/10presence.ldif
is invalid, error code 21 (Invalid syntax) -
attribute type nsAIMid: Unknown attribute syntax
OID "2.16.840.1.113730.3.7.1"



dse - Please edit the file to correct the reported
problems and then restart the server.

389-Directory/1.2.7.5
B2010.350.1724 starting up

........

*





So, my question is: How can I move my
existing FDS to a new FDS.



--

Thanks,

Utkarsh Sengar



--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users











--

Regards,

Utkarsh Sengar

utkarshsengar.com














--

Regards,

Utkarsh Sengar

utkarshsengar.com








--
Regards,
Utkarsh Sengar
utkarshsengar.com

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 

Thread Tools




All times are GMT. The time now is 07:57 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org