[389-users] Re: Problem with userRoot cache

2019-01-16 Thread William Brown
> provisions of the federal Gramm-Leach-Bliley Act. If you have received this >> facsimile or electronic message in error, please immediately notify us by >> telephone and return or destroy the original message to assure that it is >> not read, copied, or dis

[389-users] Re: Problem with userRoot cache (last one)

2019-01-16 Thread Paul Whitney
erver project.; Paul Whitney; William Brown Subject: Re: [389-users] Re: Problem with userRoot cache (last one) On 1/16/19 12:05 PM, Mark Reynolds wrote: On 1/16/19 12:02 PM, Mark Reynolds wrote: Hi Paul, Okay I think I found the bug you are running into: https://bugzilla.redhat.com/show_

[389-users] Re: Problem with userRoot cache (last one)

2019-01-16 Thread Mark Reynolds
project.; Paul Whitney; William Brown *Subject:* Re: [389-users] Re: Problem with userRoot cache (last one) On 1/16/19 12:05 PM, Mark Reynolds wrote: On 1/16/19 12:02 PM, Mark Reynolds wrote: Hi Paul, Okay I think I found the bug you are running into: https://bugzilla.redhat.com/show_bu

[389-users] Re: Problem with userRoot cache (last one)

2019-01-16 Thread Paul Whitney
list for the 389 Directory server project.; Paul Whitney; William Brown Subject: Re: [389-users] Re: Problem with userRoot cache (last one) On 1/16/19 12:05 PM, Mark Reynolds wrote: On 1/16/19 12:02 PM, Mark Reynolds wrote: Hi Paul, Okay I think I found the bug you are running into: https://bug

[389-users] Re: Problem with userRoot cache (last one)

2019-01-16 Thread Mark Reynolds
ibuted by others. *From:* William Brown *Sent:* Tuesday, January 15, 2019 7:22:18 PM *To:* 389-users@lists.fedoraproject.org *Cc:* Paul Whitney *Subject:* Re: [389-users] Problem with userRoot cache > On 16 Jan 2019, at 06:49, Mark Reynolds wrote: &g

[389-users] Re: Problem with userRoot cache

2019-01-16 Thread Mark Reynolds
ibuted by others. *From:* William Brown *Sent:* Tuesday, January 15, 2019 7:22:18 PM *To:* 389-users@lists.fedoraproject.org *Cc:* Paul Whitney *Subject:* Re: [389-users] Problem with userRoot cache > On 16 Jan 2019, at 06:49, Mark Reynolds wrot

[389-users] Re: Problem with userRoot cache

2019-01-16 Thread Mark Reynolds
ey *Subject:* Re: [389-users] Problem with userRoot cache > On 16 Jan 2019, at 06:49, Mark Reynolds wrote: > > What version were you previously on? > > Sounds like an issue with autocache sizing.  The errors log might give more info about why its being reset. > > Also check if

[389-users] Re: Problem with userRoot cache

2019-01-16 Thread Paul Whitney
server project.; Paul Whitney; William Brown Subject: Re: [389-users] Re: Problem with userRoot cache Hey Paul, On 1/16/19 10:14 AM, Paul Whitney wrote: We were on version: 389-ds-base-1.3.7.5-24. What OS? The nsslapd-cache-autosize was set to 0. We apply our own values. To keep us afloat w

[389-users] Re: Problem with userRoot cache

2019-01-16 Thread Mark Reynolds
ibuted by others. *From:* William Brown *Sent:* Tuesday, January 15, 2019 7:22:18 PM *To:* 389-users@lists.fedoraproject.org *Cc:* Paul Whitney *Subject:* Re: [389-users] Problem with userRoot cache > On 16 Jan 2019, at 06:49, Mark Reynolds wrote: &g

[389-users] Re: Problem with userRoot cache

2019-01-16 Thread Paul Whitney
turn or destroy the original message to assure that it is not read, copied, or distributed by others. From: William Brown Sent: Tuesday, January 15, 2019 7:22:18 PM To: 389-users@lists.fedoraproject.org Cc: Paul Whitney Subject: Re: [389-users] Problem wit

[389-users] Re: Problem with userRoot cache

2019-01-15 Thread William Brown
> On 16 Jan 2019, at 06:49, Mark Reynolds wrote: > > What version were you previously on? > > Sounds like an issue with autocache sizing. The errors log might give more > info about why its being reset. > > Also check if "nsslapd-cache-autosize" is set under "cn=config,cn=ldbm >

[389-users] Re: Problem with userRoot cache

2019-01-15 Thread Mark Reynolds
What version were you previously on? Sounds like an issue with autocache sizing.  The errors log might give more info about why its being reset. Also check if "nsslapd-cache-autosize" is set under "cn=config,cn=ldbm database,cn=plugins,cn=config".  If it is, set it to zero to stop the