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

Jenkins does not start after upgrading from Hudson

          Details

          • Type: Bug
          • Status: Resolved
          • Priority: Major
          • Resolution: Fixed
          • Component/s: core
          • Labels:
            None
          • Environment:
            1.397

            Description

            After upgrading from Hudson to Jenkins 1.397 with Tomcat 6.0.26 running on Red Hat Enterprise Linux Server release 5.5, Jenkins failed to start. The browser was stuck with the message:

            Please wait while Jenkins is getting ready to work....

            The tomcat log had the message:

            Feb 15, 2011 11:49:41 AM javax.jmdns.impl.HostInfo newHostInfo
            WARNING: Could not find any address beside the loopback.

            The only interfaced configured in /etc/hosts is:

            ::1 localhost.localdomain localhost hostx

            Looking at JmDNS, you can define the system property net.mdns.interface for JmDNS, I added the following system propery to my tomcat startup file and Jenkins successfully started:

            -Dnet.mdns.interface=0.0.0.0

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              robnielsen Rob Nielsen added a comment -

              Somebody else resolved the problem with an updated JmDNS:

              We solved it by updating the JmDNS lib to the latest version (3.4.0)
              (download: http://sourceforge.net/projects/jmdns/files/jmdns/).
              Jenkins comes with 3.2.1 which caused a livelock on initialization.

              Show
              robnielsen Rob Nielsen added a comment - Somebody else resolved the problem with an updated JmDNS: We solved it by updating the JmDNS lib to the latest version (3.4.0) (download: http://sourceforge.net/projects/jmdns/files/jmdns/ ). Jenkins comes with 3.2.1 which caused a livelock on initialization.
              Hide
              Permalink
              dougborg Doug Borg added a comment -

              Thanks Rob, that worked for me as well.

              It took me a while to figure out that the jar for jmdns is in the lib folder of the archive you can download from the link you posted. I just opened the jenkins.war or hudson.war and replaced the stock jmdns.jar in the WEB-INF/lib folder and then redeployed.

              Hope this saves someone else a few minutes.

              Show
              dougborg Doug Borg added a comment - Thanks Rob, that worked for me as well. It took me a while to figure out that the jar for jmdns is in the lib folder of the archive you can download from the link you posted. I just opened the jenkins.war or hudson.war and replaced the stock jmdns .jar in the WEB-INF/lib folder and then redeployed. Hope this saves someone else a few minutes.
              Hide
              Permalink
              evernat evernat added a comment -

              It seems to me that Jenkins currently uses "jmdns-3.4.0-jenkins-3.jar".
              So this should be fixed.

              Show
              evernat evernat added a comment - It seems to me that Jenkins currently uses "jmdns-3.4.0-jenkins-3.jar". So this should be fixed.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  robnielsen Rob Nielsen
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: