linux – Systemd – 在ExecStopPost中检测服务是否退出而没有错

Restart=on-failure
ExecStopPost=/path/to/script.sh

#!/usr/bin/env bash

# sleep 1; adding sleep didn't help

# this always comes out deactivating
service_status=$(systemctl is-failed app-importer) 

# could also do the other way round and check for failed
if [ $service_status = "inactive" ] 
then
  echo "Service exited normally: $service_status . Shutting down..."
  #shutdown -t 5
else
  echo "Service did not exit normally - $service_status"
fi
exit 0

您的问题是systemd在ExecPostStop进程完成之前认为该服务已停用.睡觉并没有帮助,因为它只会等待更长时间. ExecPostStop的想法是清理服务可能留下的任何内容,如临时文件,UNIX套接字等.服务未完成,并准备重新启动,直到清理完成.因此,如果你以这种方式看待它,那么systemd正在做什么是有意义的.

你应该做的是检查脚本中的$SERVICE_RESULT,$EXIT_CODE和/或$EXIT_STATUS,它将告诉你服务是如何停止的.例：

#!/bin/sh
echo running exec post script | logger
systemctl is-failed foobar.service | logger
echo $SERVICE_RESULT,$EXIT_CODE and $EXIT_STATUS | logger

当服务允许运行完成时：

Sep 17 05:58:14  systemd[1]: Started foobar.
Sep 17 05:58:17  root[1663]: foobar service will now exit
Sep 17 05:58:17  root[1669]: running exec post script
Sep 17 05:58:17  root[1671]: deactivating
Sep 17 05:58:17  root[1673]: success,exited and 0

当服务在完成之前停止时：

Sep 17 05:57:22  systemd[1]: Started foobar.
Sep 17 05:57:24  systemd[1]: Stopping foobar...
Sep 17 05:57:24  root[1643]: running exec post script
Sep 17 05:57:24  root[1645]: deactivating
Sep 17 05:57:24  root[1647]: success,killed and TERM
Sep 17 05:57:24  systemd[1]: Stopped foobar.