On 01/28/2019 09:20 AM, Mihai Carabas wrote:
On Mon, Jan 28, 2019 at 10:04 AM Ludwig wrote:
On 01/24/2019 10:34 PM, William Brown wrote:
On 25 Jan 2019, at 10:08, Mark Reynolds wrote:
On 1/24/19 3:35 PM, Mihai Carabas wrote:
On Thu, Jan 24, 2019 at 10:17 PM Mark Reynolds wrote:
On
On Mon, Jan 28, 2019 at 10:04 AM Ludwig wrote:
>
>
>
> On 01/24/2019 10:34 PM, William Brown wrote:
> >
> >> On 25 Jan 2019, at 10:08, Mark Reynolds wrote:
> >>
> >>
> >> On 1/24/19 3:35 PM, Mihai Carabas wrote:
> >>> On Thu, Jan 24, 2019 at 10:17 PM Mark Reynolds
> >>> wrote:
> On
On 01/24/2019 10:34 PM, William Brown wrote:
On 25 Jan 2019, at 10:08, Mark Reynolds wrote:
On 1/24/19 3:35 PM, Mihai Carabas wrote:
On Thu, Jan 24, 2019 at 10:17 PM Mark Reynolds wrote:
On 1/24/19 1:54 PM, Mihai Carabas wrote:
Hello,
[root@ldap ~]# dsctl slapd-ldap db2ldif
On Thu, Jan 24, 2019 at 11:08 PM Mark Reynolds wrote:
>
>
> On 1/24/19 3:35 PM, Mihai Carabas wrote:
> > On Thu, Jan 24, 2019 at 10:17 PM Mark Reynolds wrote:
> >>
> >> On 1/24/19 1:54 PM, Mihai Carabas wrote:
> >>
> >> Hello,
> >>
> >> [root@ldap ~]# dsctl slapd-ldap db2ldif --replication
> On 25 Jan 2019, at 10:08, Mark Reynolds wrote:
>
>
> On 1/24/19 3:35 PM, Mihai Carabas wrote:
>> On Thu, Jan 24, 2019 at 10:17 PM Mark Reynolds wrote:
>>>
>>> On 1/24/19 1:54 PM, Mihai Carabas wrote:
>>>
>>> Hello,
>>>
>>> [root@ldap ~]# dsctl slapd-ldap db2ldif --replication cursdb
On 1/24/19 3:35 PM, Mihai Carabas wrote:
On Thu, Jan 24, 2019 at 10:17 PM Mark Reynolds wrote:
On 1/24/19 1:54 PM, Mihai Carabas wrote:
Hello,
[root@ldap ~]# dsctl slapd-ldap db2ldif --replication cursdb cursdb.ldif
cursdb.ldif doesn't seem to contain any replication related info. What
On Thu, Jan 24, 2019 at 10:17 PM Mark Reynolds wrote:
>
>
> On 1/24/19 1:54 PM, Mihai Carabas wrote:
>
> Hello,
>
> [root@ldap ~]# dsctl slapd-ldap db2ldif --replication cursdb cursdb.ldif
>
> cursdb.ldif doesn't seem to contain any replication related info. What
> should contain related to
Mihai Carabas
> On 24 Jan 2019, at 22:15, Mark Reynolds wrote:
>
>
>> On 1/24/19 1:18 PM, Mihai Carabas wrote:
>> Hello,
>>
>> In order to help you to help me ;), I've re-run db2index and collected
>> the attached stacktraces.
> Did you see really high CPU?
>
Not at all. Almost 0. It seems
On 1/24/19 1:54 PM, Mihai Carabas wrote:
Hello,
[root@ldap ~]# dsctl slapd-ldap db2ldif --replication cursdb cursdb.ldif
cursdb.ldif doesn't seem to contain any replication related info. What
should contain related to replication?
You should at least see an entry with "dn:
On 1/24/19 1:18 PM, Mihai Carabas wrote:
Hello,
In order to help you to help me ;), I've re-run db2index and collected
the attached stacktraces.
Did you see really high CPU?
Thank you,
Mihai
On Thu, Jan 24, 2019 at 5:52 PM Mark Reynolds wrote:
On 1/24/19 10:24 AM, Mihai Carabas wrote:
Hello,
[root@ldap ~]# dsctl slapd-ldap db2ldif --replication cursdb cursdb.ldif
cursdb.ldif doesn't seem to contain any replication related info. What
should contain related to replication?
Thank you,
Mihai
On Thu, Jan 24, 2019 at 5:53 PM Mark Reynolds wrote:
>
>
> On 1/24/19 10:26 AM, Mihai
Hello,
In order to help you to help me ;), I've re-run db2index and collected
the attached stacktraces.
Thank you,
Mihai
On Thu, Jan 24, 2019 at 5:52 PM Mark Reynolds wrote:
>
>
> On 1/24/19 10:24 AM, Mihai Carabas wrote:
> > Hello Mark,
> >
> > On Thu, Jan 24, 2019 at 4:35 PM Mark Reynolds
On 1/24/19 10:26 AM, Mihai Carabas wrote:
Also I used db2index on the stopped Directory Server. Should I have
used db2index.pl on the running one?
IMO, it's best to stop to the server when doing these types of operations.
Mark
Thanks,
Mihai
On Thu, Jan 24, 2019 at 5:24 PM Mihai Carabas
On 1/24/19 10:24 AM, Mihai Carabas wrote:
Hello Mark,
On Thu, Jan 24, 2019 at 4:35 PM Mark Reynolds wrote:
On 1/24/19 8:37 AM, Mihai Carabas wrote:
On Thu, Jan 24, 2019 at 12:52 AM William Brown wrote:
On 24 Jan 2019, at 00:50, Mihai Carabas wrote:
=profesor
42815 42818
Also I used db2index on the stopped Directory Server. Should I have
used db2index.pl on the running one?
Thanks,
Mihai
On Thu, Jan 24, 2019 at 5:24 PM Mihai Carabas wrote:
>
> Hello Mark,
>
> On Thu, Jan 24, 2019 at 4:35 PM Mark Reynolds wrote:
> >
> >
> > On 1/24/19 8:37 AM, Mihai Carabas
Hello Mark,
On Thu, Jan 24, 2019 at 4:35 PM Mark Reynolds wrote:
>
>
> On 1/24/19 8:37 AM, Mihai Carabas wrote:
> > On Thu, Jan 24, 2019 at 12:52 AM William Brown wrote:
> >>
> >>
> >>> On 24 Jan 2019, at 00:50, Mihai Carabas wrote:
> >>>
> >>> =profesor
> >>> 42815 42818 42821 42824
On 1/24/19 8:37 AM, Mihai Carabas wrote:
On Thu, Jan 24, 2019 at 12:52 AM William Brown wrote:
On 24 Jan 2019, at 00:50, Mihai Carabas wrote:
=profesor
42815 42818 42821 42824 42827 42830 42833 42836 42839 42842
42845 42848 43445 43450 45720 52253
=profesori
7 68 3232
On Thu, Jan 24, 2019 at 12:52 AM William Brown wrote:
>
>
>
> > On 24 Jan 2019, at 00:50, Mihai Carabas wrote:
> >
> > =profesor
> >42815 42818 42821 42824 42827 42830 42833 42836 42839 42842
> > 42845 42848 43445 43450 45720 52253
> > =profesori
> >7 68 3232 3648 5457 6259 6268
Hello William,
[root@ldap cursdb]# pwd
/var/lib/dirsrv/slapd-ldap/db/cursdb
[root@ldap cursdb]# dbscan -r -f ou.db
+
2 3 4 7 26 27 67 68 70 71 75 77 79 305 1751 1752 1857 1858
1861 1862 1954 1998 2143 2144 2220 2434 2994 3054 3055 3093 3206 3225
3226 3229 3232 3245 3262 3391 3482 3499
> On 23 Jan 2019, at 20:14, Mihai Carabas wrote:
>
> I've tried playing with the filters on the ou=DPPD which has issues:
> # extended LDIF
> #
> # LDAPv3
> # base with scope oneLevel
> # filter: ou=Profeso
> # requesting: ALL
> #
>
> # search result
> search: 2
> result: 0 Success
>
> #
> On 23 Jan 2019, at 02:01, Mihai Carabas wrote:
>
> Helllo,
>
> On Tue, Jan 22, 2019 at 11:45 AM Ludwig wrote:
>>
>> The issue you are reporting does match exactly the issue in #49443, but
>> this was fixed and the fix is in current master. Also I cannot reproduce
>> it in current master
Helllo,
On Tue, Jan 22, 2019 at 11:45 AM Ludwig wrote:
>
> The issue you are reporting does match exactly the issue in #49443, but
> this was fixed and the fix is in current master. Also I cannot reproduce
> it in current master and not with 1.4.20 -
>
> So this is a bit weird. Can you share a
The issue you are reporting does match exactly the issue in #49443, but
this was fixed and the fix is in current master. Also I cannot reproduce
it in current master and not with 1.4.20 -
So this is a bit weird. Can you share a bit more of your data, eg
provide all entries below ou=DPPD dn
More verbose:
# extended LDIF
#
# LDAPv3
# base with scope oneLevel
# filter: ou=Profesori
# requesting: dn
#
# Profesori, DPPD, People, curs.pub.ro
dn: ou=Profesori,ou=DPPD,ou=People,dc=curs,dc=pub,dc=ro
# Asistenti-Man, DPPD, People, curs.pub.ro
dn:
Mihai Carabas
> On 22 Jan 2019, at 00:06, William Brown wrote:
>
>
>
>> On 22 Jan 2019, at 09:15, Mihai Carabas wrote:
>>
>> Hello,
>>
>> Recently I've upgraded 389ds to 389ds-1.4.0.20 on a fc29. It seems
>> that the bug https://pagure.io/389-ds-base/issue/49617 and also
>>
> On 22 Jan 2019, at 09:15, Mihai Carabas wrote:
>
> Hello,
>
> Recently I've upgraded 389ds to 389ds-1.4.0.20 on a fc29. It seems
> that the bug https://pagure.io/389-ds-base/issue/49617 and also
> https://pagure.io/389-ds-base/issue/49443
>
> [root@ldap ~]# rpm -qa | grep 389
>
26 matches
Mail list logo
