Nomad service stops with exit code: 1

Nomad
1

Hi All,
When I stop (or restart) Nomad client/server service using systemctl stop nomad
I see following in syslog:

node002 systemd[1]: nomad.service: Main process exited, code=exited, status=1/FAILURE
node002 systemd[1]: nomad.service: Failed with result 'exit-code'.

Hence when I issue systemctl status nomad it shows
Active: failed (Result: exit-code)
What might be a reason for that? I don’t see any errors in syslog when nomad service starts, all parameters in systemd unit file are correct as I see.
I see the same behaviour on 3 servers and 3 clients in my cluster.

OS: Ubuntu 20
Nomad version: 0.10.9

/etc/systemd/system/nomad.service

[Unit]
Description=Nomad
Documentation=https://nomadproject.io/docs/
Wants=network-online.target
After=network-online.target
StartLimitBurst=3
StartLimitIntervalSec=10

# When using Nomad with Consul it is not necessary to start Consul first. These
# lines start Consul before Nomad as an optimization to avoid Nomad logging
# that Consul is unavailable at startup.
# Wants=consul.service
# After=consul.service

[Service]
ExecReload=/bin/kill -HUP $MAINPID
ExecStart=/usr/bin/nomad agent -config /etc/nomad
KillMode=process
KillSignal=SIGINT
LimitNOFILE=65536
LimitNPROC=infinity
Restart=on-failure
RestartSec=10
TasksMax=infinity
OOMScoreAdjust=-1000

[Install]
WantedBy=multi-user.target
2

Hi @nnermakov,

The Nomad agent will by default always exit forcefully on any signal given, and thus return an exit code of 1. This can be controlled by the leave_on_interrupt configuration parameter. The agent code that handles capturing and reacting signals can be found here if you’re interested.

Thanks,
jrasell and the Nomad team