Setting JENKINS_ENABLE_ACCESS_LOG to "no" in sysconfig causes errors on service start (RHEL 8)

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      This doesn't seem to break our deploy but I did notice that when we do set the "JENKINS_ENABLE_ACCESS_LOG" variable to "no" in /etc/sysconfig/jenkins, when we launch Jenkins, we do see the following in /var/log/messages:

      jenkins[40626]: /usr/bin/jenkins: line 110: no: command not found

      Line 110 in /usr/bin/jenkins is:

       

      if [ -n "${JENKINS_ENABLE_ACCESS_LOG}" ] && $JENKINS_ENABLE_ACCESS_LOG; then
	inferred_jenkins_opts="${inferred_jenkins_opts} --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger"
	inferred_jenkins_opts="${inferred_jenkins_opts} --simpleAccessLogger.format=combined"
	inferred_jenkins_opts="${inferred_jenkins_opts} --simpleAccessLogger.file='/var/log/jenkins/access_log'"
fi

      So I'm assuming it's trying to run the variable "$JENKINS_ENABLE_ACCESS_LOG" in the second half of that if statement and fails.

            Assignee:
            Unassigned
            Reporter:
            Ivan Suftin
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: