[389-users] Re: issue with fresh install of directory server

[William Brown]

Probably worth sanity checking:

yum whatprovides '/etc/dirsrv/config/certmap.conf' to see why that's missing -
that directory *should* exist and comes from the rpm I believe. 

%config(noreplace)%{_sysconfdir}/%{pkgname}/config/certmap.conf

That's the rpm spec line from the RH 389-ds-base pkg, so I wonder if something went
wrong in your pkg install or similar? 

This may be in "backup if needed and remove the instance and try again"
territory. IE remove-ds.pl. It's probably wise to also yum reinstall 389-ds-base and
check /etc/dirsrv to ensure config was created. 

>  On 21 Aug 2019, at 10:13, Chase Miller <chasejmiller(a)gmail.com&gt;
> wrote:
>  
>  pwd
>  /etc/dirsrv
>  [root@xxxxxx dirsrv]# ls -l
>  total 0
>  drwxrwx--- 3 dirsrv dirsrv 61 Aug 19 13:41 slapd-xxxxxxx
>  
>  On Tue, Aug 20, 2019 at 6:58 PM William Brown <wbrown(a)suse.de&gt; wrote:
>  
>  
>  > On 20 Aug 2019, at 23:27, Chase Miller <chasejmiller(a)gmail.com&gt; wrote:
>  > 
>  >  ss -tlnp
>  > State      Recv-Q Send-Q Local Address:Port               Peer Address:Port     
>  > LISTEN     0      100    127.0.0.1:25                       *:*                  
> users:(("master",pid=1439,fd=13))
>  > LISTEN     0      128          *:22                       *:*                  
> users:(("sshd",pid=1233,fd=3))
>  > LISTEN     0      100        ::1:25                      :::*                  
> users:(("master",pid=1439,fd=14))
>  > LISTEN     0      128         :::22                      :::*                  
> users:(("sshd",pid=1233,fd=4))
>  
>  Okay, so it's not running, that's why you can't contact it. 
>  
>  > 
>  > 
>  >  cat /var/log/dirsrv/slapd-xxxxxx/errors
>  >         389-Directory/1.3.8.4 B2019.210.1719
>  >         xxxx.xxxx.xxxxx:389 (/etc/dirsrv/slapd-xxxxxxx)
>  > 
>  > [19/Aug/2019:08:50:24.723398253 -0500] - INFO -
> ldbm_instance_config_cachememsize_set - force a minimal value 512000
>  > [19/Aug/2019:08:50:24.733855781 -0500] - INFO - dblayer_instance_start - Import is
> running with nsslapd-db-private-import-mem on; No other process is allowed to access the
> database
>  > [19/Aug/2019:08:50:24.735184817 -0500] - INFO - check_and_set_import_cache -
> pagesize: 4096, available bytes 7757774848, process usage 18108416
>  > [19/Aug/2019:08:50:24.736206673 -0500] - INFO - check_and_set_import_cache - Import
> allocates 3030380KB import cache.
>  > [19/Aug/2019:08:50:24.832157963 -0500] - INFO - import_main_offline - import
> userRoot: Beginning import job...
>  > [19/Aug/2019:08:50:24.833239307 -0500] - INFO - import_main_offline - import
> userRoot: Index buffering enabled with bucket size 100
>  > [19/Aug/2019:08:50:25.034047159 -0500] - INFO - import_producer - import userRoot:
> Processing file "/tmp/ldifE5J2Ye.ldif"
>  > [19/Aug/2019:08:50:25.035917337 -0500] - INFO - import_producer - import userRoot:
> Finished scanning file "/tmp/ldifE5J2Ye.ldif" (9 entries)
>  > [19/Aug/2019:08:50:25.536444284 -0500] - INFO - import_monitor_threads - import
> userRoot: Workers finished; cleaning up...
>  > [19/Aug/2019:08:50:25.737885613 -0500] - INFO - import_monitor_threads - import
> userRoot: Workers cleaned up.
>  > [19/Aug/2019:08:50:25.739150864 -0500] - INFO - import_main_offline - import
> userRoot: Cleaning up producer thread...
>  > [19/Aug/2019:08:50:25.744587334 -0500] - INFO - import_main_offline - import
> userRoot: Indexing complete.  Post-processing...
>  > [19/Aug/2019:08:50:25.745613563 -0500] - INFO - import_main_offline - import
> userRoot: Generating numsubordinates (this may take several minutes to complete)...
>  > [19/Aug/2019:08:50:25.749532490 -0500] - INFO - import_main_offline - import
> userRoot: Generating numSubordinates complete.
>  > [19/Aug/2019:08:50:25.751110348 -0500] - INFO - ldbm_get_nonleaf_ids - import
> userRoot: Gathering ancestorid non-leaf IDs...
>  > [19/Aug/2019:08:50:25.752032364 -0500] - INFO - ldbm_get_nonleaf_ids - import
> userRoot: Finished gathering ancestorid non-leaf IDs.
>  > [19/Aug/2019:08:50:25.754209592 -0500] - INFO - ldbm_ancestorid_new_idl_create_index
> - import userRoot: Creating ancestorid index (new idl)...
>  > [19/Aug/2019:08:50:25.755417599 -0500] - INFO - ldbm_ancestorid_new_idl_create_index
> - import userRoot: Created ancestorid index (new idl).
>  > [19/Aug/2019:08:50:25.760432780 -0500] - INFO - import_main_offline - import
> userRoot: Flushing caches...
>  > [19/Aug/2019:08:50:25.763124185 -0500] - INFO - import_main_offline - import
> userRoot: Closing files...
>  > [19/Aug/2019:08:50:25.788462261 -0500] - INFO - dblayer_pre_close - All database
> threads now stopped
>  > [19/Aug/2019:08:50:25.790360743 -0500] - INFO - import_main_offline - import
> userRoot: Import complete.  Processed 9 entries in 1 seconds. (9.00 entries/sec)
>  > [19/Aug/2019:08:50:26.025795802 -0500] - INFO - main - 389-Directory/1.3.8.4
> B2019.210.1719 starting up
>  > [19/Aug/2019:08:50:30.371320559 -0500] - INFO -
> ldbm_instance_config_cachememsize_set - force a minimal value 512000
>  > [19/Aug/2019:08:50:30.380827675 -0500] - NOTICE - ldbm_back_start - found 8009548k
> physical memory
>  > [19/Aug/2019:08:50:30.382186259 -0500] - NOTICE - ldbm_back_start - found 7572380k
> available
>  > [19/Aug/2019:08:50:30.383287757 -0500] - NOTICE - ldbm_back_start - cache
> autosizing: db cache: 200238k
>  > [19/Aug/2019:08:50:30.384495330 -0500] - NOTICE - ldbm_back_start - cache
> autosizing: userRoot entry cache (1 total): 589824k
>  > [19/Aug/2019:08:50:30.390978513 -0500] - NOTICE - ldbm_back_start - cache
> autosizing: userRoot dn cache (1 total): 65536k
>  > [19/Aug/2019:08:50:30.392881893 -0500] - NOTICE - ldbm_back_start - total cache
> size: 784792534 B;
>  > [19/Aug/2019:08:50:30.394820717 -0500] - INFO - dblayer_start - Resizing db cache
> size: 3103109939 -> 164035542
>  > [19/Aug/2019:08:50:30.556808235 -0500] - INFO - slapd_daemon - slapd started. 
> Listening on All Interfaces port 389 for LDAP requests
>  > [19/Aug/2019:08:53:05.491308203 -0500] - INFO - op_thread_cleanup - slapd shutting
> down - signaling operation threads - op stack size 0 max work q size 0 max work q stack
> size 0
>  > [19/Aug/2019:08:53:05.500474342 -0500] - INFO - slapd_daemon - slapd shutting down -
> closing down internal subsystems and plugins
>  > [19/Aug/2019:08:53:05.508437708 -0500] - INFO - dblayer_pre_close - Waiting for 4
> database threads to stop
>  > [19/Aug/2019:08:53:05.632310190 -0500] - INFO - dblayer_pre_close - All database
> threads now stopped
>  > [19/Aug/2019:08:53:05.642993541 -0500] - INFO - ldbm_back_instance_set_destructor -
> Set of instances destroyed
>  > [19/Aug/2019:08:53:05.644388927 -0500] - INFO - connection_post_shutdown_cleanup -
> slapd shutting down - freed 0 work q stack objects - freed 0 op stack objects
>  > [19/Aug/2019:08:53:05.645425720 -0500] - INFO - main - slapd stopped.
>  > [19/Aug/2019:09:15:43.069475986 -0500] - INFO - main - 389-Directory/1.3.8.4
> B2019.210.1719 starting up
>  > [19/Aug/2019:09:15:47.502679129 -0500] - INFO -
> ldbm_instance_config_cachememsize_set - force a minimal value 512000
>  > [19/Aug/2019:09:15:47.514913346 -0500] - NOTICE - ldbm_back_start - found 8009548k
> physical memory
>  > [19/Aug/2019:09:15:47.515913264 -0500] - NOTICE - ldbm_back_start - found 7619740k
> available
>  > [19/Aug/2019:09:15:47.521731363 -0500] - NOTICE - ldbm_back_start - cache
> autosizing: db cache: 200238k
>  > [19/Aug/2019:09:15:47.531738396 -0500] - NOTICE - ldbm_back_start - cache
> autosizing: userRoot entry cache (1 total): 589824k
>  > [19/Aug/2019:09:15:47.537277994 -0500] - NOTICE - ldbm_back_start - cache
> autosizing: userRoot dn cache (1 total): 65536k
>  > [19/Aug/2019:09:15:47.541163537 -0500] - NOTICE - ldbm_back_start - total cache
> size: 835124182 B;
>  > [19/Aug/2019:09:15:47.687939227 -0500] - INFO - slapd_daemon - slapd started. 
> Listening on All Interfaces port 389 for LDAP requests
>  > [19/Aug/2019:13:37:30.365982188 -0500] - INFO - op_thread_cleanup - slapd shutting
> down - signaling operation threads - op stack size 0 max work q size 0 max work q stack
> size 0
>  > [19/Aug/2019:13:37:30.367924032 -0500] - INFO - slapd_daemon - slapd shutting down -
> waiting for 16 threads to terminate
>  > [19/Aug/2019:13:37:30.378443550 -0500] - INFO - slapd_daemon - slapd shutting down -
> closing down internal subsystems and plugins
>  > [19/Aug/2019:13:37:30.384076053 -0500] - INFO - dblayer_pre_close - Waiting for 4
> database threads to stop
>  > [19/Aug/2019:13:37:30.683501119 -0500] - INFO - dblayer_pre_close - All database
> threads now stopped
>  > [19/Aug/2019:13:37:30.693095235 -0500] - INFO - ldbm_back_instance_set_destructor -
> Set of instances destroyed
>  > [19/Aug/2019:13:37:30.694587104 -0500] - INFO - connection_post_shutdown_cleanup -
> slapd shutting down - freed 0 work q stack objects - freed 0 op stack objects
>  > [19/Aug/2019:13:37:30.695541469 -0500] - INFO - main - slapd stopped.
>  > [19/Aug/2019:13:39:14.956052401 -0500] - INFO -
> ldbm_instance_config_cachememsize_set - force a minimal value 512000
>  > [19/Aug/2019:13:39:14.969061719 -0500] - INFO - check_and_set_import_cache -
> pagesize: 4096, available bytes 7602278400, process usage 40792064
>  > [19/Aug/2019:13:39:14.970107682 -0500] - INFO - check_and_set_import_cache - Import
> allocates 2969640KB import cache.
>  > [19/Aug/2019:13:39:14.971216396 -0500] - INFO - ldbm_back_upgradednformat -
> userRoot: Start upgrade dn format.
>  > [19/Aug/2019:13:39:14.972355840 -0500] - INFO - ldbm_back_upgradednformat - Instance
> userRoot in /var/lib/dirsrv/slapd-xxxxx/db/userRoot is up-to-date
>  > 
>  > 
>  > 
>  > the setup file has this fatal error on setup
>  > [19/08/19:13:41:28] - [Setup] Info Are you ready to set up your servers?
>  > [19/08/19:13:41:30] - [Setup] Info yes
>  > [19/08/19:13:41:30] - [Setup] Info Creating directory server . . .
>  > [19/08/19:13:41:30] - [Setup] Info Could not copy file
> '/etc/dirsrv/config/certmap.conf' to
> '/etc/dirsrv/slapd-xxxxx/certmap.conf'.  Error: No such file or directory
>  > [19/08/19:13:41:30] - [Setup] Fatal Error: Could not create directory server
> instance 'xxxxxxxx'.
>  > [19/08/19:13:41:30] - [Setup] Fatal Exiting . . .
>  > Log file is '/tmp/setupwT17yV.log'
>  > 
>  
>  So the server failed to setup? Can you show me the output of:
>  
>  find /etc/dirsrv
>  
>  
>  
>  
>  > On Mon, Aug 19, 2019 at 7:41 PM William Brown <wbrown(a)suse.de&gt; wrote:
>  > 
>  > 
>  > > On 20 Aug 2019, at 01:54, Chase Miller <chasejmiller(a)gmail.com&gt; wrote:
>  > > 
>  > > Hello, 
>  > > 
>  > > I have a fresh install of Centos 7.
>  > > (this is not my first install of Directory Server, btw)
>  > > 
>  > > Followed this article:
>  > > https://webhostinggeeks.com/howto/setup-389-directory-server-on-centos-7/
>  > > 
>  > > 
>  > > cat setupV6AAJP.log 
>  > > [19/08/19:08:49:28] - [Setup] Info This program will set up the 389 Directory
> and Administration Servers.
>  > > 
>  > > It is recommended that you have "root" privilege to set up the
> software.
>  > > Tips for using this program:
>  > >   - Press "Enter" to choose the default and go to the next screen
>  > >   - Type "Control-B" then "Enter" to go back to the
> previous screen
>  > >   - Type "Control-C" to cancel the setup program
>  > > 
>  > > [19/08/19:08:49:28] - [Setup] Info Would you like to continue with set up?
>  > > [19/08/19:08:49:31] - [Setup] Info yes
>  > > [19/08/19:08:49:31] - [Setup] Info Your system has been scanned for potential
> problems, missing patches,
>  > > etc.  The following output is a report of the items found that need to
>  > > be addressed before running this software in a production
>  > > environment.
>  > > 
>  > > 389 Directory Server system tuning analysis version 14-JULY-2016.
>  > > 
>  > > NOTICE : System is x86_64-unknown-linux3.10.0-957.27.2.el7.x86_64 (2
> processors).
>  > > 
>  > > [19/08/19:08:49:31] - [Setup] Info Would you like to continue?
>  > > [19/08/19:08:49:39] - [Setup] Info yes
>  > > [19/08/19:08:49:39] - [Setup] Info Choose a setup type:
>  > > 
>  > >    1. Express
>  > >        Allows you to quickly set up the servers using the most
>  > >        common options and pre-defined defaults. Useful for quick
>  > >        evaluation of the products.
>  > > 
>  > >    2. Typical
>  > >        Allows you to specify common defaults and options.
>  > > 
>  > >    3. Custom
>  > >        Allows you to specify more advanced options. This is 
>  > >        recommended for experienced server administrators only.
>  > > 
>  > > To accept the default shown in brackets, press the Enter key.
>  > > 
>  > > [19/08/19:08:49:39] - [Setup] Info Choose a setup type
>  > > [19/08/19:08:49:40] - [Setup] Info 2
>  > > [19/08/19:08:49:40] - [Setup] Info Enter the fully qualified domain name of the
> computer
>  > > on which you're setting up server software. Using the form
>  > > <hostname>.<domainname>
>  > > Example: eros.example.com.
>  > > 
>  > > To accept the default shown in brackets, press the Enter key.
>  > > 
>  > > Warning: This step may take a few minutes if your DNS servers
>  > > can not be reached or if DNS is not configured correctly.  If
>  > > you would rather not wait, hit Ctrl-C and run this program again
>  > > with the following command line option to specify the hostname:
>  > > 
>  > >     General.FullMachineName=your.hostname.domain.name
>  > > 
>  > > [19/08/19:08:49:40] - [Setup] Info Computer name
>  > > [19/08/19:08:49:42] - [Setup] Info xxxxx.xxxx.com
>  > > [19/08/19:08:49:42] - [Setup] Info The servers must run as a specific user in a
> specific group.
>  > > It is strongly recommended that this user should have no privileges
>  > > on the computer (i.e. a non-root user).  The setup procedure
>  > > will give this user/group some permissions in specific paths/files
>  > > to perform server-specific operations.
>  > > 
>  > > If you have not yet created a user and group for the servers,
>  > > create this user and group using your native operating
>  > > system utilities.
>  > > 
>  > > [19/08/19:08:49:42] - [Setup] Info System User
>  > > [19/08/19:08:49:48] - [Setup] Info dirsrv
>  > > [19/08/19:08:49:48] - [Setup] Info System Group
>  > > [19/08/19:08:49:49] - [Setup] Info dirsrv
>  > > [19/08/19:08:49:49] - [Setup] Info Server information is stored in the
> configuration directory server.
>  > > This information is used by the console and administration server to
>  > > configure and manage your servers.  If you have already set up a
>  > > configuration directory server, you should register any servers you
>  > > set up or create with the configuration server.  To do so, the
>  > > following information about the configuration server is required: the
>  > > fully qualified host name of the form
>  > > <hostname>.<domainname>(e.g. hostname.example.com), the port
> number
>  > > (default 389), the suffix, the DN and password of a user having
>  > > permission to write the configuration information, usually the
>  > > configuration directory administrator, and if you are using security
>  > > (TLS/SSL).  If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
>  > > number (default 636) instead of the regular LDAP port number, and
>  > > provide the CA certificate (in PEM/ASCII format).
>  > > 
>  > > If you do not yet have a configuration directory server, enter 'No' to
>  > > be prompted to set up one.
>  > > 
>  > > [19/08/19:08:49:49] - [Setup] Info Do you want to register this software with
> an existing
>  > > configuration directory server?
>  > > [19/08/19:08:49:52] - [Setup] Info no
>  > > [19/08/19:08:49:52] - [Setup] Info Please enter the administrator ID for the
> configuration directory
>  > > server.  This is the ID typically used to log in to the console.  You
>  > > will also be prompted for the password.
>  > > 
>  > > [19/08/19:08:49:52] - [Setup] Info Configuration directory server
>  > > administrator ID
>  > > [19/08/19:08:49:57] - [Setup] Info admin
>  > > [19/08/19:08:49:57] - [Setup] Info Password
>  > > [19/08/19:08:50:06] - [Setup] Info Password (confirm)
>  > > [19/08/19:08:50:08] - [Setup] Info The information stored in the configuration
> directory server can be
>  > > separated into different Administration Domains.  If you are managing
>  > > multiple software releases at the same time, or managing information
>  > > about multiple domains, you may use the Administration Domain to keep
>  > > them separate.
>  > > 
>  > > If you are not using administrative domains, press Enter to select the
>  > > default.  Otherwise, enter some descriptive, unique name for the
>  > > administration domain, such as the name of the organization
>  > > responsible for managing the domain.
>  > > 
>  > > [19/08/19:08:50:08] - [Setup] Info Administration Domain
>  > > [19/08/19:08:50:10] - [Setup] Info xxxx.com
>  > > [19/08/19:08:50:10] - [Setup] Info The standard directory server network port
> number is 389.  However, if
>  > > you are not logged as the superuser, or port 389 is in use, the
>  > > default value will be a random unused port number greater than 1024.
>  > > If you want to use port 389, make sure that you are logged in as the
>  > > superuser, that port 389 is not in use.
>  > > 
>  > > [19/08/19:08:50:10] - [Setup] Info Directory server network port
>  > > [19/08/19:08:50:12] - [Setup] Info 389
>  > > [19/08/19:08:50:12] - [Setup] Info Each instance of a directory server requires
> a unique identifier.
>  > > This identifier is used to name the various
>  > > instance specific files and directories in the file system,
>  > > as well as for other uses as a server instance identifier.
>  > > 
>  > > [19/08/19:08:50:12] - [Setup] Info Directory server identifier
>  > > [19/08/19:08:50:13] - [Setup] Info xxxxxxx
>  > > [19/08/19:08:50:13] - [Setup] Info The suffix is the root of your directory
> tree.  The suffix must be a valid DN.
>  > > It is recommended that you use the dc=domaincomponent suffix convention.
>  > > For example, if your domain is example.com,
>  > > you should use dc=example,dc=com for your suffix.
>  > > Setup will create this initial suffix for you,
>  > > but you may have more than one suffix.
>  > > Use the directory server utilities to create additional suffixes.
>  > > 
>  > > [19/08/19:08:50:13] - [Setup] Info Suffix
>  > > [19/08/19:08:50:14] - [Setup] Info dc=xxxx, dc=com
>  > > [19/08/19:08:50:14] - [Setup] Info Certain directory server operations require
> an administrative user.
>  > > This user is referred to as the Directory Manager and typically has a
>  > > bind Distinguished Name (DN) of cn=Directory Manager.
>  > > You will also be prompted for the password for this user.  The password must
>  > > be at least 8 characters long, and contain no spaces.
>  > > Press Control-B or type the word "back", then Enter to back up and
> start over.
>  > > 
>  > > [19/08/19:08:50:14] - [Setup] Info Directory Manager DN
>  > > [19/08/19:08:50:16] - [Setup] Info cn=Directory Manager
>  > > [19/08/19:08:50:16] - [Setup] Info Password
>  > > [19/08/19:08:50:19] - [Setup] Info Password (confirm)
>  > > [19/08/19:08:50:21] - [Setup] Info The Administration Server is separate from
> any of your web or application
>  > > servers since it listens to a different port and access to it is
>  > > restricted.
>  > > 
>  > > Pick a port number between 1024 and 65535 to run your Administration
>  > > Server on. You should NOT use a port number which you plan to
>  > > run a web or application server on, rather, select a number which you
>  > > will remember and which will not be used for anything else.
>  > > 
>  > > [19/08/19:08:50:21] - [Setup] Info Administration port
>  > > [19/08/19:08:50:22] - [Setup] Info 9830
>  > > [19/08/19:08:50:22] - [Setup] Info The interactive phase is complete.  The
> script will now set up your
>  > > servers.  Enter No or go Back if you want to change something.
>  > > 
>  > > [19/08/19:08:50:22] - [Setup] Info Are you ready to set up your servers?
>  > > [19/08/19:08:50:24] - [Setup] Info yes
>  > > [19/08/19:08:50:24] - [Setup] Info Creating directory server . . .
>  > > [19/08/19:08:50:30] - [Setup] Info Your new DS instance 'xxxxx' was
> successfully created.
>  > > [19/08/19:08:50:30] - [Setup] Info Creating the configuration directory server
> . . .
>  > > [19/08/19:08:50:33] - [Setup] Fatal Error: failed to open an LDAP connection to
> host 'xxxxxx.xxxx.com' port '389' as user 'cn=Directory Manager'. 
> Error: unknown.
>  > > [19/08/19:08:50:33] - [Setup] Fatal Failed to create the configuration
> directory server
>  > > [19/08/19:08:50:33] - [Setup] Fatal Exiting . . .
>  > > Log file is '/tmp/setupV6AAJP.log'
>  > 
>  > Can you show the output of `ss -tlnp` from the server? Maybe also `systemctl status
> dirsrv@xxxx` and the content of /var/log/dirsrv/slapd-xxxxx/errors
>  > 
>  > I also recommend you look at the Red Hat Directory Server documentation for version
> 10 - that aligns to Centos7 and the server packages there, and is maintained by Marc and
> the team here on this list. It's an excellent place for help.
>  > 
>  > Hope that helps,
>  > 
>  > —
>  > Sincerely,
>  > 
>  > William Brown
>  > 
>  > Senior Software Engineer, 389 Directory Server
>  > SUSE Labs
>  > _______________________________________________
>  > 389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
>  > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>  > _______________________________________________
>  > 389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
>  > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>  
>  —
>  Sincerely,
>  
>  William Brown
>  
>  Senior Software Engineer, 389 Directory Server
>  SUSE Labs
>  _______________________________________________
>  389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]...
>  _______________________________________________
>  389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]... 
—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs