#194 When SSSD fails to start because of an invalid configuration, pid file is still created
Closed: Fixed None Opened 14 years ago by jgalipea.

Description[[BR]]

When the services fail to start because of an invalid configuration, like No Domains configured, invalid option values, etc. pid file is still being created. So, subsequently checking the status or starting the services with a valid configuration results in "sssd dead but pid file exists"[[BR]]
[[BR]]

EXPECTED:[[BR]]
No pid file to be created when the services fail to start.[[BR]]
[[BR]]

Please reference bugzilla bug 512733.


I am still seeing the behavior when you install sssd, but do not do any modifying of nss configuration, pam auth configuration or sssd.conf.[[BR]]
[[BR]]

Just yum install and service sssd start.

Stephen - can you close this please? - This is not occurring on the current build.

Fixed in 1f4f4f1

fixedin: => 0.6.0
resolution: => fixed
status: new => closed
tests: 0 => 1

Fields changed

tests: 1 => 0
testsupdated: 0 => 1

Fields changed

rhbz: => 0

Metadata Update from @jgalipea:
- Issue set to the milestone: SSSD 0.6.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/1236

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