Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1029838

Summary: Stopping sssd service doesn't kill sssd daemon started from cmdline
Product: Red Hat Enterprise Linux 7 Reporter: Kaushik Banerjee <kbanerje>
Component: sssdAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED WONTFIX QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: dlackey, dpal, grajaiya, jgalipea, lslebodn, mkosek, pbrezina
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-14 14:05:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kaushik Banerjee 2013-11-13 10:39:33 UTC 
Description of problem:
Stopping sssd service doesn't kill sssd daemon started from cmdline

Version-Release number of selected component (if applicable):
1.11.2-1.el7

How reproducible:
Always

Steps to Reproduce:
1. sssd -d 9 -f -c /tmp/sssd.conf

2. # systemctl stop sssd.service
# ps ax | grep sssd
18140 ?        Ss     0:00 sssd -d 9 -f -c /tmp/sssd.conf
18141 ?        S      0:00 /usr/libexec/sssd/sssd_be --domain LDAPTEST -d 0x77f0 --debug-to-files
18142 ?        S      0:00 /usr/libexec/sssd/sssd_nss -d 0x77f0 --debug-to-files
18143 ?        S      0:00 /usr/libexec/sssd/sssd_pam -d 0x77f0 --debug-to-files

3. # systemctl restart sssd.service
# ps ax | grep sssd
18140 ?        Ss     0:00 sssd -d 9 -f -c /tmp/sssd.conf
18141 ?        S      0:00 /usr/libexec/sssd/sssd_be --domain LDAPTEST -d 0x77f0 --debug-to-files
18142 ?        S      0:00 /usr/libexec/sssd/sssd_nss -d 0x77f0 --debug-to-files
18143 ?        S      0:00 /usr/libexec/sssd/sssd_pam -d 0x77f0 --debug-to-files
18333 ?        Ss     0:00 /usr/sbin/sssd -D -f
18334 ?        S      0:00 /usr/libexec/sssd/sssd_be --domain LDAPTEST --debug-to-files
18335 ?        S      0:00 /usr/libexec/sssd/sssd_nss --debug-to-files
18336 ?        S      0:00 /usr/libexec/sssd/sssd_pam --debug-to-files

Actual results:
Stopping sssd service doesn't kill existing sssd processes.

Expected results:


Additional info:
"service sssd stop" on RHEL6 kills manually run sssd processes.
Comment 2 Jakub Hrozek 2013-11-13 13:35:39 UTC 
That's not something sssd controls, it's a feature of systemd. I just tried it with httpd as well and it's the same "issue".

Closing. Please reopen this bug against systemd if you don't like the current behaviour.
Comment 3 Kaushik Banerjee 2013-11-13 14:52:04 UTC 
sssd can be started from cmdline but needs to be killed from cmdline since systemctl cannot stop the process starting from cmdline.

This is a change in behaviour from RHEL6.

Re-opening this bug to have this documented in release note and IPA installation guide.
Comment 4 Jakub Hrozek 2013-11-13 14:59:07 UTC 
(In reply to Kaushik Banerjee from comment #3)
> sssd can be started from cmdline but needs to be killed from cmdline since
> systemctl cannot stop the process starting from cmdline.
> 
> This is a change in behaviour from RHEL6.
> 
> Re-opening this bug to have this documented in release note and IPA
> installation guide.

Kaushik, this is not a change in behaviour in sssd and there is nothing we can do about this. Please reassign to systemd if you think this requires documentation. Thanks.
Comment 5 Jenny Severance 2013-11-13 17:48:13 UTC 
We need to make sure that man pages and documentation are updated to reflect that sssd can not be started this way ... remove references to it etc ...  It would also be nice to fail with an appropriate message.
Comment 6 Jakub Hrozek 2013-11-13 17:53:42 UTC 
(In reply to Jenny Galipeau from comment #5)
> We need to make sure that man pages and documentation are updated to reflect
> that sssd can not be started this way ... remove references to it etc ... 
> It would also be nice to fail with an appropriate message.

SSSD *can* be started manually, it just needs to be stopped manually as well, either with Ctrl+C on the command line or by sending SIGTERM to the monitor process.

If you start SSSD with one mechanism (manually) you can't stop it with another mechanism (systemctl). That's expected. We never documented this worked and frankly I'd consider the new behaviour an improvement.

We can discuss tomorrow on the meeting..
Comment 7 Dmitri Pal 2013-11-14 14:05:08 UTC 
Decision: close this one and open a doc bug against systemd.