Bug 2121747 - dscreate error, cannot start ns-slapd with custom db_dir path, incorrect sub dir permissions
Summary: dscreate error, cannot start ns-slapd with custom db_dir path, incorrect sub ...
Keywords:
Status: CLOSED DUPLICATE of bug 1924569
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Command Line Utilities
Version: 11.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-26 13:57 UTC by Pierre Rogier
Modified: 2024-03-25 18:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-26 14:07:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 4592 0 None open dscreate error, cannot start ns-slapd with custom db_dir path, incorrect sub dir permissions 2022-08-26 13:59:30 UTC

Description Pierre Rogier 2022-08-26 13:57:30 UTC 
Description of problem:
   dscreate fails when using custom path with the db_dir parameter.


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
See reproduction steps in github 

Actual results:
  dscreate fails because newly created instance fails to start


Expected results:
  instance should be successfully started and dscreate should success.

Additional info:
  There are several issues related to how the filesystem directories are created within lib389/instance/setup.py: ( ownership, permission and selinux label are not properly set)
Comment 1 Pierre Rogier 2022-08-26 14:07:02 UTC 

*** This bug has been marked as a duplicate of bug 1924569 ***
Note You need to log in before you can comment on or make changes to this bug.