<p dir="ltr">I did. debug_level was set to 10 in both two separate sectiins of the config file. You said to set it to at least 7 in both places.</p>
<p dir="ltr">I'll rerun things tonight and see if I can get something.</p>
<p dir="ltr">Thanks</p>
<div class="gmail_quote">On Aug 14, 2015 8:59 AM, "Jakub Hrozek" <<a href="mailto:jhrozek@redhat.com">jhrozek@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Aug 14, 2015 at 08:26:57AM -0400, Dmitri Pal wrote:<br>
> On 08/14/2015 08:24 AM, brendan kearney wrote:<br>
> ><br>
> > I am using rsyslog RELP (reliable event log processing) to steal away<br>
> > logs over syslog-tcp with fifo buffer to store them in a central<br>
> > database, so journalctl is the only local log on the box. The<br>
> > /var/log/sssd/* files are mostly empty. The only info in there is<br>
> > about an explicit kerberos setting not being set and having to use a<br>
> > different directives value for kerberos.<br>
> ><br>
> > Either way, the logs dont have much to go on.<br>
> ><br>
><br>
> You need to raise debug level for the logs to have more info.<br>
<br>
Right, the default log level is 0. See:<br>
<a href="https://fedorahosted.org/sssd/wiki/Troubleshooting" rel="noreferrer" target="_blank">https://fedorahosted.org/sssd/wiki/Troubleshooting</a><br>
<br>
btw sssd doesn't use syslog or journal by default to write the debug<br>
logs. We simply open the files and fwrite() to them, so even though your<br>
log config forwards syslog messages, the sssd log directory should<br>
contain files once you raise the debug_level.<br>
_______________________________________________<br>
sssd-users mailing list<br>
<a href="mailto:sssd-users@lists.fedorahosted.org">sssd-users@lists.fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/sssd-users" rel="noreferrer" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/sssd-users</a><br>
</blockquote></div>