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

Updatecenter doesn't get update informations about plugins. No logging of any kind

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core

      Updatecenter doesn't get update informations about plugins. No logging of any kind.

      Tests:
      Opening up the extended settings and test connection: success.
      We tested this URLs:
      https://updates.jenkins.io/update-center.json
      http://updates.jenkins-ci.org/update-center.json
      Both succeded.

      Now we try to update the "Updates" list:
      /pluginManager/checkUpdates
      It shows: Checking Updates... Go back to update center

      While we wait we checked

      • tcpdump: no traffic to / from the proxy. checked both in the docker container, on the host machine.
      • proxyserver: nothing logged
      • logger: nothing not even a try

      What happens when we choose an available Plugin that isn't installed yet
      Tag it, snag it, bag it. Works like a charm

      • tcpdump: happy talking through the proxy with the internet
      • proxyserver: nothing logged
      • logger: We see the entries stating what plugin was installed

      Help.... Ideas needed.
      How can I get more log information? The Defaultlogs doesn't output anything.

      Last time this worked was around version 2.86.
      I did not find an actual issue here.
      Issue JENKINS-45235 isn't a match here, because ther is absolutly no traffic going out.

       

      Kind Regards
      AUsername

          [JENKINS-49400] Updatecenter doesn't get update informations about plugins. No logging of any kind

          User Name added a comment - - edited

          Workaround without using the updatecenter

          wget -O default.js http://updates.jenkins-ci.org/update-center.json
sed '1d;$d' default.js > default.json
cp default.json /opt/jenkins/updates/
chown -R jenkins:jenkins /opt/jenkins/updates

          After jenkins restart and waiting a while, jenkins picked up the ne default.js
          Updating the plugins within the gui wasn't a problem.

          However, using the updatecenter function to gather a new json, still silently fails. Without any notice / log.

          User Name added a comment - - edited Workaround without using the updatecenter wget -O default.js http://updates.jenkins-ci.org/update-center.json sed '1d;$d' default.js > default.json cp default.json /opt/jenkins/updates/ chown -R jenkins:jenkins /opt/jenkins/updates After jenkins restart and waiting a while, jenkins picked up the ne default.js Updating the plugins within the gui wasn't a problem. However, using the updatecenter function to gather a new json, still silently fails. Without any notice / log.

          John Tal added a comment - - edited

          This started happening to us coincident to moving to Jenkins LTS 2.319.3 in February of this year.   I've tried all sort of things to no avail.  Since we build our own docker image from the LTS war, and issue occurs within the container, not the host vm, I didn't think it's a Jenkins nor a reverse proxy issue.  Still trying to track down root cause.   

          A clue is that curl to http connections returns 301 to the https side.

          A curl to the https side does not complete.

          This is not an uncommon issue and once a solution is found please update the Jenkins documentation to point to the solution. 

          *https://stackoverflow.com/questions/60819122/docker-jenkins-container-cant-access-internet*
          *https://github.com/jenkinsci/docker/issues/808*

           

          For us the clue was that MTU for the VM and MTU for docker network was set to the same value.  We made docker network less than VM eth0/eth1 by taking those devices from non-standard MTU=1430 to standard MTU=1500 (docker network left at MTU=1430).   With that change our ability to get to the update center is solved.

          John Tal added a comment - - edited This started happening to us coincident to moving to Jenkins LTS 2.319.3 in February of this year.   I've tried all sort of things to no avail.  Since we build our own docker image from the LTS war, and issue occurs within the container, not the host vm, I didn't think it's a Jenkins nor a reverse proxy issue.  Still trying to track down root cause.    A clue is that curl to http connections returns 301 to the https side. A curl to the https side does not complete. This is not an uncommon issue and once a solution is found please update the Jenkins documentation to point to the solution.  * https://stackoverflow.com/questions/60819122/docker-jenkins-container-cant-access-internet* * https://github.com/jenkinsci/docker/issues/808*   For us the clue was that MTU for the VM and MTU for docker network was set to the same value.  We made docker network less than VM eth0/eth1 by taking those devices from non-standard MTU=1430 to standard MTU=1500 (docker network left at MTU=1430).   With that change our ability to get to the update center is solved.

            Unassigned Unassigned
            ausername User Name
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: