-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
systemd unit file kills executors when nomad agent is stopped #4302
Comments
adding https://github.com/hashicorp/nomad/blob/master/dist/systemd/nomad.service documentation reference: https://www.freedesktop.org/software/systemd/man/systemd.kill.html#KillMode= |
@ramSeraph Could you submit a PR for changing that sample config file? - this default makes sense |
I considered doing the same (we're running edit: on a second read, i might be wrong about that. |
@insanejudge thanks for the PR. I was offline and didn't see the response |
FYI, #4305 (comment) |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.8.3 (c85483d)
Operating system and Environment details
uname -a
Linux <hostname> 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
systemd --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
Issue
restarting nomad agent on the host restarts the jobs on the host when nomad is running under systemd
Reproduction steps
systemctl stop nomad
stops the running executors on the hostthen if i do a
systemctl start nomad
, the reattachment attempt kills the existing containers as the corresponding executors are deadThe text was updated successfully, but these errors were encountered: