[389-users] Re: New Install Missing Schema Files

[Trevor Fong]

Hi Patrick,

Thanks for the link to those docs.  

I finally succeeded with a combination of tips from Mark and Patrick:
1. removed /usr/share/dirsrv/schema/10rfc2307.ldif
2. copied /usr/share/dirsrv/data/10rfc2307bis.ldif to /usr/share/dirsrv/schema/

It seems that for 389 DS 1.3.6.1, /usr/share/dirsrv/schema/ takes precedence 
over /etc/dirsrv/slapd-/schema/

This seems to be different for 389 DS 1.2.11, where the converse is true.

However, I was reading more re schema:
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/administration_guide/index

11.1.1. Default Schema Files
The schema for Directory Server is defined in several different schema files 
(LDIF files which define schema elements). The Directory Server schema files 
are located in the /usr/share/dirsrv/schema/ directory. The files in this 
directory are used as templates for new Directory Server instances. Adding a 
new schema into this directory will make it available to any new instances.

Do the docs need to be updated?

Thanks,
Trev
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] Re: New Install Missing Schema Files

[Patrick Landry]

There are several references to 10rfc2307bis.ldif in the Red Hat Directory 
Server version 10 "Configuration, Command, and File Reference" 
manual . This one talks about replacing 60autofs.ldif with 10rfc2307bis.ldif . 
5.2.16. automountInformation 
This attribute contains information used by the autofs automounter. 

Note 
The automountInformation attribute is defined in 60autofs.ldif in the Directory 
Server. To use the updated RFC 2307 schema, remove the 60autofs.ldif file and 
copy the 10rfc2307bis.ldif file from the /usr/share/dirsrv/data directory to 
the /etc/dirsrv/slapd- instance /schema directory. 

This one talks about replacing 10rfc2307.ldif with 10rfc2307bis.ldif. 
5.2.17. bootFile 
This attribute contains the boot image file name. 

Note 
The bootFile attribute is defined in 10rfc2307.ldif in the Directory Server. To 
use the updated RFC 2307 schema, remove the 10rfc2307.ldif file and copy the 
10rfc2307bis.ldif file from the /usr/share/dirsrv/data directory to the 
/etc/dirsrv/slapd- instance /schema directory. 

I have not needed to do this but I would think that if you do want to use 
10rfc2307bis.ldif you would have 
to remove both 60autofs.ldif and 10rfc2307.ldif to avoid conflicting 
(duplicate) attribute definitions. 

- Original Message -

> From: "Trevor Fong" <tjf...@gmail.com>
> To: "General discussion list for the 389 Directory server project."
> <389-users@lists.fedoraproject.org>
> Sent: Tuesday, October 10, 2017 12:16:34 PM
> Subject: [389-users] Re: New Install Missing Schema Files

> Oh - I get it now; core schema is now immutably maintained in
> /usr/share/dirsrv/schema/ and is referenced by each slapd instance.

> How do I go about overriding the core schema?
> For example, if I wanted to replace 10rfc2307.ldif with 10rfc2307bis.ldif,
> what would I do?
> Previously, we would remove
> /etc/dirsrv/slapd-/schema/10rfc2307.ldif and add
> /etc/dirsrv/slapd-/schema/10rfc2307bis.ldif
> How would we accomplish this now with core schema immutably maintained in
> /usr/share/dirsrv/schema/?

> Currently I get the fatal error:

> [10/Oct/2017:10:07:50.514409639 -0700] - ERR - dse_read_one_file - The entry
> cn=schema in file /etc/dirsrv/slapd-eldapdcp1/schema/10rfc2307bis.ldif
> (lineno: 1) is invalid, error code 20 (Type or value exists) - object class
> nisMap: The name does not match the OID "1.3.6.1.1.1.2.9". Another object
> class is already using the name or OID.

> because it clashes with the default /usr/share/dirsrv/schema/10rfc2307.ldif

> Thanks,
> Trev

> On 10 October 2017 at 09:46, Mark Reynolds < marey...@redhat.com > wrote:

> > On 10/10/2017 12:36 PM, Trevor Fong wrote:
> 

> > > Hi Mark and Michael,
> > 
> 

> > > Thanks a lot for your replies.
> > 
> 
> > > I've run the setup-ds.pl (and also tried setup-ds-admin.pl ),
> > > /etc/dirsrv/slapd-/schema only contains 99user.ldif.
> > 
> 
> > > /usr/share/dirsrv/schema does indeed contain all the default schema
> > > files,
> > > but it doesn't look like they're copied to the instance schema dir.
> > 
> 

> > Correct, the core schema stays in /usr/share/dirsrv/schema, while custom
> > schema is in the instance directory.
> 

> > Are you running into problems?
> 

> > > Trev
> > 
> 

> > > On 10 October 2017 at 08:19, Mark Reynolds < marey...@redhat.com > wrote:
> > 
> 

> > > > On 10/10/2017 11:13 AM, Trevor Fong wrote:
> > > 
> > 
> 
> > > > > Hi Everyone,
> > > 
> > 
> 
> > > > >
> > > 
> > 
> 
> > > > > I just did a new install and it looks like no schema files were
> > > > > included
> > > > > with it?
> > > 
> > 
> 
> > > > > I seem to remember that previously, included schema files would be in
> > > > > /etc/dirsrv/schema and would get copied into any new instances that
> > > > > were
> > > > > set up.
> > > 
> > 
> 
> > > > > However with this install /etc/dirsrv/schema/ only contained
> > > > > 99user.ldif
> > > 
> > 
> 
> > > > > Am I missing something?
> > > 
> > 
> 
> > > > Things were changed for the "core" server schema. It should be in
> > > 
> > 
> 
> > > > /usr/share/dirsrv/schema
> > > 
> > 
> 
> > > > >
> > > 
> > 
> 
> > > > > Thanks a lot,
> > > 
> > 
> 
> > > > > Trev
> > > 
> > 
> 
> > > > >
>

[389-users] Re: New Install Missing Schema Files

[Mark Reynolds]

On 10/10/2017 02:19 PM, Mark Reynolds wrote:
>
>
> On 10/10/2017 01:12 PM, Trevor Fong wrote:
>> Oh - I get it now; core schema is now immutably maintained in
>> /usr/share/dirsrv/schema/ and is referenced by each slapd instance.  
>>
>> How do I go about overriding the core schema? 
> You are not supposed to :-/
>
> You can try stopping the server, then replacing the file in
> /usr/dirsrv/share/schema.  It looks like it's still pulling it into: 
> /etc/dirsrv/slapd-eldapdcp1/schema, so you might have to do it in two
> locations
>> For example, if I wanted to replace 10rfc2307.ldif
>> with 10rfc2307bis.ldif, what would I do?
>> Previously, we would remove
>> /etc/dirsrv/slapd-/schema/10rfc2307.ldif and add
>> /etc/dirsrv/slapd-/schema/10rfc2307bis.ldif
>> How would we accomplish this now with core schema immutably
>> maintained in /usr/share/dirsrv/schema/?
>>
>> Currently I get the fatal error:
>>
>> [10/Oct/2017:10:07:50.514409639 -0700] - ERR - dse_read_one_file -
>> The entry cn=schema in file
>> /etc/dirsrv/slapd-eldapdcp1/schema/10rfc2307bis.ldif (lineno: 1) is
>> invalid, error code 20 (Type or value exists) - object class nisMap:
>> The name does not match the OID "1.3.6.1.1.1.2.9". Another object
>> class is already using the name or OID.
>>
>> because it clashes with the
>> default /usr/share/dirsrv/schema/10rfc2307.ldif
>>
>> Thanks,
>> Trev
>>
>>
>> On 10 October 2017 at 09:46, Mark Reynolds > > wrote:
>>
>>
>>
>> On 10/10/2017 12:36 PM, Trevor Fong wrote:
>>> Hi Mark and Michael,
>>>
>>> Thanks a lot for your replies.
>>> I've run the setup-ds.pl  (and also
>>> tried setup-ds-admin.pl ),
>>> /etc/dirsrv/slapd-/schema only contains 99user.ldif.
>>> /usr/share/dirsrv/schema does indeed contain all the default
>>> schema files, but it doesn't look like they're copied to the
>>> instance schema dir.
>> Correct, the core schema stays in /usr/share/dirsrv/schema, while
>> custom schema is in the instance directory.
>>
>> Are you running into problems?
>>
>>>
>>> Trev 
>>>
>>> On 10 October 2017 at 08:19, Mark Reynolds >> > wrote:
>>>
>>>
>>>
>>> On 10/10/2017 11:13 AM, Trevor Fong wrote:
>>> > Hi Everyone,
>>> >
>>> > I just did a new install and it looks like no schema files
>>> were included with it?
>>> > I seem to remember that previously, included schema files
>>> would be in /etc/dirsrv/schema and would get copied into any
>>> new instances that were set up.
>>> > However with this install /etc/dirsrv/schema/ only
>>> contained 99user.ldif
>>> > Am I missing something?
>>> Things were changed for the "core" server schema.  It should
>>> be in
>>> /usr/share/dirsrv/schema
>>> >
>>> > Thanks a lot,
>>> > Trev
>>> >
>>> > Here’s what I did:
>>> >
>>> > [root@eldapdch1 tfong]# uname -a
>>> > Linux eldapdch1 3.10.0-693.2.2.el7.x86_64 #1 SMP Sat Sep 9
>>> 03:55:24 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
>>> > [root@eldapdch1 etc]# yum install 389-ds
>>> > Loaded plugins: rhnplugin, search-disabled-repos
>>> > This system is receiving updates from RHN Classic or Red
>>> Hat Satellite.
>>> > Resolving Dependencies
>>> > --> Running transaction check
>>> > ---> Package 389-ds.noarch 0:1.2.2-6.el7 will be installed
>>> > --> Processing Dependency: 389-dsgw for package:
>>> 389-ds-1.2.2-6.el7.noarch
>>> > --> Processing Dependency: 389-ds-console-doc for package:
>>> 389-ds-1.2.2-6.el7.noarch
>>> > --> Processing Dependency: 389-ds-console for package:
>>> 389-ds-1.2.2-6.el7.noarch
>>> > --> Processing Dependency: 389-ds-base for package:
>>> 389-ds-1.2.2-6.el7.noarch
>>> > --> Processing Dependency: 389-console for package:
>>> 389-ds-1.2.2-6.el7.noarch
>>> > --> Processing Dependency: 389-admin-console-doc for
>>> package: 389-ds-1.2.2-6.el7.noarch
>>> > --> Processing Dependency: 389-admin-console for package:
>>> 389-ds-1.2.2-6.el7.noarch
>>> > --> Processing Dependency: 389-admin for package:
>>> 389-ds-1.2.2-6.el7.noarch
>>> > --> Running transaction check
>>> > ---> Package 389-admin.x86_64 0:1.1.46-1.el7 will be installed
>>> > --> Processing Dependency: libadmsslutil.so.0()(64bit) for
>>> package: 389-admin-1.1.46-1.el7.x86_64
>>> > --> Processing Dependency: libadminutil.so.0()(64bit) for
>>> package: 389-admin-1.1.46-1.el7.x86_64
>>> > ---> Package 389-admin-console.noarch 0:1.1.12-1.el7 will
>>> be installed
>>> > ---> Package 

[389-users] Re: New Install Missing Schema Files

[Trevor Fong]

Oh - I get it now; core schema is now immutably maintained in
/usr/share/dirsrv/schema/ and is referenced by each slapd instance.

How do I go about overriding the core schema?
For example, if I wanted to replace 10rfc2307.ldif with 10rfc2307bis.ldif,
what would I do?
Previously, we would remove /etc/dirsrv/slapd-/schema/10rfc2307.ldif
and add /etc/dirsrv/slapd-/schema/10rfc2307bis.ldif
How would we accomplish this now with core schema immutably maintained in
/usr/share/dirsrv/schema/?

Currently I get the fatal error:

[10/Oct/2017:10:07:50.514409639 -0700] - ERR - dse_read_one_file - The
entry cn=schema in file /etc/dirsrv/slapd-eldapdcp1/schema/10rfc2307bis.ldif
(lineno: 1) is invalid, error code 20 (Type or value exists) - object class
nisMap: The name does not match the OID "1.3.6.1.1.1.2.9". Another object
class is already using the name or OID.

because it clashes with the default /usr/share/dirsrv/schema/10rfc2307.ldif

Thanks,
Trev

On 10 October 2017 at 09:46, Mark Reynolds  wrote:

>
>
> On 10/10/2017 12:36 PM, Trevor Fong wrote:
>
> Hi Mark and Michael,
>
> Thanks a lot for your replies.
> I've run the setup-ds.pl (and also tried setup-ds-admin.pl),
> /etc/dirsrv/slapd-/schema only contains 99user.ldif.
> /usr/share/dirsrv/schema does indeed contain all the default schema files,
> but it doesn't look like they're copied to the instance schema dir.
>
> Correct, the core schema stays in /usr/share/dirsrv/schema, while custom
> schema is in the instance directory.
>
> Are you running into problems?
>
>
> Trev
>
> On 10 October 2017 at 08:19, Mark Reynolds  wrote:
>
>>
>>
>> On 10/10/2017 11:13 AM, Trevor Fong wrote:
>> > Hi Everyone,
>> >
>> > I just did a new install and it looks like no schema files were
>> included with it?
>> > I seem to remember that previously, included schema files would be in
>> /etc/dirsrv/schema and would get copied into any new instances that were
>> set up.
>> > However with this install /etc/dirsrv/schema/ only contained 99user.ldif
>> > Am I missing something?
>> Things were changed for the "core" server schema.  It should be in
>> /usr/share/dirsrv/schema
>> >
>> > Thanks a lot,
>> > Trev
>> >
>> > Here’s what I did:
>> >
>> > [root@eldapdch1 tfong]# uname -a
>> > Linux eldapdch1 3.10.0-693.2.2.el7.x86_64 #1 SMP Sat Sep 9 03:55:24 EDT
>> 2017 x86_64 x86_64 x86_64 GNU/Linux
>> > [root@eldapdch1 etc]# yum install 389-ds
>> > Loaded plugins: rhnplugin, search-disabled-repos
>> > This system is receiving updates from RHN Classic or Red Hat Satellite.
>> > Resolving Dependencies
>> > --> Running transaction check
>> > ---> Package 389-ds.noarch 0:1.2.2-6.el7 will be installed
>> > --> Processing Dependency: 389-dsgw for package:
>> 389-ds-1.2.2-6.el7.noarch
>> > --> Processing Dependency: 389-ds-console-doc for package:
>> 389-ds-1.2.2-6.el7.noarch
>> > --> Processing Dependency: 389-ds-console for package:
>> 389-ds-1.2.2-6.el7.noarch
>> > --> Processing Dependency: 389-ds-base for package:
>> 389-ds-1.2.2-6.el7.noarch
>> > --> Processing Dependency: 389-console for package:
>> 389-ds-1.2.2-6.el7.noarch
>> > --> Processing Dependency: 389-admin-console-doc for package:
>> 389-ds-1.2.2-6.el7.noarch
>> > --> Processing Dependency: 389-admin-console for package:
>> 389-ds-1.2.2-6.el7.noarch
>> > --> Processing Dependency: 389-admin for package:
>> 389-ds-1.2.2-6.el7.noarch
>> > --> Running transaction check
>> > ---> Package 389-admin.x86_64 0:1.1.46-1.el7 will be installed
>> > --> Processing Dependency: libadmsslutil.so.0()(64bit) for package:
>> 389-admin-1.1.46-1.el7.x86_64
>> > --> Processing Dependency: libadminutil.so.0()(64bit) for package:
>> 389-admin-1.1.46-1.el7.x86_64
>> > ---> Package 389-admin-console.noarch 0:1.1.12-1.el7 will be installed
>> > ---> Package 389-admin-console-doc.noarch 0:1.1.12-1.el7 will be
>> installed
>> > ---> Package 389-console.noarch 0:1.1.18-1.el7 will be installed
>> > ---> Package 389-ds-base.x86_64 0:1.3.6.1-19.el7_4 will be installed
>> > --> Processing Dependency: 389-ds-base-libs = 1.3.6.1-19.el7_4 for
>> package: 389-ds-base-1.3.6.1-19.el7_4.x86_64
>> > --> Processing Dependency: libnunc-stans.so.0()(64bit) for package:
>> 389-ds-base-1.3.6.1-19.el7_4.x86_64
>> > --> Processing Dependency: libsds.so.0()(64bit) for package:
>> 389-ds-base-1.3.6.1-19.el7_4.x86_64
>> > --> Processing Dependency: libns-dshttpd-1.3.6.1.so()(64bit) for
>> package: 389-ds-base-1.3.6.1-19.el7_4.x86_64
>> > --> Processing Dependency: libslapd.so.0()(64bit) for package:
>> 389-ds-base-1.3.6.1-19.el7_4.x86_64
>> > ---> Package 389-ds-console.noarch 0:1.2.16-1.el7 will be installed
>> > ---> Package 389-ds-console-doc.noarch 0:1.2.16-1.el7 will be installed
>> > ---> Package 389-dsgw.x86_64 0:1.1.11-5.el7 will be installed
>> > --> Running transaction check
>> > ---> Package 389-adminutil.x86_64 0:1.1.21-2.el7 will be installed
>> > ---> Package 389-ds-base-libs.x86_64 0:1.3.6.1-19.el7_4 will be
>> installed
>> 

[389-users] Re: New Install Missing Schema Files

[Mark Reynolds]

On 10/10/2017 12:36 PM, Trevor Fong wrote:
> Hi Mark and Michael,
>
> Thanks a lot for your replies.
> I've run the setup-ds.pl  (and also
> tried setup-ds-admin.pl ),
> /etc/dirsrv/slapd-/schema only contains 99user.ldif.
> /usr/share/dirsrv/schema does indeed contain all the default schema
> files, but it doesn't look like they're copied to the instance schema dir.
Correct, the core schema stays in /usr/share/dirsrv/schema, while custom
schema is in the instance directory.

Are you running into problems?
>
> Trev 
>
> On 10 October 2017 at 08:19, Mark Reynolds  > wrote:
>
>
>
> On 10/10/2017 11:13 AM, Trevor Fong wrote:
> > Hi Everyone,
> >
> > I just did a new install and it looks like no schema files were
> included with it?
> > I seem to remember that previously, included schema files would
> be in /etc/dirsrv/schema and would get copied into any new
> instances that were set up.
> > However with this install /etc/dirsrv/schema/ only contained
> 99user.ldif
> > Am I missing something?
> Things were changed for the "core" server schema.  It should be in
> /usr/share/dirsrv/schema
> >
> > Thanks a lot,
> > Trev
> >
> > Here’s what I did:
> >
> > [root@eldapdch1 tfong]# uname -a
> > Linux eldapdch1 3.10.0-693.2.2.el7.x86_64 #1 SMP Sat Sep 9
> 03:55:24 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
> > [root@eldapdch1 etc]# yum install 389-ds
> > Loaded plugins: rhnplugin, search-disabled-repos
> > This system is receiving updates from RHN Classic or Red Hat
> Satellite.
> > Resolving Dependencies
> > --> Running transaction check
> > ---> Package 389-ds.noarch 0:1.2.2-6.el7 will be installed
> > --> Processing Dependency: 389-dsgw for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-ds-console-doc for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-ds-console for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-ds-base for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-console for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-admin-console-doc for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-admin-console for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-admin for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Running transaction check
> > ---> Package 389-admin.x86_64 0:1.1.46-1.el7 will be installed
> > --> Processing Dependency: libadmsslutil.so.0()(64bit) for
> package: 389-admin-1.1.46-1.el7.x86_64
> > --> Processing Dependency: libadminutil.so.0()(64bit) for
> package: 389-admin-1.1.46-1.el7.x86_64
> > ---> Package 389-admin-console.noarch 0:1.1.12-1.el7 will be
> installed
> > ---> Package 389-admin-console-doc.noarch 0:1.1.12-1.el7 will be
> installed
> > ---> Package 389-console.noarch 0:1.1.18-1.el7 will be installed
> > ---> Package 389-ds-base.x86_64 0:1.3.6.1-19.el7_4 will be installed
> > --> Processing Dependency: 389-ds-base-libs = 1.3.6.1-19.el7_4
> for package: 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > --> Processing Dependency: libnunc-stans.so.0()(64bit) for
> package: 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > --> Processing Dependency: libsds.so.0()(64bit) for package:
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > --> Processing Dependency: libns-dshttpd-1.3.6.1.so
> ()(64bit) for package:
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > --> Processing Dependency: libslapd.so.0()(64bit) for package:
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > ---> Package 389-ds-console.noarch 0:1.2.16-1.el7 will be installed
> > ---> Package 389-ds-console-doc.noarch 0:1.2.16-1.el7 will be
> installed
> > ---> Package 389-dsgw.x86_64 0:1.1.11-5.el7 will be installed
> > --> Running transaction check
> > ---> Package 389-adminutil.x86_64 0:1.1.21-2.el7 will be installed
> > ---> Package 389-ds-base-libs.x86_64 0:1.3.6.1-19.el7_4 will be
> installed
> > --> Finished Dependency Resolution
> >
> > Dependencies Resolved
> >
> >
> 
> =
> > Package                                              Arch       
>                           Version                                 
>           Repository                                           Size
> >
> 
> 

[389-users] Re: New Install Missing Schema Files

[Trevor Fong]

Hi Mark and Michael,

Thanks a lot for your replies.
I've run the setup-ds.pl (and also tried setup-ds-admin.pl),
/etc/dirsrv/slapd-/schema only contains 99user.ldif.
/usr/share/dirsrv/schema does indeed contain all the default schema files,
but it doesn't look like they're copied to the instance schema dir.

Trev

On 10 October 2017 at 08:19, Mark Reynolds  wrote:

>
>
> On 10/10/2017 11:13 AM, Trevor Fong wrote:
> > Hi Everyone,
> >
> > I just did a new install and it looks like no schema files were included
> with it?
> > I seem to remember that previously, included schema files would be in
> /etc/dirsrv/schema and would get copied into any new instances that were
> set up.
> > However with this install /etc/dirsrv/schema/ only contained 99user.ldif
> > Am I missing something?
> Things were changed for the "core" server schema.  It should be in
> /usr/share/dirsrv/schema
> >
> > Thanks a lot,
> > Trev
> >
> > Here’s what I did:
> >
> > [root@eldapdch1 tfong]# uname -a
> > Linux eldapdch1 3.10.0-693.2.2.el7.x86_64 #1 SMP Sat Sep 9 03:55:24 EDT
> 2017 x86_64 x86_64 x86_64 GNU/Linux
> > [root@eldapdch1 etc]# yum install 389-ds
> > Loaded plugins: rhnplugin, search-disabled-repos
> > This system is receiving updates from RHN Classic or Red Hat Satellite.
> > Resolving Dependencies
> > --> Running transaction check
> > ---> Package 389-ds.noarch 0:1.2.2-6.el7 will be installed
> > --> Processing Dependency: 389-dsgw for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-ds-console-doc for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-ds-console for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-ds-base for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-console for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-admin-console-doc for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-admin-console for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Processing Dependency: 389-admin for package:
> 389-ds-1.2.2-6.el7.noarch
> > --> Running transaction check
> > ---> Package 389-admin.x86_64 0:1.1.46-1.el7 will be installed
> > --> Processing Dependency: libadmsslutil.so.0()(64bit) for package:
> 389-admin-1.1.46-1.el7.x86_64
> > --> Processing Dependency: libadminutil.so.0()(64bit) for package:
> 389-admin-1.1.46-1.el7.x86_64
> > ---> Package 389-admin-console.noarch 0:1.1.12-1.el7 will be installed
> > ---> Package 389-admin-console-doc.noarch 0:1.1.12-1.el7 will be
> installed
> > ---> Package 389-console.noarch 0:1.1.18-1.el7 will be installed
> > ---> Package 389-ds-base.x86_64 0:1.3.6.1-19.el7_4 will be installed
> > --> Processing Dependency: 389-ds-base-libs = 1.3.6.1-19.el7_4 for
> package: 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > --> Processing Dependency: libnunc-stans.so.0()(64bit) for package:
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > --> Processing Dependency: libsds.so.0()(64bit) for package:
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > --> Processing Dependency: libns-dshttpd-1.3.6.1.so()(64bit) for
> package: 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > --> Processing Dependency: libslapd.so.0()(64bit) for package:
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> > ---> Package 389-ds-console.noarch 0:1.2.16-1.el7 will be installed
> > ---> Package 389-ds-console-doc.noarch 0:1.2.16-1.el7 will be installed
> > ---> Package 389-dsgw.x86_64 0:1.1.11-5.el7 will be installed
> > --> Running transaction check
> > ---> Package 389-adminutil.x86_64 0:1.1.21-2.el7 will be installed
> > ---> Package 389-ds-base-libs.x86_64 0:1.3.6.1-19.el7_4 will be installed
> > --> Finished Dependency Resolution
> >
> > Dependencies Resolved
> >
> > 
> 
> 
> =
> > Package  Arch
>   Version
> Repository   Size
> > 
> 
> 
> =
> > Installing:
> > 389-ds   noarch
>   1.2.2-6.el7epel
>11 k
> > Installing for dependencies:
> > 389-adminx86_64
>   1.1.46-1.el7   epel
>   391 k
> > 389-admin-consolenoarch
>   1.1.12-1.el7   epel
>   204 k
> > 389-admin-console-doc   

[389-users] Re: New Install Missing Schema Files

[Michal Medvecky]

You have to run setup-ds after package installation

> On 10 Oct 2017, at 17:13, Trevor Fong  wrote:
> 
> Hi Everyone,
> 
> I just did a new install and it looks like no schema files were included with 
> it?
> I seem to remember that previously, included schema files would be in 
> /etc/dirsrv/schema and would get copied into any new instances that were set 
> up.
> However with this install /etc/dirsrv/schema/ only contained 99user.ldif
> Am I missing something?
> 
> Thanks a lot,
> Trev
> 
> Here’s what I did:
> 
> [root@eldapdch1 tfong]# uname -a
> Linux eldapdch1 3.10.0-693.2.2.el7.x86_64 #1 SMP Sat Sep 9 03:55:24 EDT 2017 
> x86_64 x86_64 x86_64 GNU/Linux
> [root@eldapdch1 etc]# yum install 389-ds
> Loaded plugins: rhnplugin, search-disabled-repos
> This system is receiving updates from RHN Classic or Red Hat Satellite.
> Resolving Dependencies
> --> Running transaction check
> ---> Package 389-ds.noarch 0:1.2.2-6.el7 will be installed
> --> Processing Dependency: 389-dsgw for package: 389-ds-1.2.2-6.el7.noarch
> --> Processing Dependency: 389-ds-console-doc for package: 
> 389-ds-1.2.2-6.el7.noarch
> --> Processing Dependency: 389-ds-console for package: 
> 389-ds-1.2.2-6.el7.noarch
> --> Processing Dependency: 389-ds-base for package: 389-ds-1.2.2-6.el7.noarch
> --> Processing Dependency: 389-console for package: 389-ds-1.2.2-6.el7.noarch
> --> Processing Dependency: 389-admin-console-doc for package: 
> 389-ds-1.2.2-6.el7.noarch
> --> Processing Dependency: 389-admin-console for package: 
> 389-ds-1.2.2-6.el7.noarch
> --> Processing Dependency: 389-admin for package: 389-ds-1.2.2-6.el7.noarch
> --> Running transaction check
> ---> Package 389-admin.x86_64 0:1.1.46-1.el7 will be installed
> --> Processing Dependency: libadmsslutil.so.0()(64bit) for package: 
> 389-admin-1.1.46-1.el7.x86_64
> --> Processing Dependency: libadminutil.so.0()(64bit) for package: 
> 389-admin-1.1.46-1.el7.x86_64
> ---> Package 389-admin-console.noarch 0:1.1.12-1.el7 will be installed
> ---> Package 389-admin-console-doc.noarch 0:1.1.12-1.el7 will be installed
> ---> Package 389-console.noarch 0:1.1.18-1.el7 will be installed
> ---> Package 389-ds-base.x86_64 0:1.3.6.1-19.el7_4 will be installed
> --> Processing Dependency: 389-ds-base-libs = 1.3.6.1-19.el7_4 for package: 
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> --> Processing Dependency: libnunc-stans.so.0()(64bit) for package: 
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> --> Processing Dependency: libsds.so.0()(64bit) for package: 
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> --> Processing Dependency: libns-dshttpd-1.3.6.1.so()(64bit) for package: 
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> --> Processing Dependency: libslapd.so.0()(64bit) for package: 
> 389-ds-base-1.3.6.1-19.el7_4.x86_64
> ---> Package 389-ds-console.noarch 0:1.2.16-1.el7 will be installed
> ---> Package 389-ds-console-doc.noarch 0:1.2.16-1.el7 will be installed
> ---> Package 389-dsgw.x86_64 0:1.1.11-5.el7 will be installed
> --> Running transaction check
> ---> Package 389-adminutil.x86_64 0:1.1.21-2.el7 will be installed
> ---> Package 389-ds-base-libs.x86_64 0:1.3.6.1-19.el7_4 will be installed
> --> Finished Dependency Resolution
> 
> Dependencies Resolved
> 
> =
> Package  Arch 
>  VersionRepository
>Size
> =
> Installing:
> 389-ds   noarch   
>  1.2.2-6.el7epel  
>11 k
> Installing for dependencies:
> 389-adminx86_64   
>  1.1.46-1.el7   epel  
>   391 k
> 389-admin-consolenoarch   
>  1.1.12-1.el7   epel  
>   204 k
> 389-admin-console-docnoarch   
>  1.1.12-1.el7   epel  
>45 k
> 389-adminutilx86_64   
>  1.1.21-2.el7   epel  
>73 k
> 389-console  noarch