Creating an instance fails if you use a different LDAP port than 389, or 636 for LDAPS.
READY: Preparing installation for demo READY: Beginning installation for demo Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv@demo.service → /usr/lib/systemd/system/dirsrv@.service. Job for dirsrv@demo.service failed because the control process exited with error code. See "systemctl status dirsrv@demo.service" and "journalctl -xe" for details. Error: Command '['/usr/bin/systemctl', 'start', 'dirsrv@demo']' returned non-zero exit status 1.
The script must allow the port.
Also the config file allows to set several paths, such as for the database. The script must also take care of the SELinux context of these directories, if "selinux = True" - which is the default.
This is a duplicate of https://pagure.io/389-ds-base/issue/49705
Metadata Update from @vashirov: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
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/2851
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: duplicate)