Details

    • Type: Bug
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: NuGet
    • Labels:
      None

      Description

      After version upgrade from 6.11.3 to 6.12.2 and then 6.13.1 we are faced with the issue:

      Time to time (like 3 times from 10) a job was failed when trying to find Nuget package from a Virtual or Remote Nuget repository. This issue accompanied by errors:

      16:17:00 Errors in packages.config projects
      16:17:00 Unable to find version '1.0.29' of package 'xxxxx'.
      16:17:00 https://api.nuget.org/v3/index.json: Package 'xxx.1.0.29' is not found on source 'https://api.nuget.org/v3/index.json'.
      16:17:00 https://xxxx: Failed to fetch results from V2 feed at 'xxxxxxxx(Id='core.sbtech',Version='1.0.29')' with following message : An error occurred while sending the request.
      16:17:00 An error occurred while sending the request.
      16:17:00 Unable to connect to the remote server
      16:17:00 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx:443
      16:17:00 https://xxxx: Failed to fetch results from V2 feed at 'xxxxx(Id='xxxx',Version='1.0.29')' with following message : An error occurred while sending the request.
      16:17:00 An error occurred while sending the request.
      16:17:00 Unable to connect to the remote server
      16:17:00 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx:443
      
      "The HTTP request to 'GET xxxx/api/nuget/nuget.org/FindPackagesById()?id='Serilog'&semVerLevel=2.0.0' has timed out after 100000ms."
      

      Sensitive info was hidden by the xxxx

      When we tried to "wget" the last URL we have found it takes to much time to respond. Like a few minutes. But the next respond to the same URL was very quick.

      In periods of time when the errors have happened, there are weren't any lack of system resources at all.

      What we have tried:

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              riser Ruslan Ponimarenko
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: