On 1/23/20 1:17 PM, Alberto Viana wrote:
Mark,
I using python3-lib389-1.4.3.1-20200116gita08202a5b.el8.noarch
python3.6
And still got the same error:
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/lib/python3.6/site-packages/lib389/cli_ctl/health.py",
line 88, in health_check_run
lo_inst = lo(inst)
File "/usr/lib/python3.6/site-packages/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'
Should I file a ticket or it already fixed in?
I have never seen this error. dsctl
works fine on RHEL 8 for me. Well I
did fix an issue around the certificate expiration health check and
python 36 vs 37, but other than that it works. Like I said before it
looks like your version of lib389 is wrong as this is an error in a
fundamental part of the CLI (looking up the instance). This code has
not changed in a long time which is why I think you have a problem with
how you are trying to deploy the server. How are you building the rpms
again?
Thanks
On Thu, Jan 16, 2020 at 4:27 PM Alberto Viana <albertocrj(a)gmail.com
<mailto:albertocrj@gmail.com>> wrote:
Mark,
Thanks, I'm now building the packages as well.
Alberto Viana
On Mon, Jan 13, 2020 at 4:58 PM Mark Reynolds
<mreynolds(a)redhat.com <mailto:mreynolds@redhat.com>> wrote:
On 1/13/20 2:56 PM, Alberto Viana wrote:
> Mark,
>
> Just to let you know, I'm cloning pagure repo and
> in /src/lib389 the VERSION file points me to this version:
>
> ~# cat VERSION
> 1.0.4
That's obsolete since we made it a subpackage of 389-ds-base...
>
> Thanks
>
> Alberto Viana
>
> On Mon, Jan 13, 2020 at 4:48 PM Alberto Viana
> <albertocrj(a)gmail.com <mailto:albertocrj@gmail.com>> wrote:
>
> Mark,
>
> I'm installing it from source, to install lib389 I run:
> make lib389-install
>
> Am I missing something?
>
> Thanks
>
> Alberto Viana
>
> On Mon, Jan 13, 2020 at 4:36 PM Mark Reynolds
> <mreynolds(a)redhat.com <mailto:mreynolds@redhat.com>> wrote:
>
>
> On 1/13/20 2:24 PM, Alberto Viana wrote:
>> 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:
>
> This is the wrong python-lib389 version. It would be
> something like 1.4.2.4.x. It would (needs to) match
> the 389-ds-base package version.
>
> What does "rpm -qa | grep lib389" show?
>
> Thanks,
> Mark
>
>> 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
>> <mreynolds(a)redhat.com <mailto:mreynolds@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(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org>
>>> To unsubscribe send an email
to389-users-leave(a)lists.fedoraproject.org
<mailto:389-users-leave@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.fe...
>>
>> --
>>
>> 389 Directory Server Development Team
>>
> --
>
> 389 Directory Server Development Team
>
--
389 Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)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.fedoraproje...
--
389 Directory Server Development Team