From 52d0886cfbcdfd69fa0cac0a6d51cd8811d8c6d7 Mon Sep 17 00:00:00 2001 From: Gaurav Yadav Date: Sun, 18 Jun 2017 23:10:57 +0530 Subject: glusterd.service (systemd), shows "Active failed" when gd in stop state While doing cleanupandexit glusterd was handling the signal SIGTERM which is clean exit but systemd treats it as failure being a non-zero value. With this fix dependency "SuccessExitStatus " has been added in glusterd.service which takes care of service stop properly. Signed-off-by: Gaurav Yadav Change-Id: Ie5216722632a245f787fd69bfbbf8d0f0068bccb BUG: 1462200 Reviewed-on: https://review.gluster.org/17559 Tested-by: Gaurav Yadav Smoke: Gluster Build System NetBSD-regression: NetBSD Build System CentOS-regression: Gluster Build System Reviewed-by: Prashanth Pai --- extras/systemd/glusterd.service.in | 1 + 1 file changed, 1 insertion(+) (limited to 'extras') diff --git a/extras/systemd/glusterd.service.in b/extras/systemd/glusterd.service.in index 26694cfc8ab..78f8e40b0e4 100644 --- a/extras/systemd/glusterd.service.in +++ b/extras/systemd/glusterd.service.in @@ -12,6 +12,7 @@ Environment="LOG_LEVEL=INFO" EnvironmentFile=-@sysconfdir@/sysconfig/glusterd ExecStart=@prefix@/sbin/glusterd -p @localstatedir@/run/glusterd.pid --log-level $LOG_LEVEL $GLUSTERD_OPTIONS KillMode=process +SuccessExitStatus=15 [Install] WantedBy=multi-user.target -- cgit