Hi William,
Thanks for the response. I'll check on that and let you know if that resolves
the problem or not. Thanks again.
On 1/16/19, 3:02 PM, "William Brown" wrote:
> On 17 Jan 2019, at 06:25, Jason Jenkins wrote:
>
> Hi,
>
> One of my consumers is
> On 17 Jan 2019, at 06:25, Jason Jenkins wrote:
>
> Hi,
>
> One of my consumers is showing the following error:
>
> Entry "uid=,ou=People,dc=XXX" has unknown object class "ldapPublicKey"
> WARNING: passwordPolicy modify error 65 on entry uid=,ou=People,dc=XXX
>
>
> This error
> On 17 Jan 2019, at 02:38, Mark Reynolds wrote:
>
> 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 we have been forced
Hi Mark,
Thanks for all your help. I was able to role back to the 1.3.7 base just by
stopping services, removing the new packages, install the old packages, and
start the service back up. In the process I lost the ability to start the
"dirsrv.target" but I can start the individual instances
Hi,
One of my consumers is showing the following error:
Entry "uid=,ou=People,dc=XXX" has unknown object class "ldapPublicKey"
WARNING: passwordPolicy modify error 65 on entry uid=,ou=People,dc=XXX
This error is coming up for anyone that tries to authenticate against this
consumer. It
On 1/16/19 12:42 PM, Paul Whitney wrote:
Mark,
Thank you for figuring out the issue we are having. Question, is it
possible for us to roll back/downgrade the 389-ds to a "previously"
working version?
You'd have to go back to 389-ds-base-1.3.7, but I don't know if that's
possible on
Mark,
Thank you for figuring out the issue we are having. Question, is it possible
for us to roll back/downgrade the 389-ds to a "previously" working version?
Paul M. Whitney, RHCSA, CISSP
Chesapeake IT Consulting, Inc.
2680 Tobacco Rd
Chesapeake Beach, MD 20732
Work: 443-492-2872
Cell:
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_bug.cgi?id=1627512
https://pagure.io/389-ds-base/issue/49618
So sounds like you need to upgrade to:
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_bug.cgi?id=1627512
https://pagure.io/389-ds-base/issue/49618
So sounds like you need to upgrade to:
389-ds-base-1.3.8.4-21 (RHEL/Centos 7.6)
Or
Hi Paul,
Okay I think I found the bug you are running into:
https://bugzilla.redhat.com/show_bug.cgi?id=1627512
https://pagure.io/389-ds-base/issue/49618
So sounds like you need to upgrade to:
389-ds-base-1.3.8.4-21 (RHEL/Centos 7.6)
Or build the upstream 1.3.7 server yourself using
Hi Mark,
OS = CentOS 7.6.1810
Kernel = 3.10.0-957.1.3
I have access to the logs, just cannot port them over to this side of the
network. :-)
Paul M. Whitney, RHCSA, CISSP
Chesapeake IT Consulting, Inc.
2680 Tobacco Rd
Chesapeake Beach, MD 20732
Work: 443-492-2872
Cell: 410.493.9448
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 we have been forced to enable
nsslapd-cache-autosize. However, our performance has degraded in
We were on version: 389-ds-base-1.3.7.5-24.
The nsslapd-cache-autosize was set to 0. We apply our own values.
To keep us afloat we have been forced to enable nsslapd-cache-autosize.
However, our performance has degraded in response times and feel we are not
able to better
13 matches
Mail list logo
