[389-users] healthcheck problems

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

[389-users] Re: Attribute encryption issue

Mark, This is happens to me too, I think that is very easy to reproduce that. Configure 389 to setup a self-signed certificate and enable TLS, after that we import a new CA (we use a specific CA) and server-cert based on this new CA. if I delete the self-signed cert (generated during the

[389-users] Re: healthcheck problems

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 wrote: > > On 1/13/20 2:24 PM, Alberto Viana wrote: > > Mark, > > Here's: > > INFO: Checking DSEldif ... > DEBUG:

[389-users] Re: healthcheck problems

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 Thanks Alberto Viana On Mon, Jan 13, 2020 at 4:48 PM Alberto Viana wrote: > Mark, > > I'm installing it from source, to install lib389 I run: > make

[389-users] Re: healthcheck problems

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

[389-users] Re: healthcheck problems

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     result = args.func(inst, log, args)  

[389-users] Re: healthcheck problems

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

[389-users] Re: healthcheck problems

On 1/13/20 2:48 PM, Alberto Viana wrote: Mark, I'm installing it from source, to install lib389 I run: make lib389-install I'm not sure that works :-/  I never tried it.  I always build the rpms when working with lib389:     # make -f rpm.mk rpms     # cd dist/rpms You can always

[389-users] Announcing 389 Directory Server 1.4.3

389 Directory Server 1.4.3.1 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.3.1 Fedora packages are available on rawhide. https://koji.fedoraproject.org/koji/taskinfo?taskID=40493136 - Rawhide

[389-users] Re: healthcheck problems

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 result = args.func(inst, log, args) File

[389-users] Announcing 389 Directory Server 1.4.2.6

389 Directory Server 1.4.2.6 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.2.6 Fedora packages are available on Fedora 31. https://koji.fedoraproject.org/koji/taskinfo?taskID=40494075 - Fedora 31

[389-users] Announcing 389 Directory Server 1.4.1.13

389 Directory Server 1.4.1.13 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.1.13 Fedora packages are available on Fedora 30. https://koji.fedoraproject.org/koji/taskinfo?taskID=40494821 - Fedora 

[389-users] Re: Attribute encryption issue

This has been a known issue for some time. https://pagure.io/389-ds-base/issue/49525 > On 13 Jan 2020, at 22:37, Alberto Viana wrote: > > Mark, > > This is happens to me too, I think that is very easy to reproduce that. > Configure 389 to setup a self-signed certificate and enable TLS,