Sunday, December 10, 2023

[389-users] Re: 389-ds-base name log pipe problems

On Thu, Dec 7, 2023 at 11:25 AM Nyquist <> wrote:

1. Stop directory server and remove access log file.
2. Run Python create access.pipe (pipe)
3. Change directory server settings
nsslapd-accesslog-maxlogsperdir: 1
nsslapd-accesslog-logexpirationtime: -1
nsslapd-accesslog-logrotationtime: -1
nsslapd-accesslog: /var/log/dirsrv/slapd-localhost/access.pipe
nsslapd-accesslog-logbuffering: off
4. Run directory server
=> Check normal execution, and are operating normally.

The problem arises after this. This server has consumed all connections. A forced shutdown of the external system returned the connection, and we expected it to work normally. However, port 389 health check failed intermittently. Joining and removing from the L4 switch is repeated. Could this be caused by my logging settings to pipe?
Or should I think it's a problem with the Linux file system?

Judging by the version, it's a system with systemd, where logpipe was not working properly and the server would refuse to start.
Some time ago I investigated issues with logpipe and systemd and wrote these instructions to make it work: (you can skip dsconf part as you already did have this configuration in cn=config).
Could you please try this approach?

389-users mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:


No comments:

Post a Comment