When I add an additional instance to my server, an error is displayed at the end of the installation and the LDAPS port is not listening.
389-ds-base-1.4.1.1-20190306git0ad1dd2ed.el8.x86_64
# dscreate interactive Install Directory Server (interactive mode) =========================================== Enter system's hostname [server.example.com]: Use strict hostname verification (set to "no" if using GSSAPI behind a load balancer) [yes]: Enter the instance name [server]: Enter port number []: 1389 Create self-signed certificate database [yes]: Enter secure port number []: 1636 Enter Directory Manager DN [cn=Directory Manager]: Enter the Directory Manager password: Confirm the Directory Manager Password: Enter the database suffix (or enter "none" to skip) [dc=server,dc=example,dc=com]: Create sample entries in the suffix [no]: Create just the top suffix entry [no]: yes Are you ready to install? [no]: yes Starting installation... Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv@server.service → /usr/lib/systemd/system/dirsrv@.service. Error: 'start'
# netstat -tulpn | egrep "1389|1636" tcp6 0 0 :::1636 :::* LISTEN 4375/ns-slapd tcp6 0 0 :::1389 :::* LISTEN 4375/ns-slapd
If you manually restart the instance after the installation, LDAPS is in listening mode, too.
The error log contains right after the installation:
[06/Mar/2019:11:36:09.506895225 +0100] - INFO - main - 389-Directory/1.4.1.1.20190306git0ad1dd2ed B2019.065.104 starting up [06/Mar/2019:11:36:10.147643335 +0100] - INFO - PBKDF2_SHA256 - Based on CPU performance, chose 2048 rounds [06/Mar/2019:11:36:10.159011548 +0100] - NOTICE - ldbm_back_start - found 2037856k physical memory [06/Mar/2019:11:36:10.161478850 +0100] - NOTICE - ldbm_back_start - found 1563116k available [06/Mar/2019:11:36:10.163874228 +0100] - NOTICE - ldbm_back_start - cache autosizing: db cache: 50946k [06/Mar/2019:11:36:10.166235569 +0100] - NOTICE - ldbm_back_start - total cache size: 41735290 B; [06/Mar/2019:11:36:10.468936336 +0100] - INFO - slapd_daemon - slapd started. Listening on All Interfaces port 1389 for LDAP requests [06/Mar/2019:11:36:10.686147176 +0100] - INFO - postop_modify_config_dse - The change of nsslapd-securePort will not take effect until the server is restarted [06/Mar/2019:11:36:10.701736861 +0100] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000 [06/Mar/2019:11:36:10.848187811 +0100] - INFO - postop_modify_config_dse - The change of nsslapd-ldapifilepath will not take effect until the server is restarted [06/Mar/2019:11:36:10.872512126 +0100] - INFO - postop_modify_config_dse - The change of nsslapd-ldapilisten will not take effect until the server is restarted
<img alt="error.log" src="/389-ds-base/issue/raw/files/5eb8a81cae749ed8af5aceb7486922ece7c27668d9a94b5274f069267ee367a9-error.log" />
Metadata Update from @spichugi: - Issue assigned to spichugi
https://pagure.io/389-ds-base/pull-request/50266
Metadata Update from @spichugi: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Metadata Update from @spichugi: - Issue close_status updated to: fixed - 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/3322
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.