Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-70644

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • packaging
    • RHEL 8.7
      v2.375.3
      Installed as RPM

      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.

            Unassigned Unassigned
            isuftin Ivan Suftin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: