Hello Oleg,
'Unavailable Critical Extension' can come from a lot of places (mostly
plugins but not only).
So yes, you need to find that in logs.
First of all, you can check the access log and check if some operations
have requested something unusual (some server-side control or something).
Or, also, If the OID is not supported, it will return 'Unavailable Critical
Extension'.
If you won't find anything useful there, then you can try to look for the
info in errors log.
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11...
I think it makes sense to add 8192 — Replication debugging - first. And
wait for the error.
Then, if your error still happens silently in the logs, you can check - 128
— Access control list processing too.
Be aware, that the logs may cause performance issue so I won't recommend
running that on production.
Sincerely,
Simon
On Fri, Dec 18, 2020 at 6:56 PM Oleg Cohen <oleg.cohen(a)assurebridge.com>
wrote:
Greetings,
I run a Java application. From time to time I start seeing the following
error in the logs:
LDAP: error code 12 - Unavailable Critical Extension
I have a three node 389-DS cluster and don't see any errors in the
respective 389 DS logs.
The restart of the Java application seems to resolve the issue.
Wondering if anybody has seen this error before and how to debug/remediate.
Thanks!
Oleg
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...