Installing 389-ds-base doesn't appear to result in a working LDAP server

  • Open
  • quality assurance status badge
2 participants
  • Brant Gardner
  • Ricardo Wurmus
Submitted by
Brant Gardner
Brant Gardner wrote on 10 Jul 2019 20:02
Installing 389-ds-base doesn't appear to result in a working L DAP server
(address .
I used the quickstart documentation for all my testing, located here:

Initially I ran into trouble because the 'dirsrv' user and group are apparently expected to already exist, so I added this to my config.scm and ran guix system reconfigure:

(groups (cons*
;; To support 389-ds-base
(user-group (name "dirsrv"))

(users (cons*
;; To support 389-ds-base
(name "dirsrv")
(comment "LDAP Server User")
(group "users")
(supplementary-groups '("netdev" "dirsrv"))
(home-directory "/home/dirsrv"))

After this, I generated a template config file with:

# dscreate create-template > gardner.inf

Then I read through the resulting template file and modified only these values:
- password
- server FQDN
- instance name (gardner)
- selinux (False)
- suffix (dc=gardner,dc=local)

Finally I tried to create the new instance with:

# dscreate from-file /root/gardner.inf

This said "Starting installation...", then paused for about 60 seconds and then said:

Error: Failed to start DS, removing incomplete installation...

Note that even though it claims to, it did not actually remove the incomplete installation, as trying the same command again results in:

Starting installation...
Error: Another instance named 'gardner' may already exist

Checking the logs, I found only this line in /var/log/debug that seems related:

Jul 10 12:49:09 localhost ns-slapd: looking for plugins in '/usr/lib/x86_64-linux-gnu', failed to open directory, error: No such file or directory

Thanks for any suggestions,

Brant Gardner
Attachment: file
Ricardo Wurmus wrote on 11 Jul 2019 11:06
Re: bug#36581: Installing 389-ds-base doesn't appear to result in a working LDAP server
(name . Brant Gardner)(address . .
Hi Brant,

that’s right. Installing just 389-ds-base isn’t going to be enough and
the scripts it comes with are less than helpful.

In the Guix System overarching configuration (involving configuration
files, creation of groups and user accounts, starting of daemons, etc)
is done via system services.

I was just about to recommend a certain service … but then realized that
I never actually finished it and the (gnu services ldap) module is only
provided by a file in my personal copy of the Guix repository!

I’ll make finishing this a priority once I’m back from vacation this

Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to

To respond to this issue using the mumi CLI, first switch to it
mumi current 36581
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch