Skip to content
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

Handle SIGTERM in service archetypes #770

Closed
wsargent opened this issue Apr 9, 2016 · 2 comments
Closed

Handle SIGTERM in service archetypes #770

wsargent opened this issue Apr 9, 2016 · 2 comments
Labels
feature request universal Zip, tar.gz, tgz and bash issues

Comments

@wsargent
Copy link
Contributor

wsargent commented Apr 9, 2016

From playframework/playframework#5933

When stopping a play app using the systemd init system, systemd sends a SIGTERM to the process, the jvm then exits with the 143 code which, since it's nonzero, is treated as a failure by systemd.

I think play should handle this itself and exit cleanly. As it is, we have to add SuccessExitStatus=143 to the service file (for a similar discussion see https://tickets.puppetlabs.com/si/jira.issueviews:issue-html/SERVER-70/SERVER-70.html).

@muuki88 muuki88 added feature request universal Zip, tar.gz, tgz and bash issues labels Apr 9, 2016
@muuki88
Copy link
Contributor

muuki88 commented Apr 9, 2016

@wsargent if I understood the issue correctly we would either

  • add - the ExecStart parameter
  • or add an ExitSuccessStatus setting

in the systemd template

@wsargent
Copy link
Contributor Author

wsargent commented Apr 9, 2016

I think he's asking for "ExecStart=-143" in the systemd template, yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request universal Zip, tar.gz, tgz and bash issues
Projects
None yet
Development

No branches or pull requests

2 participants