-
Notifications
You must be signed in to change notification settings - Fork 82
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
Could not start Service[sssd]: #10
Comments
Hmm, I have several CentOS 6 nodes and have not experienced this. My config always goes in first and then starts the service, due this ordering in init.pp: anchor { 'sssd::begin': } ->
class { '::sssd::install': } ->
class { '::sssd::config': } ~>
class { '::sssd::service': } ->
anchor { 'sssd::end': } |
Can you provide a sample of the code you are using to include the main class? |
Service is not even started as the config file is not in place. domains key in sssd.conf is empty here(after the first run), some keys are empty too but most of the keys declared in the hash are getting populated. |
Your example looks pretty similar to mine, except this part: 'nss' => {
'filter_users' => [ 'root','ldap','named','avahi','haldaemon','dbus','radiusd','news','nscd','apache','mysql' ]
}, Is that correct? should that block have some other options? |
Other than that I'm not sure... I may be able to spin up a test box later this eve and play around. |
That's exactly what I need in this block. My only guessing that the problem is with the Ruby and the way it handles a list of hashes here? |
These are puppet hashes, so we should be shielded from the underlying ruby.... So if you run puppet a second time, it puts in your config and starts the sssd Daemon just fine? |
The thing is that the config file is created but missing some pieces from the hash, thus preventing the service to start. After 2nd run the file is in place and service starts regularly. |
I don't have any PE in my environment :( |
closed by pr #11 |
Testing your module on Centos 6. System does not get in convergent state in a single run. It seems that not all the changes have been applied on a sssd.conf during the first Puppet run. Services array is geting default values and not the values defined in a config hash.
(/Stage[main]/Sssd::Config/File[sssd_config_file]/content) -services = nss, pam, autofs
(/Stage[main]/Sssd::Config/File[sssd_config_file]/content) +services = nss,pam
The text was updated successfully, but these errors were encountered: