On Fri, Oct 21, 2011 at 11:02:51AM +1000, GOLLSCHEWSKY, Tim wrote:
Hi Jan, thanks for your response.
> > Reconnected to the Data Provider.
> >
> > ...here it just keeps trying to reconnect to the data provider.
> > Reconnection attempt... etc. Over and over.
> >
> > I'm not sure what this means:
> >
> > (Thu Oct 20 12:42:50 2011) [sssd] [ping_check] (4): Service
> > XXX.XXX.XXX replied to ping (Thu Oct 20 12:42:50 2011) [sssd[pam]]
> > [sbus_dispatch]
> > (1): Performing auto-reconnect (Thu Oct 20 12:42:50 2011) [sssd]
> > [sbus_dispatch] (3): Connection is not open for dispatching.
> >
> > Connection to what exactly... I'm not sure. The LDAP server? The pipe?
>
> It's sbus connection between NSS/PAM responder and the data provider.
> Could you please send sanitized logs separated for each process? You
> can achieve this by running sssd with -f. Also please set debug level a bit higher
(7 or 8 will do) so it's easier to debug.
These are the sanitized log files with debug level 8:
== sssd_XXX.XXX.XXX.log ==
(Fri Oct 21 10:43:26 2011) [sssd[be[XXX.XXX.XXX]]] [main] (1): Backend provider
(XXX.XXX.XXX) started!
(Fri Oct 21 10:43:36 2011) [sssd[be[XXX.XXX.XXX]]] [main] (1): Backend provider
(XXX.XXX.XXX) started!
(Fri Oct 21 10:43:47 2011) [sssd[be[XXX.XXX.XXX]]] [main] (1): Backend provider
(XXX.XXX.XXX) started!
Is this really it in the backend log even with a high debug_level in the
domain section if sssd.conf?
Can you check if the back end is crashing? abrt would tell you or you'd
see a message in the syslog.