Hi, folks,
Sorry for the slow response. Things got busy.On 11/21/25 7:21 PM, William Brown via 389-users wrote:What "brand" of directory server are you moving from? IIRC there might be some format differences between the schema in some directories compared to 389-ds.
I'm moving from OpenDJ.Also what makes you think it's "not working"? Does your imported schema appear in cn=schema if you query it?
The imported schema does appear. However, at least one attribute is acting wonky. I can't load an ldif file containing it. I get this:
#!ERROR [LDAP result code 65 - objectClassViolation] attribute "mailUserStatus" not allowed
If you added your schema definitions, 'mailUserStatus' should be present in the schema. You may search the attribute on suffix 'cn=schema' with 'attributetypes' and 'objectclasses' attributes to confirm they are available. If a definition can not be loaded you will find a error message in error log.
The above message means that added/updated entry has not the objectclass allowing 'mailUserStatus'. Looking in access logs for err=65 you will identify what is the target entry.
Entries which do have it show it in the Apache Directory browser in italics and are completely uncapitalized.
On Sat, Nov 22, 2025 at 11:55 AM Mark Reynolds <mareynol@redhat.com> wrote:Also, where are you moving it to exactly? Did you restart the server or run the schema reload task afterwards?
I couldn't tell from the documentation whether to put it into /etc/dirserv/schema or /etc/dirserv/slapd-mail/schema, so I put it into both and restarted the server.
I suggest that you use UI or dsconf to update your schema. Else you can manually drop it in schema directory see https://docs.redhat.com/en/documentation/red_hat_directory_server/13/html/management_configuration_and_operations/managing-the-directory-schema#manually-creating-a-custom-schema-file
Thanks,
John A
No comments:
Post a Comment