How to start and stop a systemd unit with another?
Posted
by
Andy Shinn
on Server Fault
See other posts from Server Fault
or by Andy Shinn
Published on 2014-08-19T20:27:10Z
Indexed on
2014/08/19
22:21 UTC
Read the original article
Hit count: 195
I am using CoreOS to schedule systemd units with fleet. I have two units (firehose.service
and firehose-announce.service
. I am trying to get the firehose-announce.service
to start and stop along with the firehose.service
. Here is the unit file for firehose-announce.service
:
[Unit]
Description=Firehose etcd announcer
BindsTo=firehose@%i.service
After=firehose@%i.service
Requires=firehose@%i.service
[Service]
EnvironmentFile=/etc/environment
TimeoutStartSec=30s
ExecStartPre=/bin/sh -c 'sleep 1'
ExecStart=/bin/sh -c "port=$(docker inspect -f '{{range $i, $e := .NetworkSettings.Ports }}{{$p := index $e 0}}{{$p.HostPort}}{{end}}' firehose-%i); echo -n \"Adding socket $COREOS_PRIVATE_IPV4:$port/tcp to /firehose/upstream/firehose-%i\"; while netstat -lnt | grep :$port >/dev/null; do etcdctl set /firehose/upstream/firehose-%i $COREOS_PRIVATE_IPV4:$port --ttl 300 >/dev/null; sleep 200; done"
RestartSec=30s
Restart=on-failure
[X-Fleet]
X-ConditionMachineOf=firehose@%i.service
I am trying to use BindsTo
with the notion that start and stop of firehose.service
will also start or stop firehose-announce.service
. But this never happens correctly. If firehose.service
is stopped, then firehose-announce.service
goes to failed state. But when I start firehose.service
, the firehose-announce.service
doesn't start up.
What am I doing wrong here?
© Server Fault or respective owner