Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1401161 - Updating to latest packages of jenkins prevents jenkins from properly starting
Summary: Updating to latest packages of jenkins prevents jenkins from properly starting
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: jenkins
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Srb
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1401714 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-03 04:35 UTC by David Hill
Modified: 2017-03-14 02:21 UTC (History)
10 users (show)

Fixed In Version: jenkins-1.651.3-5.fc25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-13 23:55:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description David Hill 2016-12-03 04:35:48 UTC 
Description of problem:

Updating to latest packages of jenkins prevents jenkins from properly starting

java.io.FileNotFoundException: /usr/share/jenkins/webroot/WEB-INF/lib/jtidy.jar (Too many levels of symbolic links)

java.io.FileNotFoundException: /usr/share/jenkins/webroot/WEB-INF/lib/mina-core.jar (Too many levels of symbolic links)




java.io.FileNotFoundException: /usr/share/jenkins/webroot/WEB-INF/lib/mina-core.jar (Too many levels of symbolic links)
        at java.io.FileInputStream.open0(Native Method)
        at java.io.FileInputStream.open(FileInputStream.java:195)
        at java.io.FileInputStream.<init>(FileInputStream.java:138)
        at org.eclipse.jetty.util.resource.FileResource.getInputStream(FileResource.java:286)
        at org.eclipse.jetty.webapp.JarScanner.matched(JarScanner.java:151)
        at org.eclipse.jetty.util.PatternMatcher.matchPatterns(PatternMatcher.java:100)
        at org.eclipse.jetty.util.PatternMatcher.match(PatternMatcher.java:82)
        at org.eclipse.jetty.webapp.JarScanner.scan(JarScanner.java:84)
        at org.eclipse.jetty.webapp.MetaInfConfiguration.preConfigure(MetaInfConfiguration.java:84)
        at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:457)
        at winstone.HostConfiguration$1.preConfigure(HostConfiguration.java:166)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:493)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
        at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
        at org.eclipse.jetty.server.Server.doStart(Server.java:282)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
        at winstone.Launcher.<init>(Launcher.java:152)
        at winstone.Launcher.main(Launcher.java:352)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at Main._main(Main.java:290)
        at Main.main(Main.java:104)

Dec 02, 2016 11:19:13 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started SelectChannelConnector.0.0:8080
Dec 02, 2016 11:19:13 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
Dec 02, 2016 11:23:06 PM winstone.Logger logInternal
INFO: JVM is terminating. Shutting down Winstone
Dec 02, 2016 11:23:07 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-8.1.17.v20150415
Dec 02, 2016 11:23:07 PM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Failed startup of context w.{,file:/usr/share/jenkins/webroot/},/usr/share/jenkins/webroot
java.io.FileNotFoundException: /usr/share/jenkins/webroot/WEB-INF/lib/mina-core.jar (Too many levels of symbolic links)
        at java.io.FileInputStream.open0(Native Method)
        at java.io.FileInputStream.open(FileInputStream.java:195)
        at java.io.FileInputStream.<init>(FileInputStream.java:138)
        at org.eclipse.jetty.util.resource.FileResource.getInputStream(FileResource.java:286)
        at org.eclipse.jetty.webapp.JarScanner.matched(JarScanner.java:151)
        at org.eclipse.jetty.util.PatternMatcher.matchPatterns(PatternMatcher.java:100)
        at org.eclipse.jetty.util.PatternMatcher.match(PatternMatcher.java:82)
        at org.eclipse.jetty.webapp.JarScanner.scan(JarScanner.java:84)
        at org.eclipse.jetty.webapp.MetaInfConfiguration.preConfigure(MetaInfConfiguration.java:84)
        at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:457)
        at winstone.HostConfiguration$1.preConfigure(HostConfiguration.java:166)
        at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:493)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
        at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
        at org.eclipse.jetty.server.Server.doStart(Server.java:282)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
        at winstone.Launcher.<init>(Launcher.java:152)
        at winstone.Launcher.main(Launcher.java:352)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at Main._main(Main.java:290)
        at Main.main(Main.java:104)

Version-Release number of selected component (if applicable):
Dec 02 22:52:35 DEBUG ---> Package jenkins.noarch 1.651.3-1.fc25 will be upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins.noarch 1.651.3-2.fc25 will be an upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-webapp.noarch 1.651.3-1.fc25 will be upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-webapp.noarch 1.651.3-2.fc25 will be an upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-cli.noarch 1.651.3-1.fc25 will be upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-cli.noarch 1.651.3-2.fc25 will be an upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-core.noarch 1.651.3-1.fc25 will be upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-core.noarch 1.651.3-2.fc25 will be an upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-remoting.noarch 2.59-1.fc25 will be upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-remoting.noarch 2.62.3-1.fc25 will be an upgrade
Dec 02 22:52:35 DEBUG ---> Package jenkins-remoting-webapp.noarch 2.59-1.fc25 will be upgraded
Dec 02 22:52:35 DEBUG ---> Package jenkins-remoting-webapp.noarch 2.62.3-1.fc25 will be an upgrade


How reproducible:
This time

Steps to Reproduce:
1. Update from 2.62.3-1 to 2.62.3-2
2.
3.

Actual results:
Fails to properly start

Expected results:
Start properly

Additional info:
I deleted the symlinks and restarted the service which started but idk in which state is now my jenkins instance.
Comment 1 Gwyn Ciesla 2017-01-03 19:38:42 UTC 
*** Bug 1401714 has been marked as a duplicate of this bug. ***
Comment 2 Gwyn Ciesla 2017-01-04 16:22:39 UTC 
I submitted a build commenting these symlinks out, and it builds and runs on f25, but not rawhide or f24.  It needs a package still in testing, jenkins-remoting.
Comment 3 Carl Bennett 2017-01-09 02:01:49 UTC 
I'm having this error as well.

jenkins-1.651.3-2.fc25.noarch
Comment 4 Tim Way 2017-01-14 17:26:55 UTC 
I hit this error as well. In the SPEC for the RPM it runs a command to create the symlinks. For some reason these aren't created correctly during install but the command the SPEC uses runs w/sudo after the install w/the same result of a working install.

cd /usr/share/jenkins/webroot/WEB-INF/lib
ls -lah | grep -e 'jtidy\|mina-core'
sudo ln -sf `build-classpath jtidy` jtidy.jar
sudo ln -sf `build-classpath apache-mina/mina-core` mina-core.jar
ls -lah | grep -e 'jtidy\|mina-core'

sudo systemctl start jenkins.service

Jon, I'm not sure if commenting out the link creating for jtidy or mina-core is a good solution or just enough to get a web interface running. That said I'm also not sure why the link creating is failing w/the current RPM since the commands run and the required packages are installed. The required packages would be jtidy.noarch and apache-mina-mina-core.noarch.
Comment 5 Gwyn Ciesla 2017-01-17 15:59:23 UTC 
I'm not sure either.  All I can say is that since I got it set up it's been working fine for me.  That it builds only on f25 and not f24 or rawhide is problematic, and I've not made headway on that.  I'm not sure if pushing an update with my build is a good idea or not.
Comment 6 Tim Way 2017-01-17 17:44:39 UTC 
If I have some time maybe I will compare the SPEC from the Jenkins project upstream to see what they may be doing differently. I may also see if it's worth packing up an updated version.
Comment 7 Gwyn Ciesla 2017-01-17 17:48:03 UTC 
Possibly, but that means Jenkins 2.x.
Comment 8 Carl Bennett 2017-01-17 19:13:33 UTC 
Please keep us informed on what you find out!
Comment 9 Milan Kubík 2017-02-27 16:01:00 UTC 
Hi, what is the status on this bug?
Comment 10 Tim Way 2017-02-27 17:25:20 UTC 
Milan,

For some reason the link creation for one of the .jar files doesn't get created even though the target file is present. From what I can tell the command executes when the package is installed but for some reason the link isn't created. If I run the same command from the SPEC file manually it works as expected. I'm not sure if there is something environmentally that isn't working. I don't image we want to change the dynamic link creation (using classpath) to hard coded ln commands as that may cause the RPM and SPEC to be less portable.

Thoughts?

Tim
Comment 11 Fedora Update System 2017-03-04 21:47:27 UTC 
jenkins-1.651.3-5.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c4725ad473
Comment 12 Fedora Update System 2017-03-04 21:51:14 UTC 
jenkins-1.651.3-5.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2303ed6489
Comment 13 Fedora Update System 2017-03-05 21:50:06 UTC 
jenkins-1.651.3-5.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c4725ad473
Comment 14 Fedora Update System 2017-03-05 21:50:12 UTC 
jenkins-1.651.3-5.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-2303ed6489
Comment 15 Fedora Update System 2017-03-13 23:55:36 UTC 
jenkins-1.651.3-5.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Comment 16 Fedora Update System 2017-03-14 02:21:53 UTC 
jenkins-1.651.3-5.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.