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

Configure System hangs with "LOADING" gray div covering top half of settings

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • other
    • None

      I am setting up Jenkins for the first time. I've successfully gone into the configure system screen before, because I was able to set up matrix user permissions as outlined in the Standard Security guide. I wanted to add an environment variable to set the time, but now I'm unable, because the page load never completes. I'm new to java, but happy to troubleshoot and try things if you tell me what logs to look at. This is NOT running under TomCat.

          [JENKINS-9494] Configure System hangs with "LOADING" gray div covering top half of settings

          Dumbo Junior added a comment -

          Just like Daniel this problem appeared out of the blue after an update but given the initial issue was created in 2011 this looks like a regression.

          Dumbo Junior added a comment - Just like Daniel this problem appeared out of the blue after an update but given the initial issue was created in 2011 this looks like a regression.

          Daniel Haskin added a comment -

          I should also note that if I install jenkins 1.528 fresh, I do not have this problem. It only happens on our production server (d'oh!). The main differences between our production server and our fresh one is that one has lots of plugins installed and jobs defined, and one does not. I suspect this is a conflict with a plugin.

          Daniel Haskin added a comment - I should also note that if I install jenkins 1.528 fresh, I do not have this problem. It only happens on our production server (d'oh!). The main differences between our production server and our fresh one is that one has lots of plugins installed and jobs defined, and one does not. I suspect this is a conflict with a plugin.

          Dumbo Junior added a comment -

          Because a saw 2 times some ssh publishing stuff displayed on the screen it tried to disable the ssh publishing plugin after a restart I can edit configuration again.

          Dumbo Junior added a comment - Because a saw 2 times some ssh publishing stuff displayed on the screen it tried to disable the ssh publishing plugin after a restart I can edit configuration again.

          omid kashefi added a comment -

          I'm using 1.528,I simply disabled "Publish Over SSH Plugin" and everything works fine , now.

          omid kashefi added a comment - I'm using 1.528,I simply disabled "Publish Over SSH Plugin" and everything works fine , now.

          Halim Ansari added a comment -

          For me everything worked fine until I upgraded from 1.524 to 1.528. Then I read this post and discovered that something is wrong with 1.528 so i downgraded back to 1.524 and everything started working fine again.
          Seems some bug got introduced in 1.528. Need a fix.

          Halim Ansari added a comment - For me everything worked fine until I upgraded from 1.524 to 1.528. Then I read this post and discovered that something is wrong with 1.528 so i downgraded back to 1.524 and everything started working fine again. Seems some bug got introduced in 1.528. Need a fix.

          Björn Pedersen added a comment - https://issues.jenkins-ci.org/browse/JENKINS-19248

          In my case it was also "Publish Over SSH Plugin" plugin.
          I uninstall that and everything worked well.

          Tommi Lindeman added a comment - In my case it was also "Publish Over SSH Plugin" plugin. I uninstall that and everything worked well.

          Mat Gomes added a comment -

          https://issues.jenkins-ci.org/browse/JENKINS-19562
          Disabled "Publish Over SSH Plugin" fixed the issue.
          Yet we still require the plugin.

          Mat Gomes added a comment - https://issues.jenkins-ci.org/browse/JENKINS-19562 Disabled "Publish Over SSH Plugin" fixed the issue. Yet we still require the plugin.

          Jesse Glick added a comment -

          Believed to have been resolved with the fix in JENKINS-19457.

          Jesse Glick added a comment - Believed to have been resolved with the fix in JENKINS-19457 .

          We solved this by touching the jenkins war file, to restart/recreate internal server directories (I guess).

          We got this problem when moving an installation between machines. We figured it out when some of the javascripts could not be found. Looking at the webconsole (firefox) and the network we found that bind.js got a 404. The request was: /adjuncts/61a88662/org/kohsuke/stapler/bind.js. Touching the war-file and thus restarting jenkins another directory (simular to 61a88662) was used and then all started working.

          Mattias Persson added a comment - We solved this by touching the jenkins war file, to restart/recreate internal server directories (I guess). We got this problem when moving an installation between machines. We figured it out when some of the javascripts could not be found. Looking at the webconsole (firefox) and the network we found that bind.js got a 404. The request was: /adjuncts/61a88662/org/kohsuke/stapler/bind.js. Touching the war-file and thus restarting jenkins another directory (simular to 61a88662) was used and then all started working.

            Unassigned Unassigned
            jay_levitt Jay Levitt
            Votes:
            14 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated:
              Resolved: