When SSSD fails to start because of an invalid configuration, pid file is still created

[sssd-bot]

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

• Created at 2009-09-21 16:36:54 by jgalipea
• Closed as Fixed
• Assigned to nobody

---

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.

Comments

---

Comment from jgalipea at 2009-09-21 17:18:20

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.

---

Comment from jgalipea at 2009-09-22 15:29:15

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

---

Comment from sgallagh at 2009-09-22 15:31:34

Fixed in 1f4f4f1

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

---

Comment from jgalipea at 2009-09-22 17:05:27

Fields changed

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

---

Comment from dpal at 2012-01-19 02:19:35

Fields changed

rhbz: => 0

---

Comment from jgalipea at 2017-02-24 14:53:39

Metadata Update from @jgalipea:

• Issue set to the milestone: SSSD 0.6.0