#105 reconnection endless loop
Closed: Fixed None Opened 14 years ago by simo.

after latest patches it seems that reconnection to dp is not working properly.

The nss and pam client seem to try forever to reconnect, and they apparently suceed on their end, but the dp end simply claims a timeout has occurred and closes the connection again.

LOOPING forever at level 4 debug:

[sssd[pam]] [sbus_dispatch] (1): Performing auto-reconnect
[sssd[nss]] [sbus_dispatch] (1): Performing auto-reconnect
[sssd[nss]] [sbus_reconnect] (3): Making reconnection attempt 1 to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[nss]] [sbus_reconnect] (3): Reconnected to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[nss]] [nss_dp_reconnect_init] (1): Reconnected to the Data Provider.
[sssd[pam]] [sbus_reconnect] (3): Making reconnection attempt 1 to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[pam]] [sbus_reconnect] (3): Reconnected to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[pam]] [pam_dp_reconnect_init] (1): Reconnected to the Data Provider.
[sssd[dp]] [init_timeout] (2): Client timed out before Identification!
[sssd[dp]] [init_timeout] (2): Client timed out before Identification!

Fields changed

priority: major => critical

This is a serious bug and should be fixed for 0.5.0.

You broke it, you bought it.

description: after latest patches it seems that reconnection to dp is not working properly.
The nss and pam client seem to try forever to reconnect, and they apparently suceed on their end, but the dp end simply claims a timeout has occurred and closes the connection again.

LOOPING forever at level 4 debug:
[sssd[pam]] [sbus_dispatch] (1): Performing auto-reconnect
[sssd[nss]] [sbus_dispatch] (1): Performing auto-reconnect
[sssd[nss]] [sbus_reconnect] (3): Making reconnection attempt 1 to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[nss]] [sbus_reconnect] (3): Reconnected to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[nss]] [nss_dp_reconnect_init] (1): Reconnected to the Data Provider.
[sssd[pam]] [sbus_reconnect] (3): Making reconnection attempt 1 to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[pam]] [sbus_reconnect] (3): Reconnected to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[pam]] [pam_dp_reconnect_init] (1): Reconnected to the Data Provider.
[sssd[dp]] [init_timeout] (2): Client timed out before Identification!
[sssd[dp]] [init_timeout] (2): Client timed out before Identification!
=> after latest patches it seems that reconnection to dp is not working properly.

The nss and pam client seem to try forever to reconnect, and they apparently suceed on their end, but the dp end simply claims a timeout has occurred and closes the connection again.

LOOPING forever at level 4 debug:
{{{
[sssd[pam]] [sbus_dispatch] (1): Performing auto-reconnect
[sssd[nss]] [sbus_dispatch] (1): Performing auto-reconnect
[sssd[nss]] [sbus_reconnect] (3): Making reconnection attempt 1 to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[nss]] [sbus_reconnect] (3): Reconnected to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[nss]] [nss_dp_reconnect_init] (1): Reconnected to the Data Provider.
[sssd[pam]] [sbus_reconnect] (3): Making reconnection attempt 1 to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[pam]] [sbus_reconnect] (3): Reconnected to [unix:path=/var/lib/sss/pipes/private/sbus-dp]
[sssd[pam]] [pam_dp_reconnect_init] (1): Reconnected to the Data Provider.
[sssd[dp]] [init_timeout] (2): Client timed out before Identification!
[sssd[dp]] [init_timeout] (2): Client timed out before Identification!
}}}
owner: somebody => simo
priority: critical => blocker

I cannot reproduce this bug. Please check if this still happens with the latest version.

priority: blocker => major

fixed in: c0f3393

fixedin: => 0.5.0
priority: major => blocker
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @simo:
- Issue assigned to simo
- Issue set to the milestone: SSSD 1.0

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/1147

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