What platform are you on?  What version of 389-ds-base?  Please provide more information when asking questions on the mailing list otherwise most people will not respond to your questions - just an FYI. 

Since I am somewhat familiar with the issue I will provide more background information for you...

[1] This is on Oracle Linux with 389-ds-base-1.3.8

[2] The problem happened after applying OS updates

As I had previously stated to your coworker, this seems related to systemd.  Was systemd updated as part of the OS update that broke 389?  If it was then you might need a fix that is not present in 389-ds-base-1.3.8.  Note - this fix does not apply to RHEL 7.x, and it would break FreeIPA if we did add it - which is why it was not included in 389-ds-base-1.3.8, and only in 389-ds-base-1.4.x

Options:

[1] Backout OS updates that broke 389 DS

[2] You can build your own hotfix to see if it solves the problem:

https://www.port389.org/docs/389ds/contributing.html#building-the-project

Here are the exact steps to build the hotfix

# git clone https://pagure.io/389-ds-base.git

# cd 389-ds-base

# git checkout 389-ds-base-1.3.8

# git cherry-pick 1088afbb3

---> You probably need to install a lot of packages to do the build.  Start with this, but on Oracle LInux there could be more you need to install:

# yum install libtool libtalloc* libtevent* libevent* systemd-devel icu libicu* net-snmp-devel pcre* pam* libdb-devel mod_nss gdb gcc-c++ perl-Archive-Tar  rpm-build git gdb rsync libatomic gperftools doxygen nspr* nss-devel bzip2-devel cracklib-devel libtool automake autoconf krb5-devel npm libcmocka-devel

# make -f rpm.mk rpms

# cd dist/rpms

HTH,

Mark

When attempting to start 389 I get the following error.

 

[root@ openldap]# systemctl status dirsrv@slapd.service

● dirsrv@slapd.service - 389 Directory Server slapd.

   Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled)

   Active: failed (Result: resources)

 

Jul 10 09:19:21local systemd[1]: Unit dirsrv@slapd.service entered failed state.

Jul 10 09:19:21 local systemd[1]: dirsrv@slapd.service failed.

Jul 10 09:33:32 local systemd[1]: Failed to load environment files: No such file or directory

Jul 10 09:33:32 local systemd[1]: dirsrv@slapd.service failed to run 'start-pre' task: No such file or directory

Jul 10 09:33:32 local systemd[1]: Failed to start 389 Directory Server slapd..

Jul 10 09:33:32 local systemd[1]: dirsrv@slapd.service failed.

Jul 10 09:39:47 local systemd[1]: Failed to load environment files: No such file or directory

Jul 10 09:39:47 local systemd[1]: dirsrv@slapd.service failed to run 'start-pre' task: No such file or directory

Jul 10 09:39:47 loccal systemd[1]: Failed to start 389 Directory Server slapd..

Jul 10 09:39:47 local systemd[1]: dirsrv@slapd.service failed.

 

Any ideas on the reason?

 

Thanks,

 

 

Harlan Whitley

Unix System Administration

 

_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@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/389-users@lists.fedoraproject.org

-- 

389 Directory Server Development Team