[JIRA] (JENKINS-55149) Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure

[jenkins@keithmarsh.com (JIRA)]

Keith Marsh created an issue

Jenkins / JENKINS-55149 Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-12-12 12:44 Environment: Ubuntu 18.04 v2.150.1 installed via apt as per https://jenkins.io/doc/book/installing/#debianubuntu Priority: Major Reporter: Keith Marsh If you set JENKINS_ENABLE_ACCESS_LOG="yes" in /etc/default/jenkins, the startup script in /etc/init.d/jenkins appends -accessLoggerClassName... to DAEMON_ARGS.  This is incorrect and causes jenkins startup to fail with the error Dec 12 10:50:43 dtg-jenkins jenkins[28926]: /usr/bin/daemon: unrecognized option '--accessLoggerClassName=winstone.accesslog.SimpleA Dec 12 10:50:43 dtg-jenkins jenkins[28926]: usage: daemon [options] [--] [cmd arg...] Dec 12 10:50:43 dtg-jenkins jenkins[28926]: options: Dec 12 10:50:43 dtg-jenkins jenkins[28926]: -h, --help - Print a help message then exit ... Changing the line in /etc/init.d/jenkins to       JENKINS_ARGS="$JENKINS_ARGS --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined --simpleAccessLogger.file=/var/log/$NAME/access_log" makes jenkins start correctly and the access log appear correctly in /var/log/jenkins/access_log Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[dbeck@cloudbees.com (JIRA)]

Daniel Beck updated an issue

Jenkins / JENKINS-55149 Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure

Change By: Daniel Beck Component/s: packaging Component/s: core

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-55149 Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure

Change By: Oleg Nenashev Labels: newbie-friendly

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev commented on JENKINS-55149

Re: Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure Keith Marshwould you like to submit a pull request for it?

Add Comment

[jenkins@keithmarsh.com (JIRA)]

Keith Marsh commented on JENKINS-55149

Re: Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure

That's been done.  It's my first PR, so if I've gone awry, put me straight please. https://github.com/jenkinsci/packaging/pull/111

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-55149

Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure

Change By: Oleg Nenashev Labels: lts-candidate newbie-friendly

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated JENKINS-55149

https://github.com/jenkinsci/packaging/pull/111 fixes it. IIUC it might be reasonable to backport it, but I am not sure whether we have a process for packaging

Jenkins / JENKINS-55149 Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure

Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-55149 Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure

To be released in Jenkins 2.175 Change By: Oleg Nenashev Released As: Jenkins 2.175

Add Comment

[ogondza@gmail.com (JIRA)]

Oliver Gondža updated an issue

Jenkins / JENKINS-55149 Setting JENKINS_ENABLE_ACCESS_LOG="yes" causes jenkins startup failure

Change By: Oliver Gondža Labels: lts-candidate newbie-friendly

Add Comment