Bug 1095988

Summary:	systemd killing everything in cgroup when ssh session closes?
Product:	[Fedora] Fedora	Reporter:	Ian Colle <icolle>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	johannbg, lnykryn, msekleta, plautrba, s, systemd-maint, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-17 20:14:22 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 Ian Colle 2014-05-09 03:10:50 UTC

Description of problem:
I'm 90% sure this is systemd killing everything in the cgroup when ceph-deploy's ssh session closes. The log file just ends (kill -9?) right when the ceph-deploy command finishes. In the cases where we start several OSDs at once, they all stay running until it finishes and then all die at once, consistent with the ssh close.

The f19 config options don't explicitly enable KillUserProcesses or kill-session-processes (at least that i can see), but i can't figure out how to view what the default is.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: Log of one of the failed tests
http://qa-proxy.ceph.com/teuthology/teuthology-2014-03-05_01:10:15-ceph-deploy-firefly-distro-basic-vps/117053/teuthology.log

http://tracker.ceph.com/issues/7627

Comment 1 Zbigniew Jędrzejewski-Szmek 2014-05-09 12:25:27 UTC

The default is control-group, consistent with your description (see http://www.freedesktop.org/software/systemd/man/systemd.kill.html#KillMode=).
You shouldn't start system services from within a user session (long-lived or otherwise), but from within a systemd unit.

Using http://www.freedesktop.org/software/systemd/man/systemd-run.html is one way to do it without running any unit files.

Comment 2 Fedora End Of Life 2015-01-09 21:21:24 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 20:14:22 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.