I have a service on my 389-ds host that is configured in systemd to depend on
389-ds and start after dirsrv.target. However, unless I add a sleep
(ExecStartPre systemd stanza) to the startup of that other service it fails to
start as 389 is not fully ready. I can see that systemd is
Nice one! Happy to be of help and thanks for being so responsive to the
initial query.
Dave
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Hi Mark,
I can confirm removing it from adm.conf prevents it working. Adding it back,
it works again.
Possibly there's another means that normally ensures the correct range is set
for the config DS connection?
The function returning the error that shows up in the log with the debug build
is
Great! Thanks very much!
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
I figured out the issue here so updating for anyone else who may suffer this
problem.
It appears that when things are locked down to prevent use of SSLv3, if you
want to use SSL with the Config DS from the admin server, you also need to
specify the min/max SSL/TLS version in adm.conf.
I added
I believe that should all be ok. It's using the same key/cert as the DS
although I've also tried different keys/certs. There is an intermediate cert
in the chain, but in Manage Certs in both DS and admin server the trust chain
seems to appear ok.
I can contact the admin server over https,
I am having difficulty getting the config DS connection working over TLS. When
I enable this and attempt to log into the console, I receive an "Authentication
Failed" error.
The admin server log shows:
[Tue Jun 13 21:34:16.649391 2017] [:error] [pid 2246:tid 140216580957952] Could
not bind as
