Quantcast

wbinfo -g stops after some hours

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

wbinfo -g stops after some hours

Lars Maes
Hi All,

I am using samba 4.2.10+dfsg-0+deb8u3 and have winbind running and joined to a windows AD.

When starting winbind everthing works, wbinfo -u, wbinfo -g returns all stuff correct.
But after an hour or so this is being shown in the logs:

[2016/06/14 19:15:02.239460,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ Miscellaneous failure (see text): Message stream modified]
[2016/06/14 19:15:02.239604,  0] ../source3/libads/sasl.c:764(ads_sasl_spnego_bind)
  kinit succeeded but ads_sasl_spnego_gensec_bind(KRB5) failed: An internal error occurred.
[2016/06/14 19:25:01.370737,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ Miscellaneous failure (see text): Message stream modified]
[2016/06/14 19:25:04.498488,  0] ../source3/libads/sasl.c:764(ads_sasl_spnego_bind)
  kinit succeeded but ads_sasl_spnego_gensec_bind(KRB5) failed: Invalid credentials
[2016/06/14 19:35:01.634212,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ Miscellaneous failure (see text): Message stream modified]
[2016/06/14 19:35:01.773252,  0] ../source3/libads/sasl.c:764(ads_sasl_spnego_bind)
  kinit succeeded but ads_sasl_spnego_gensec_bind(KRB5) failed: Invalid credentials
[2016/06/14 19:45:01.884970,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ Miscellaneous failure (see text): Message stream modified]
[2016/06/14 19:45:02.015390,  0] ../source3/libads/sasl.c:764(ads_sasl_spnego_bind)
  kinit succeeded but ads_sasl_spnego_gensec_bind(KRB5) failed: Invalid credentials

and after some time it changes to:

[2016/06/15 05:25:01.628669,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ The context has expired: Success]
[2016/06/15 05:25:01.781881,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ The context has expired: Success]
[2016/06/15 05:25:01.782074,  0] ../source3/libads/sasl.c:764(ads_sasl_spnego_bind)
  kinit succeeded but ads_sasl_spnego_gensec_bind(KRB5) failed: An internal error occurred.
[2016/06/15 05:35:01.924251,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ The context has expired: Success]
[2016/06/15 05:35:02.046027,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ The context has expired: Success]
[2016/06/15 05:35:02.046161,  0] ../source3/libads/sasl.c:764(ads_sasl_spnego_bind)
  kinit succeeded but ads_sasl_spnego_gensec_bind(KRB5) failed: An internal error occurred.
[2016/06/15 05:45:01.144497,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ The context has expired: Success]
[2016/06/15 05:45:01.264120,  0] ../source3/librpc/crypto/gse.c:341(gse_get_client_auth_token)
  gss_init_sec_context failed with [ The context has expired: Success]
[2016/06/15 05:45:01.264270,  0] ../source3/libads/sasl.c:764(ads_sasl_spnego_bind)
  kinit succeeded but ads_sasl_spnego_gensec_bind(KRB5) failed: An internal error occurred.

What could be wrong here?

Best Regards,
Lars Maes




--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: wbinfo -g stops after some hours

Madguy
This post has NOT been accepted by the mailing list yet.
Consider rejoining you Domain (example.domain.com) and issuing the command
sudo net rpc getsid -S example.domain.com

Loading...