[JIRA] (JENKINS-55053) Jenkins init script does not stop jenkins if JENKINS_HOME not found

[jlher...@capgemini.com (JIRA)]

Title: Message Title

Jeremy L created an issue   Jenkins / JENKINS-55053 Jenkins init script does not stop jenkins if JENKINS_HOME not found Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-12-06 13:45 Environment: Centos7 Labels: jenkins Priority: Minor Reporter: Jeremy L Hello, I run into an issue with the jenkins.init script : it does not stop jenkins process if JENKINS_HOME does not exist and it returns 0 like everything was fine. In my case /var/lib/jenkins is stored on a NAS, if I start jenkins and then unmount /var/lib/jenkins, jenkins.init stop will not stop jenkins. It's a problem if you use failover system like corosync to start another jenkins instance in case of failure because the script returns 0 and corosync will assume that jenkins is stopped. As you can see below, this behavior happens only when you try to stop jenkins, others commands will return 1. [ -d "$JENKINS_HOME" ] || { echo "JENKINS_HOME directory does not exist: $JENKINS_HOME"; if [ "$1" = "stop" ]; then exit 0; else exit 1; fi; } Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.