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

Plugin Manager does not update information (and seems like dont even run the updater)

    Details

    • Similar Issues:

      Description

      The process of checking for the plugins updates information doesnt ever completes(or even starts).

          When clicking the "Check now" button i get never-ending  "Checking Updates..." message. 
          I have enabled logging for hudson.model.UpdateSite:ALL,  hudson.model.UpdateCenter: ALL but the log screen is empty. So i even doesnt have any logs to present.

        Attachments

        1. afterAwhile.txt.zip
          5 kB
        2. GET-request.txt.zip
          234 kB
        3. postBack.txt.zip
          258 kB
        4. rightAfterButtonClick.txt.zip
          5 kB

          Activity

          Hide
          y0sh1 Dmitry Esarev added a comment - - edited

          GET-request.txt.zip postBack.txt.zip

          yes, actually there is an postback error when sniffering through dev console:

          1. On GET request https://updates.jenkins-ci.org/current/update-center.json.html?id=default&version=2.53
          The headers are:

          Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
          Accept-Encoding:gzip, deflate, sdch, br
          Accept-Language:en-US,en;q=0.8,ru;q=0.6,zh;q=0.4
          Connection:keep-alive
          Host:updates.jenkins-ci.org
          If-Modified-Since:Fri, 14 Apr 2017 05:32:56 GMT
          If-None-Match:"117316-54d19c619320f-gzip"
          Referer:http://jenkins.vm.mycorp.local/pluginManager/checkUpdates
          Upgrade-Insecure-Requests:1
          User-Agent:Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
          

          And the whole request body file-attached as : GET-request.txt.zip (it has json pretty-formatted for readability)

          2. And then i'v got a respone with Status Code:413 Request Entity Too Large.
          And the whole response body file-attached as postBack.txt.zip (it has json pretty-formatted for readability)

          Show
          y0sh1 Dmitry Esarev added a comment - - edited GET-request.txt.zip postBack.txt.zip yes, actually there is an postback error when sniffering through dev console: 1. On GET request https://updates.jenkins-ci.org/current/update-center.json.html?id=default&version=2.53 The headers are: Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8 Accept-Encoding:gzip, deflate, sdch, br Accept-Language:en-US,en;q=0.8,ru;q=0.6,zh;q=0.4 Connection:keep-alive Host:updates.jenkins-ci.org If-Modified-Since:Fri, 14 Apr 2017 05:32:56 GMT If-None-Match: "117316-54d19c619320f-gzip" Referer:http: //jenkins.vm.mycorp.local/pluginManager/checkUpdates Upgrade-Insecure-Requests:1 User-Agent:Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 And the whole request body file-attached as : GET-request.txt.zip (it has json pretty-formatted for readability) 2. And then i'v got a respone with Status Code:413 Request Entity Too Large. And the whole response body file-attached as postBack.txt.zip (it has json pretty-formatted for readability)
          Hide
          y0sh1 Dmitry Esarev added a comment - - edited

          Thank you for the tips. I have it fixed by configuring client_max_body_size of the nginx:

          # vi /etc/nginx/sites-enabled/jenkins
          server {
              client_max_body_size 10m;
          ...
          
          # service nginx restart
          

          this parameter is also documented here https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Nginx

          Show
          y0sh1 Dmitry Esarev added a comment - - edited Thank you for the tips. I have it fixed by configuring client_max_body_size of the nginx: # vi /etc/nginx/sites-enabled/jenkins server { client_max_body_size 10m; ... # service nginx restart this parameter is also documented here https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Nginx
          Hide
          danielbeck Daniel Beck added a comment -

          The browser-based metadata download has been deprecated as being unsafe and unreliable years ago. There should have been an admin monitor warnings against its use. Seems you dismissed it?

          Show
          danielbeck Daniel Beck added a comment - The browser-based metadata download has been deprecated as being unsafe and unreliable years ago. There should have been an admin monitor warnings against its use. Seems you dismissed it?
          Hide
          y0sh1 Dmitry Esarev added a comment -

          i actually dont remember. it is possible i somehow mute it. And now what should i do?

          Show
          y0sh1 Dmitry Esarev added a comment - i actually dont remember. it is possible i somehow mute it. And now what should i do?
          Hide
          danielbeck Daniel Beck added a comment -

          Well, you worked around it. Nothing I suppose? But you can still disable the option in the security configuration.

          Show
          danielbeck Daniel Beck added a comment - Well, you worked around it. Nothing I suppose? But you can still disable the option in the security configuration.

            People

            • Assignee:
              Unassigned
              Reporter:
              y0sh1 Dmitry Esarev
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: