#494 Connecting to the network after an offline kerberos auth logs continuous error messages to sssd_ldap.log
Closed: Fixed None Opened 13 years ago by sgallagh.

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=591873

Description of problem

Connecting to the network after an offline auth logs continuous error messages
to sssd_ldap.log which causes it to grow at a rapid pace until stopping it by
doing a "service sssd restart".

Version-Release number of selected component (if applicable)

sssd-1.1.91-10.el6.x86_64

How reproducible

Every time

Steps to Reproduce

  • Do a tail -f /var/log/sssd/sssd_ldap.log on a separate terminal for

monitoring.

  1. configure sssd.conf for kerberos auth.
  2. login as "sssd" user to cache credentials - authentication successful.
  3. logout.
  4. disconnect the network.
  5. login as "sssd" - authentication successful with cached credentials.
  6. logout.
  7. connect the network.
  8. wait for a few seconds ~30.
  9. Observer the log messages in the other terminal.

Actual results

<snip>
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
</snip>

The above error gets logged continuously until a service sssd restart.

Expected results

Should not log any error messages.

Additional info

Configuration:
https://bugzilla.redhat.com/attachment.cgi?id=413728

Full log:
https://bugzilla.redhat.com/attachment.cgi?id=413731


Fields changed

description: Cloned from https://bugzilla.redhat.com/process_bug.cgi

== Description of problem ==
Connecting to the network after an offline auth logs continuous error messages
to sssd_ldap.log which causes it to grow at a rapid pace until stopping it by
doing a "service sssd restart".

== Version-Release number of selected component (if applicable) ==
sssd-1.1.91-10.el6.x86_64

== How reproducible ==
Every time

== Steps to Reproduce ==

  • Do a tail -f /var/log/sssd/sssd_ldap.log on a separate terminal for
    monitoring.
  1. configure sssd.conf for kerberos auth.
  2. login as "sssd" user to cache credentials - authentication successful.
  3. logout.
  4. disconnect the network.
  5. login as "sssd" - authentication successful with cached credentials.
  6. logout.
  7. connect the network.
  8. wait for a few seconds ~30.
  9. Observer the log messages in the other terminal.

=== Actual results ===
{{{
<snip>
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
</snip>
}}}
The above error gets logged continuously until a service sssd restart.

=== Expected results ===
Should not log any error messages.

== Additional info ==
Configuration:
https://bugzilla.redhat.com/attachment.cgi?id=413728

Full log:
https://bugzilla.redhat.com/attachment.cgi?id=413731 => Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=591873

== Description of problem ==
Connecting to the network after an offline auth logs continuous error messages
to sssd_ldap.log which causes it to grow at a rapid pace until stopping it by
doing a "service sssd restart".

== Version-Release number of selected component (if applicable) ==
sssd-1.1.91-10.el6.x86_64

== How reproducible ==
Every time

== Steps to Reproduce ==

  • Do a tail -f /var/log/sssd/sssd_ldap.log on a separate terminal for
    monitoring.
  1. configure sssd.conf for kerberos auth.
  2. login as "sssd" user to cache credentials - authentication successful.
  3. logout.
  4. disconnect the network.
  5. login as "sssd" - authentication successful with cached credentials.
  6. logout.
  7. connect the network.
  8. wait for a few seconds ~30.
  9. Observer the log messages in the other terminal.

=== Actual results ===
{{{
<snip>
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (8): Trace:
sh[0x1bc0e20], connected[0], ops[(nil)], ldap[0x1bc1040]
(Thu May 13 15:11:38 2010) [sssd[be[ldap]]] [sdap_process_result] (2): ERROR:
LDAP connection is not connected!
</snip>
}}}
The above error gets logged continuously until a service sssd restart.

=== Expected results ===
Should not log any error messages.

== Additional info ==
Configuration:
https://bugzilla.redhat.com/attachment.cgi?id=413728

Full log:
https://bugzilla.redhat.com/attachment.cgi?id=413731

Fields changed

status: new => assigned

Fixed by 48c3ce8

fixedin: => 1.2.1
resolution: => fixed
status: assigned => closed

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.2.1

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1536

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata