FreeRADIUS is commonly used with Directory Server. However, if installed on the same system it way fail to start often due to inability to contact the ldap server.
I have tried to contact the FreeRADIUS developers to add the correct systemd depends in their unit files to no success (the issue was ignored).
As a result, we should add a "Before" statement to our unitfiles to prevent radiusd starting until ldap is available.
<img alt="0001-Ticket-49294-radiusd-before-in-unit-file.patch" src="/389-ds-base/issue/raw/4c081a9f998c7c72335a569db2bea3d2041c856026de08f1f05e0519eb371bcd-0001-Ticket-49294-radiusd-before-in-unit-file.patch" />
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to review - Custom field type adjusted to defect
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: review)
commit 62a8db6ca13c7305737d9962b9656a58f6f17d0b To ssh://git@pagure.io/389-ds-base.git dd7a9fa..b23e560 master -> master
Metadata Update from @firstyear: - Issue status updated to: Closed (was: Open)
Metadata Update from @firstyear: - Issue close_status updated to: fixed
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2353
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.