https://bugs.openldap.org/show_bug.cgi?id=10021

          Issue ID: 10021
           Summary: Cannot insert data into wiredtiger backend
           Product: OpenLDAP
           Version: 2.6.4
          Hardware: x86_64
                OS: Linux
            Status: UNCONFIRMED
          Keywords: needs_review
          Severity: normal
          Priority: ---
         Component: backends
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

I have a test system running OpenLDAP 2.6.4 linked against WiredTiger 11.1.0
running on a RHEL9.1-based system. Running kernel is 6.1.16, filesystem is XFS.

back_wt.la was added to cn=module and a simple olcDatabase=wt was created like:

dn: olcDatabase=wt
objectClass: olcDatabaseConfig
objectClass: olcWtConfig
olcDatabase: wt
olcDbDirectory: /var/lib/ldap
olcSuffix: dc=fdf,dc=net
olcLimits: {0}dn.base="cn=root,dc=fdf,dc=net" time.soft=unlimited time.hard=u
 nlimited size.soft=unlimited size.hard=unlimited
olcRootDN: cn=root,dc=fdf,dc=net
olcWtConfig: create
olcDbIndex: objectClass,uid,gidNumber,uidNumber pres,eq
olcDbIndex: ou,cn,mail pres,eq,sub
structuralObjectClass: olcWtConfig

I start slapd and it creates the database files correctly. I then go and try to
create the container with a simple .ldif and ldapadd:

dn: dc=fdf,dc=net
objectClass: dcObject
objectClass: organization
o: FDF
dc: fdf

That generates:

[1677801597:758327][83158:0x55b4158fb640], file:dn2id.wt, WT_CURSOR.insert:
[WT_VERB_DEFAULT][ERROR]: __wt_txn_id_check, 1339: write operations are not
supported in read-committed or read-uncommitted transactions.: Operation not
supported
Mar  2 15:59:57 slapd[83158]: wt_dn2id_add: insert failed: Operation not
supported (95)

That comes from WiredTiger @
https://github.com/wiredtiger/wiredtiger/blob/5a032be765b1ebd9bb789e837cd00cc572dd689b/src/include/txn_inline.h#L1340-L1351
but I don't seem to understand why it's happening on a simple add? Am I missing
something obvious?

-- 
You are receiving this mail because:
You are on the CC list for the issue.

Reply via email to