RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1715410 - legacy-tools: start-dirsrv doesn't start the instances
Summary: legacy-tools: start-dirsrv doesn't start the instances
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-30 09:40 UTC by Viktor Ashirov
Modified: 2020-04-28 16:01 UTC (History)
9 users (show)

Fixed In Version: 389-ds-base-1.4.2.4-1.module+el8.2.0+4699+cf2da360
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:01:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1703 0 None None None 2020-04-28 16:01:36 UTC

Description Viktor Ashirov 2019-05-30 09:40:56 UTC 
Description of problem:
start-dirsrv no longer starts the installed instances, it tries to look them up in /etc/sysconfig, but it is no longer created.

Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.3-1.module+el8.1.0+3259+a5bc8ad3.x86_64


How reproducible:
always

Steps to Reproduce:
1. Create an instance, stop it.
2. Run start-dirsrv
3.

Actual results:
Instance is not running

Expected results:
Instance should be up and running

Additional info:
Comment 1 Viktor Ashirov 2019-07-09 19:51:37 UTC 
Still present in 389-ds-base-1.4.1.3-3.module+el8.1.0+3533+f8225121.x86_64
Comment 4 Viktor Ashirov 2019-12-03 13:40:09 UTC 
Builds tested:
389-ds-base-1.4.2.4-4.module+el8.2.0+4930+d4051b3a.x86_64
389-ds-base-legacy-tools-1.4.2.4-4.module+el8.2.0+4930+d4051b3a.x86_64

{start,stop,status,restart}-dirsrv commands work as expected with the legacy tools installed:

[root@server-rhel8 ds]# stop-dirsrv 
Stopping instance "server-rhel8"
[root@server-rhel8 ds]# start-dirsrv 
Starting instance "server-rhel8"
[root@server-rhel8 ds]# restart-dirsrv 
Restarting instance "server-rhel8"
[root@server-rhel8 ds]# status-dirsrv 
● dirsrv - 389 Directory Server server-rhel8.
   Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/dirsrv@.service.d
           └─custom.conf
   Active: active (running) since Tue 2019-12-03 13:38:47 UTC; 4s ago
  Process: 2439 ExecStartPre=/usr/libexec/dirsrv/ds_systemd_ask_password_acl /etc/dirsrv/slapd-server-rhel8/dse.ldif (code=exited, status=0/SUCCESS)
 Main PID: 2444 (ns-slapd)
   Status: "slapd started: Ready to process requests"
   CGroup: /machine.slice/libpod-9a87fb2afc5f86ff07bb4b0bb1e7bcbe42fe09f05b20509dce07ffa4fa1c7399.scope/system.slice/system-dirsrv.slice/dirsrv
           └─2444 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-server-rhel8 -i /run/dirsrv/slapd-server-rhel8.pid

Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.356162776 +0000] - NOTICE - ldbm_back_start - found 65300384k physical memory
Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.360290730 +0000] - NOTICE - ldbm_back_start - found 59679340k available
Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.364440389 +0000] - NOTICE - ldbm_back_start - cache autosizing: db cache: 1572864k
Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.368586250 +0000] - NOTICE - ldbm_back_start - cache autosizing: userroot entry cache (1 total): 4521984k
Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.373147161 +0000] - NOTICE - ldbm_back_start - cache autosizing: userroot dn cache (1 total): 524288k
Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.377684736 +0000] - NOTICE - ldbm_back_start - total cache size: 6777995264 B;
Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.709866984 +0000] - INFO - slapd_daemon - slapd started.  Listening on All Interfaces port 389 for LDAP requests
Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.715701181 +0000] - INFO - slapd_daemon - Listening on All Interfaces port 636 for LDAPS requests
Dec 03 13:38:47 server-rhel8.example.com ns-slapd[2444]: [03/Dec/2019:13:38:47.719863498 +0000] - INFO - slapd_daemon - Listening on /var/run/slapd-server-rhel8.socket for LDAPI requests
Dec 03 13:38:47 server-rhel8.example.com systemd[1]: Started 389 Directory Server server-rhel8..


Marking as VERIFIED, SanityOnly.
Comment 6 errata-xmlrpc 2020-04-28 16:01:20 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1703
Note You need to log in before you can comment on or make changes to this bug.