Posible bug in Schema Reload plug-in validator?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I'm running 389DS version 1.4.4.11-2 on Debian Bullseye and when I try dynamic schema reload I get this error:

[08/Apr/2022:09:50:38.481339672 +0200] - INFO - schemareload - schemareload_thread - Schema reload task starts (schema dir: default) ...
[08/Apr/2022:09:50:38.528960187 +0200] - ERR - parse_attr_str - Cannot find parent attribute type "certSubjectDN"
[08/Apr/2022:09:50:38.534608629 +0200] - ERR - dse_read_one_file - The entry cn=schema in file /etc/dirsrv/slapd-ldap33/schema/96radoc.ldif (lineno: 1) is invalid, error code 21 (Invalid syntax) - attribute type raOfficerSubjectDN: Missing parent attribute syntax OID
[08/Apr/2022:09:50:38.539912128 +0200] - ERR - schema_reload - slapi_validate_schema_files failed
[08/Apr/2022:09:50:38.544588257 +0200] - ERR - schemareload - schemareload_thread - Schema validation failed.

raOfficerSubjectDN is defined this way:

attributeTypes: ( raOfficerSubjectDN-oid
  NAME 'raOfficerSubjectDN'
  DESC 'RA office subject  DN; KDO'
  SUP certSubjectDN
  SINGLE-VALUE
  X-ORIGIN 'CESNET RA DOC'
 )

and certSubjectDN is defined:

attributeTypes: ( certSubjectDN-oid
  NAME 'certsubjectdn'
  DESC 'CESNET Attribute'
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
  X-ORIGIN 'CESNET'
 )

It is interesting that when I restart whole server it starts correctly and in schema is attribute present:

ldapsearch -H ldaps://ldap33 -x -b 'cn=schema' -o ldif-wrap=no +
...
attributeTypes: ( raOfficerSubjectDN-oid NAME 'raOfficerSubjectDN' DESC 'RA office subject DN; KDO' SUP certSubjectDN SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE X-ORIGIN 'CESNET RA DOC' )

I was looking for attributeType syntax and in RFC 2252 is written:

... Servers SHOULD provide at least one of the "SUP" and "SYNTAX"
fields for each AttributeTypeDescription.
Isn't there a bug in validator which is used by Schema Reload plug-in?

Best regards
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux