Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Startup after resume takes too long #1749

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

Startup after resume takes too long #1749

sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/707

  • Created at 2010-12-10 16:39:26 by dpal
  • Closed as Fixed
  • Assigned to sbose

Resume machine in the morning. VPN is broken so there is Internet access but outside the firewall. The startup took a while meaning that the gnome login screen did not come up for a long time. I di not know if it is related to the recent gnome-screen saver fix.

I saw it yesterday too, so it is pretty reproducible.

Configuration

[sssd]
config_file_version = 2
reconnection_retries = 3
services = nss, pam
domains = foobar.com
debug_timestamps = true
debug_level = 9


[nss]
filter_groups = root
filter_users = root
entry_cache_nowait_timeout = 50

[pam]

[domain/foobar.com]
id_provider = ldap
ldap_uri = ldap://ldap.foobar.com
ldap_user_search_base = ou=Users,dc=foobar,dc=com
ldap_group_search_base = ou=Groups,dc=foobar,dc=com
enumerate = false

auth_provider = krb5
krb5_kdcip = kerberos.foobar.com, kerberos.foobar.com
krb5_auth_timeout = 5
krb5_realm = FOOBAR.COM
cache_credentials = true

access_provider = permit
bhpass_provider = krb5

krb5_store_password_if_offline = True

Log file attached. I could not detect in the log at what point the screen came up so I was able to type. But it took about 90+ seconds before it came up.

Comments


Comment from dpal at 2010-12-10 16:40:50

Cut out portion of the log
sssddp.log


Comment from sgallagh at 2010-12-14 15:32:50

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.1


Comment from sgallagh at 2011-01-04 15:23:01

Fields changed

coverity: =>
owner: somebody => sbose


Comment from sbose at 2011-01-20 12:51:02

I could reproduce this issue and it was fixed by 29993ce

resolution: => fixed
status: new => closed
upgrade: => 0


Comment from dpal at 2012-01-19 03:02:28

Fields changed

rhbz: => 0


Comment from dpal at 2017-02-24 14:30:32

Metadata Update from @dpal:

  • Issue assigned to sbose
  • Issue set to the milestone: SSSD 1.5.1
@sssd-bot sssd-bot added the Closed: Fixed Issue was closed as fixed. label May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

2 participants