mohammad sereshki via FreeIPA-users wrote:
Hi But it is near 2 months that exists and servers which refer to it sometimes ger error and it does not work prperly
You need to provide more information. The snippet you provided, as I've said, is a common thing to see and can normally be ignored (and yes, it repeats every time the TGT expires AFAIR). If you server is NEVER recovering from this then that's a different matter.
What does: ipa-replica-manage list -v `hostname` show?
How about on a master with an agreement with this one?
Check /var/log/krb5kdc.log to see if a TGT is being issued.
rob
Do you have any idea how can i fix it?
On Tuesday, October 23, 2018, 5:46:44 AM GMT+11, Rob Crittenden rcritten@redhat.com wrote:
mohammad sereshki wrote:
Hi Everything works fine and with kinit I got new tgt for admin and restart but still same issue , do you have any idea about getting new tgt
The directory server uses its own keytab and should obtain it automatically. You may see a couple of these errors in a row but it should recover quickly.
rob
On Tuesday, October 23, 2018, 4:39:13 AM GMT+11, Rob Crittenden <rcritten@redhat.com mailto:rcritten@redhat.com> wrote:
mohammad sereshki via FreeIPA-users wrote:
Hi I got below error ,is there anyone who knows what is this and how can
i s=
ort it out? =C2=A0slapd_ldap_sasl_interactive_bind - Error: could not perform
interacti=
ve bind for id [] mech [GSSAPI]: LDAP error -2 (Local error)
(SASL(-1): gen=
eric failure: GSSAPI Error: Unspecified GSS failure.=C2=A0 Minor code
may p=
rovide more information (Credentials cache file '/tmp/krb5cc_491' not
found=
)) errno 0 (Success) [22/Oct/2018:16:59:33 +031800] slapi_ldap_bind - Error: could not
perform i=
nteractive bind for id [] mech [GSSAPI]: error -2 (Local error) NSMMReplicationPlugin - agmt=3D"cn=3DmeTosrv1.example.com"
(drvl124:389): R=
eplication bind with GSSAPI auth failed: LDAP error -2 (Local error)
(SASL(=
-1): generic failure: GSSAPI Error: Unspecified GSS failure.=C2=A0
Minor co=
de may provide more information (Credentials cache file
'/tmp/krb5cc_491' n=
ot found))
Is something not working?
It is likely that this is just noise. 389-ds logs when it's cert is expired (or on start up non-existent). It pretty quickly recovers from this by getting a TGT and proceeds.
rob
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahoste...