389-ds Can't delete groups/users

Hi all,

Tried this on tumbleweed but also on Leap 15.5 and got the same result :frowning:

I’ve been following the SuSE guide to setting up 389-ds available at :

I’ve been able to setup a default instance with dscreate

dscreate from-file traken-test-template.txt

This shows up ok, and I can create users/groups

ldap-test:~ # dsidm traken-test group list
demo_group
test

But when I try and delete a group I get :
ldap-test:~ # dsidm traken-test group delete
Enter dn to delete : test
Deleting Group test :
Type ‘Yes I am sure’ to continue: Yes I am sure
Error: The entry does not exist

What could be wrong?
Also is there a flag I can pass to dsidm to not have to type ‘Yes I am sure’ every time, this will make automating stuff a pain…

I’ll include below my create script (with comments stripped) and my ~/.dsrc

Cheers.

Phill.

[general]
full_machine_name = ldap-test.ftt
start = True

[slapd]
db_lib = mdb
instance_name = traken-test
ldapi = /run/slapd-{instance_name}.socket
mdb_max_size = 21138142003.2
port = 389
root_password = redacted
secure_port = 636
self_sign_cert = True
elf_sign_cert_valid_months = 24

[backend-userroot]
changelog_max_age = 7d
changelog_max_entries = -1
create_suffix_entry = False
enable_replication = False
replica_binddn = cn=replication manager,cn=config
replica_bindgroup =
replica_bindpw =
replica_id = 1
replica_role = supplier
require_index = False
hangelog_max_entries = -1
create_suffix_entry = False
enable_replication = False
replica_binddn = cn=replication manager,cn=config
replica_bindgroup =
replica_bindpw =
replica_id = 1
replica_role = supplier
require_index = False
sample_entries = yes
suffix = dc=traken-test,dc=ftt

and my ~/.dsrc[traken-test]

uri = ldapi://%%2fvar%%2frun%%2fslapd-traken-test.socket

basedn = dc=traken-test,dc=ftt
binddn = cn=Directory Manager

Wild guess here … type it WITH the quote marks, as in
‘Yes I am sure’
(or maybe double quote marks)
… vs
Yes I am sure

If it really needs DN, then test is obviously wrong. Please familarize yourself with LDAP definitions, in particular, what DN (Distinguished Name) is. Briefly looking at dsidm manual page, some commands specify CN (which you want to use), some specify DN. Try full DN.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.