Currently is sometimes takes up to 60 seconds to determine that the system is offline.
I usually see it with the case when the machine is connected to the enterprise network over VPN over the local wireless connection. From time to time VPN drops. When this happens while logged in but screen is locked the time to determine the offline status turns to long.
How to reproduce: 1) Log into local wireless network 2) Start VPN 3) Lock screen 4) VPN connection expires or breaks 5) Try to unlock the screen
Expected: Up to 10 sec delay
Actual: Up to 60 second delay
Note: I suggest trying to connect for 2 sec to each of the fail over servers in the list. 2 seconds nowadays should be enough to establish connection. If the connection is not established in 2 seconds it is fair to assume that the server is unreachable for whatever reason.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.1 owner: somebody => sgallagh
We think this may be an issue with RHEL5's openldap and/or vpnc features, and not the SSSD. We will re-evaluate if this appears in newer OSes.
milestone: SSSD 1.1 => SSSD Deferred
Fixed by db534f6eb40f083860756afe3b2d0589f271dec0
component: SSSD => LDAP Provider fixedin: => 1.2.0 milestone: SSSD Deferred => SSSD 1.2.0 resolution: => fixed status: new => closed
rhbz: => 0
Metadata Update from @dpal: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.2.0
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/1453
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.