https://pagure.io/389-ds-base/pull-request/50724

@mreynolds we should check that /etc/resolf.conf has the appropriate rights +r. Else (e.g. 600) a replication agreement may fail to connect to the remote host.

@mreynolds we should check that /etc/resolf.conf has the appropriate rights +r. Else (e.g. 600) a replication agreement may fail to connect to the remote host.

You mean /etc/resolv.conf ? Is this a problem you've seen before? I have not heard of this being an issue, that's why I'm asking

@mreynolds It comes from a user case and the diagnostic was difficult to establish.
replication looked the perfect usual suspect. RA reported a mysterious 'Can't contact LDAP server' while the consumer was running.

Commit a370f8d relates to this ticket

2a64658..02c913e 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

d513014..728b679 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

Commit f439447 relates to this ticket

Fix typo:

Commit f439447 relates to this ticket

02c913e..53ae896 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

728b679..67b12ad 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

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/3756

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.