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 dsctlbut 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@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
-- 389 Directory Server Development Team
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx