[389-users] Re: 389 Windows Console

2016-01-05 Thread Phil Daws
Hello Noriko, Same problem unfortunately :( Thanks, Phil - On 4 Jan, 2016, at 20:54, Noriko Hosoi wrote: > Hello Phil, > We are working on the issue, but not sure what the root cause is yet. > If you could try the new installer I have just uploaded, it would be a > big help for us. (

[389-users] Re: CentOS 7: unable to create AdmldapInfo

2016-01-05 Thread Rich Megginson
On 01/04/2016 08:50 PM, David Barr wrote: On Jan 4, 2016, at 07:53, Rich Megginson wrote: We'll need to know what platform/version you are upgrading from, because there is not supposed to be a missing log directory, and the SELinux labels are already supposed to be provided. In order for us

[389-users] Re: CentOS 7: unable to create AdmldapInfo

2016-01-05 Thread Noriko Hosoi
> I’m experimenting with upgrading 389DS to 1.3.4.0-21.el7_2 on CentOS 7 (I neglected to note what version I had previously). Could you also tell us the version of the 389-admin and adminutil? rpm -q 389-admin 389-adminutil There is a known issue that anonymous binds are necessary when the admi

[389-users] memberOf + error65

2016-01-05 Thread ghiureai
Hi LIst, we need to fix Error (65) we are seeing with memberOf pluging in last DS 1.3.4. with already existing groups entries, after some research I found the new param: |memberofAutoAddOC needs to be added to membeOf plugin cfg , would this be sufficient to maintain the exiting DS ent

[389-users] Re: CentOS 7: unable to create AdmldapInfo

2016-01-05 Thread David Barr
> On Jan 5, 2016, at 10:57, Noriko Hosoi wrote: > > Could you also tell us the version of the 389-admin and adminutil? > rpm -q 389-admin 389-adminutil Installed Packages 389-admin.x86_64 1.1.38-1.el7@epel 389-adminutil.x86_64 1.1.21-2.el7@epel 389-ds-base.x86_64