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

Service restart issue #30

Closed
robert4man opened this issue Jan 17, 2017 · 3 comments
Closed

Service restart issue #30

robert4man opened this issue Jan 17, 2017 · 3 comments
Milestone

Comments

@robert4man
Copy link

When upgrading from v0.3.0 -> v0.4.0 I encountered a couple odd issues. It looks like sssd.conf received some extra line spacing to separate the sections (which is fine) resulting in a restart of messagebus, sssd and oddjobd (which also seems fine). Unfortunately it resulted in a couple error conditions for RHEL7:

  1. ssh logins were suddenly very slow, i.e. >25 seconds to connect. Sudo commands were equally slow.
  2. NetworkManager started spewing errors
    • could not create org.freedesktop.DBus proxy
    • GLib-GIO-CRITICAL **: Error while sending AddMatch() message

I was able to resolve both issues with systemctl restart systemd-logind NetworkManager. I was able to reproduce the issue manually with systemctl restart messagebus sssd oddjobd so this may be a system related bug/error. I'm not sure if there is even anything we could do from a puppet module perspective to deal with this condition, but I thought you should be aware.

@robert4man
Copy link
Author

Now that I look and think about this a little more I'm thinking maybe this construct is a little too basic:
class { '::sssd::config': } ~>
class { '::sssd::service': } ->

sssd.conf changes should only trigger sssd service restarts, not everything.

@edestecd
Copy link
Collaborator

I can agree with that. The other services were added b/c they were needed by sssd, but they def do not need restarted when config changes happen.

sgnl05 added a commit that referenced this issue Jan 20, 2017
@sgnl05 sgnl05 added this to the 0.4.1 milestone Jan 21, 2017
@sgnl05
Copy link
Owner

sgnl05 commented Jan 24, 2017

Fixed in 0.4.1

@sgnl05 sgnl05 closed this as completed Jan 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants