Mark,
Here's:
INFO: Checking DSEldif ...
DEBUG: [Errno 2] No such file or directory:
'/etc/dirsrv/slapd-{instance_name}/dse.ldif'
Traceback (most recent call last):
File "/usr/sbin/dsctl", line 134, in <module>
result = args.func(inst, log, args)
File
"/usr/local/lib/python3.6/site-packages/lib389-1.4.0.1-py3.6.egg/lib389/cli_ctl/health.py",
line 88, in health_check_run
lo_inst = lo(inst)
File
"/usr/local/lib/python3.6/site-packages/lib389-1.4.0.1-py3.6.egg/lib389/dseldif.py",
line 49, in __init__
with open(self.path, 'r') as file_dse:
FileNotFoundError: [Errno 2] No such file or directory:
'/etc/dirsrv/slapd-{instance_name}/dse.ldif'
ERROR: Error: [Errno 2] No such file or directory:
'/etc/dirsrv/slapd-{instance_name}/dse.ldif'
Thanks.
Alberto Viana
On Mon, Jan 13, 2020 at 4:19 PM Mark Reynolds <mreyno...@redhat.com> wrote:
>
> On 1/13/20 2:07 PM, Alberto Viana wrote:
>
> Hi Guys,
>
> In 389 version 1.4.2.4 healthcheck works fine:
>
> ~# dsconf RNP healthcheck
> Enter password for cn=Directory Manager on ldaps://localhost:
> Beginning lint report, this could take a while ...
> Checking Backends ...
> Checking Config ...
> Checking Encryption ...
> Checking ReferentialIntegrityPlugin ...
> Healthcheck complete!
>
> And seems that function was moved to dsctl
> but in 1.4.2.5 I got this error:
>
> ~# dsctl RNP healthcheck
> Beginning lint report, this could take a while ...
> Checking Backends ...
> Checking Config ...
> Checking Encryption ...
> Checking FSChecks ...
> Checking ReferentialIntegrityPlugin ...
> Checking MonitorDiskSpace ...
> Checking Replica ...
> Checking Changelog5 ...
> Checking DSEldif ...
> Error: [Errno 2] No such file or directory:
> '/etc/dirsrv/slapd-{instance_name}/dse.ldif'
>
> Is that a bug?
>
> Probably, but not one I've seen. Maybe 1.4.2 is missing a patch that is
> in Master branch? I'll be doing 1.4.2.6 in the next day or two. So I will
> double check nothing is missing. But for now can you run it again but
> with "-v" option and share the failing exception: # dsctl -v RNP
> healthcheck
>
> Thanks,
>
> Mark
>
>
> Thanks
>
> Alberto Viana
>
>
>
> _______________________________________________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@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
>
>
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@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
