Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-480

Debian package repository: Connection refused

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: administrative
    • Labels:
      None
    • Environment:
      Linux (Debian Stretch)
    • Similar Issues:

      Description

      Currently apt-get dist-upgrade fails with following error:

      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      Calculating upgrade... Done
      The following packages will be upgraded:
         jenkins (2.107.1 => 2.107.2)
      1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      Need to get 73.9 MB of archives.
      After this operation, 43.0 kB of additional disk space will be used.
      Do you want to continue? [Y/n]
      Err:1 https://pkg.jenkins.io/debian-stable binary/ jenkins 2.107.2
        FailReason: ConnectionRefused
      E: Failed to fetch https://prodjenkinsreleases.blob.core.windows.net/debian-stable/jenkins_2.107.2_all.deb  FailReason: ConnectionRefused
      E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

        Attachments

          Activity

          Hide
          ogmueller Oliver Mueller added a comment -

          The bug seems to have reepeared:

           

           

          The following packages will be upgraded: 
            jenkins 
          1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
          Need to get 65.8 MB of archives. After unpacking 50.2 kB will be used.
          Err https://pkg.jenkins.io/debian binary/ jenkins 2.240                    
            404  The specified blob does not exist. [IP: 52.167.88.112 443]
          0% [Working]E: Failed to fetch https://prodjenkinsreleases.blob.core.windows.net/debian/jenkins_2.240_all.deb: 404  The specified blob does not exist. [IP: 52.167.88.112 443]
          E: Unable to fetch some packages; try '-o APT::Get::Fix-Missing=true' to continue with missing packages
          

           

          Show
          ogmueller Oliver Mueller added a comment - The bug seems to have reepeared:     The following packages will be upgraded:    jenkins  1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 65.8 MB of archives. After unpacking 50.2 kB will be used. Err https: //pkg.jenkins.io/debian binary/ jenkins 2.240                       404  The specified blob does not exist. [IP: 52.167.88.112 443] 0% [Working]E: Failed to fetch https: //prodjenkinsreleases.blob.core.windows.net/debian/jenkins_2.240_all.deb: 404  The specified blob does not exist. [IP: 52.167.88.112 443] E: Unable to fetch some packages; try '-o APT::Get::Fix-Missing= true ' to continue with missing packages  
          Hide
          dhs Dirk Heinrichs added a comment -

          "... blob does not exist" != "Connection refused", isn't it?

          Show
          dhs Dirk Heinrichs added a comment - "... blob does not exist" != "Connection refused", isn't it?
          Hide
          ogmueller Oliver Mueller added a comment -

          That is correct.

          Show
          ogmueller Oliver Mueller added a comment - That is correct.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            dhs Dirk Heinrichs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: