Thursday, August 27, 2020

[389-users] Re: Installing an instance of 389ds from scratch - how?

On 27 Aug 2020, at 15:32, Mark Reynolds <mreynolds@redhat.com> wrote:

All of this works correctly for me:


[general]
config_version = 2
full_machine_name = localhost.localdomain
start = False

[slapd]
instance_name = graham
port = 389
root_dn = cn=dm
root_password = PASSWORD
self_sign_cert = False

[backend-userroot]
sample_entries = yes
suffix = dc=example,dc=com


Server is created, but not started, and TLS is disabled.  Did I miss a step?

No luck for me:

[root@gatekeeper dirsrv]# cat /etc/dirsrv/slapd-default.inf
[general]
config_version = 2
full_machine_name = localhost.localdomain
start = False

[slapd]
instance_name = default
port = 389
root_dn = cn=dm
root_password = PASSWORD
self_sign_cert = False

[backend-userroot]
sample_entries = yes
suffix = dc=example,dc=com
[root@gatekeeper dirsrv]# /usr/sbin/dscreate from-file /etc/dirsrv/slapd-default.inf
Starting installation...
Error: Can't contact LDAP server - 107 - Transport endpoint is not connected
[root@gatekeeper dirsrv]# ps -auxwww | grep slap
dirsrv     25283  1.6  2.4 971356 197544 ?       Ssl  16:55   0:02 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-default -i /run/dirsrv/slapd-default.pid
root       25360  0.0  0.0 221900  1092 pts/0    S+   16:58   0:00 grep --color=auto slap

Running dscreate through strace shows that despite being told the name of the server is localhost.localdomain, and despite being told not to start the server, dscreate tries to connect to the server using the FQDN of the machine on port 389, and not localhost.localdomain.

Regards,
Graham

No comments:

Post a Comment