Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
After instance is created, I see the following error in journalctl:
Nov 27 22:48:33 server-rhel8.example.com systemd[1]: /usr/lib/systemd/system/dirsrv@.service:40: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Version-Release number of selected component (if applicable):
389-ds-base-1.4.0.19-2
How reproducible:
always
Steps to Reproduce:
1. dscreate
2. journalctl | grep deprecated
3.
Actual results:
Deprecation message is found in the logs
Expected results:
No deprecation message
Additional info:
https://github.com/systemd/systemd/commit/41b283d0f1f4abd85d0bbeeb7f71bb30f87cfab9
Build tested: 389-ds-base-1.4.1.3-3.module+el8.1.0+3533+f8225121.x86_64
[root@server-rhel8 ds]# journalctl -u dirsrv _COMM=systemd
-- Logs begin at Tue 2019-07-02 07:33:44 UTC, end at Tue 2019-07-02 07:35:31 UTC. --
Jul 02 07:35:23 server-rhel8.example.com systemd[1]: Starting 389 Directory Server localhost....
Jul 02 07:35:25 server-rhel8.example.com systemd[1]: Started 389 Directory Server localhost..
Jul 02 07:35:25 server-rhel8.example.com systemd[1]: Stopping 389 Directory Server localhost....
Jul 02 07:35:28 server-rhel8.example.com systemd[1]: Stopped 389 Directory Server localhost..
Jul 02 07:35:29 server-rhel8.example.com systemd[1]: Starting 389 Directory Server localhost....
Jul 02 07:35:31 server-rhel8.example.com systemd[1]: Started 389 Directory Server localhost..
Message is no longer present in the logs.
And instead of include, a drop-in file is used to configure service parameters:
[root@server-rhel8 ds]# systemctl show dirsrv@localhost -p LimitNOFILE
LimitNOFILE=1048576
[root@server-rhel8 ds]# vim /usr/lib/systemd/system/dirsrv@.service.d/custom.conf
[root@server-rhel8 ds]# systemctl daemon-reload
[root@server-rhel8 ds]# systemctl show dirsrv@localhost -p LimitNOFILE
LimitNOFILE=4096
Marking as VERIFIED.
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/RHSA-2019:3401