#51197 389 DS fails to restart when rotating log files
Closed: wontfix 3 years ago by spichugi. Opened 3 years ago by billf8004.

Issue Description

dirsrv process fails to restart when rotating logs with the following error(s):
Jun 30 00:00:00 patchqaldap02s.eng.c4e.ops ns-slapd[31440]: Failed to open errors log file /var/log/dirsrv/slapd-patchqaldap02s/errors: error 13 (Permission denied); Exiting...
Jun 30 00:00:00 patchqaldap02s.eng.c4e.ops ns-slapd[31440]: Failed to reopen errors log file, Netscape Portable Runtime error -5966 (Access Denied.)

dirsrv user and group has ownership with 600 permissions on /var/log/dirsrv and all files and directories.

The process cannot be started without removing errors.rotationinfo

Package Version and Platform

RHEL 7 - 3.10.0-1062.1.1.el7.x86_64
389-ds-base 1.3.10.1-14.el7_8

Steps to reproduce

Automated process

Actual results

Process fails to restart

Expected results

Process restarts successfully


@billf8004 can you verify how the log was rotated? Did the server rotate it as part of the rotation policy, or was it somehow manually rotated outside of the server?

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

3 years ago

@billf8004 can you verify how the log was rotated? Did the server rotate it as part of the rotation policy, or was it somehow manually rotated outside of the server?

This is the OEM rotation policy. These were all new builds without making any changes to the rotation policy and it happens across the board. I went so far as giving recursive ownership to dirsrv:dirsrv with 777 permissions and it didn't resolve the issue.

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/4250

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata