automatically. You may see a couple of these errors in a row but it
should recover quickly.
>
> On Tuesday, October 23, 2018, 4:39:13 AM GMT+11, Rob Crittenden
> <
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
>