[JIRA] (JENKINS-12864) NullPointerException in winstone Launcher

[steven.jo...@computerminds.co.uk (JIRA)]

Steven Jones commented on JENKINS-12864 NullPointerException in winstone Launcher I also have this issue. Here's the command that the init.d script is trying to execute: /bin/su -l jenkins --shell=/bin/bash -c "/usr/bin/daemon --name=jenkins --inherit --env=JENKINS_HOME=/var/lib/jenkins --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid -- /usr/bin/java -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1" If I execute the following as the Jenkins user: /usr/bin/java -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 Then Jenkins starts up happily. Indeed if I execute the following as the jenkins user: /usr/bin/daemon --foreground --name=jenkins --inherit --env=JENKINS_HOME=/var/lib/jenkins --output=/var/log/jenkins/jenkins.log --pidfile=/var/run/jenkins/jenkins.pid -- /usr/bin/java -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 Then Jenkins also starts up, so I think it must be something to do with the way that Jenkins is being put into the background or something? Is there anything else I can try?

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira