Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. ygeelen-tb
    3. Posts

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Y Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 13
    • Posts 43
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: ProGet 5.1.x upgrade broke ProGet (SQL timeout)

      I'm directly executing the DashboardFeeds view, so I'm not using the parameter.

      It seems that the SUM([Package_Size] for [Feed_Size] and [Cache_Size] are the culprit.
      When I replace the query with [Feed_Size] = 0, [Cache_Size] = 0 then the timeouts are gone! They are just missing from the feed disk usage graph. Adding an index to NuGetPackageVersionsV2.Package_Size didn't help.

      The strange thing is that some pages that are not using the graph are also executing the DashboardInfo stored procedure.

      posted in Support
      Y
      ygeelen-tb
    • RE: ProGet 5.1.x upgrade broke ProGet (SQL timeout)

      I did some database cleanup (deleted old packages) and ran the Feed Cleanup tasks:
      NuGetPackageVersionsV2 2477
      NuGetPackagesV2 1266

      But the first query in view dbo.DashboardFeeds is still very slow (1 minute and 38 seconds), particularly the subqueries Feed_Size and Cache_Size:

      Feed_Id Feed_Name FeedType_Name Package_Download_Count Package_Count Feed_Size Cache_Size Active_Indicator
      1 nuget.org-proxy NuGet 3581 628 1371022356 1370053686 Y
      2 tobania NuGet 555 36 364376870 3685794 Y
      3 chocolatey-proxy Chocolatey 0 0 0 0 Y
      5 nuget.org-microsoft.net-proxy NuGet 3130 577 1053810421 1053810421 Y
      7 anton2 NuGet 4 7 102825284 0 Y
      9 powershell-tobania PowerShell 0 0 0 0 Y
      22 digipolis NuGet 186 16 8250831 0 Y
      23 febelfin-academy NuGet 69 2 238575 0 Y
      25 zorgplan-devexpress NuGet 0 0 0 0 Y

      Are those sizes exceptionally large?

      posted in Support
      Y
      ygeelen-tb
    • RE: ProGet 5.1.x upgrade broke ProGet (SQL timeout)

      Could you please improve the performance of the stored procedure and provide a new ProGet release to include this?

      posted in Support
      Y
      ygeelen-tb
    • RE: ProGet 5.1.x upgrade broke ProGet (SQL timeout)

      Hi Alana,

      After defragmenting the indexes and updating the statistics, we are still getting the timeout...

      Running the stored proc like this takes 1'45":

      EXEC @return_value = [dbo].[Dashboards_GetDashboardInfo]
      @Packages_Count = 10,
      @IncludeInactive_Indicator = Y

      Our database is really not spectacular looking at the row counts.
      Perhaps the nuget.org connector could be the culprit?

      TableName RowCount

      dbo.EventOccurrences 198648

      dbo.PackageDownloads 16878

      dbo.ScopedExecutionLogEntries 7100

      dbo.NuGetPackageVersionsV2 4950

      dbo.NuGetPackagesV2 2530

      dbo.LogMessages 2004

      dbo.DockerBlobs 1706

      dbo.LicenseUrls 1394

      dbo.Executions 1228

      dbo.NuGetPackageSymbolsV2 690

      dbo.Licenses 654

      dbo.ScopedExecutionLogs 614

      dbo.DockerImages 512

      dbo.__BuildMaster_DbSchemaChanges2 406

      dbo.__BuildMaster_DbSchemaChanges 328

      dbo.__StoredProcInfo 254

      dbo.DockerImageTags 143

      dbo.RoleTasks 38

      dbo.Tasks 32

      dbo.Feeds 32

      dbo.Privileges 27

      dbo.Configuration 27

      dbo.EventTypes 23

      dbo.ScheduledTasks 21

      dbo.Roles 18

      dbo.FeedConnectors 12

      dbo.Users 8

      dbo.UserGroups 7

      dbo.Connectors 6

      dbo.UserDirectories 4

      dbo.Groups 3

      dbo.AssessmentTypes 3

      dbo.VsixPackages 2

      dbo.Webhooks 1

      posted in Support
      Y
      ygeelen-tb
    • RE: ProGet 5.1.x upgrade broke ProGet (SQL timeout)

      I've narrowed down the issue a bit: the database connection is working on most pages of ProGet, except for the pages that make a call to the stored procedure dbo.Dashboards_GetDashboardInfo which causes the SQL timeout:

      • www.example.com/ (root url)
      • www.example.com/feeds (all feeds)
      • www.example.com/feeds/<containerregistryname> (Docker container registry)

      Increasing the command timeout of SQL Server didn't help.
      When I execute the stored procedure dbo.Dashboards_GetDashboardInfo manually then it gets really slow depending on how high value I pass to parameter @Packages_Count (I don't know which values is actually being passed by ProGet). When I pass for example 5000 then the query takes 2 minutes and 35 seconds to complete.

      posted in Support
      Y
      ygeelen-tb
    • RE: ProGet 5.1.x upgrade broke ProGet (SQL timeout)

      I already tried restarting SQL Server and also uninstalling ProGet and even with a clean installation (which checks the database connection) we're getting the timeout error.
      Other applications using other databases on the same SQL Server instance are still working fine.

      posted in Support
      Y
      ygeelen-tb
    • ProGet 5.1.x upgrade broke ProGet (SQL timeout)

      Suddenly our ProGet installation is getting SQL timeouts. I've seen that the configuration has been moved to a central configuration file: https://inedo.com/support/documentation/proget/reference/config-files

      The SQL connectionstring is still valid, but it seems the application is not reading the connectionstring from the shared config file?
      I tried putting ConnectionString and EncryptionKey inside Web_appSettings.config and App_appSettings.config but still get the same error.

      Don't I need a customconfiguration section declaration for "InedoAppConfig" inside Web.config and Proget.Service.exe.config ?

      Is anyone else experiencing this issue?

      Server Error in '/' Application.
      The wait operation timed out
      Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
      Exception Details: System.ComponentModel.Win32Exception: The wait operation timed out
      Source Error:
      An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
      Stack Trace:
      [Win32Exception (0x80004005): The wait operation timed out]
      [SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
      System.Data.SqlClient.<>c.<ExecuteDbDataReaderAsync>b__174_0(Task1 result) +1161090 System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke() +108
      System.Threading.Tasks.Task.Execute() +71
      System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
      System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
      Inedo.Data.<CreateAsync>d__10.MoveNext() +341
      System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
      System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
      Inedo.Data.<ExecuteInternalAsync>d__33.MoveNext() +1239
      System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
      System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
      Inedo.ProGet.Data.<Dashboards_GetDashboardInfoAsync>d__91.MoveNext() +731
      System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
      System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
      System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) +14139265
      Inedo.ProGet.WebApplication.Pages.<CreateChildControlsAsync>d__2.MoveNext() +411
      System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
      System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
      Inedo.ProGet.WebApplication.Pages.<InitializeAsync>d__1.MoveNext() +348
      System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
      System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
      Inedo.Web.PageFree.<ProcessRequestAsync>d__46.MoveNext() +283
      System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
      System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
      System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) +69
      Inedo.Web.Handlers.AsyncHandlerWrapper.EndProcessRequest(IAsyncResult result) +34
      System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +178
      Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1590.0

      Product: ProGet
      Version: 5.1.7

      posted in Support proget
      Y
      ygeelen-tb
    • Delete feed error

      I had to delete the standard Feed Cleanup scheduled task record before being able to delete a feed, because the following error was thrown during deletion:

      Deleting indexed feed metadata...
      Unhandled exception: System.Data.SqlClient.SqlException (0x80131904): 547160Feeds_DeleteFeed80The DELETE statement conflicted with the REFERENCE constraint "FK__Executions__ScheduledTasks". The conflict occurred in database "ProGet", table "dbo.Executions", column 'ScheduledTask_Id'. at System.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__174_0(Task1 result)
      at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
      at System.Threading.Tasks.Task.Execute()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Inedo.Data.DatabaseContext.DbResult.<CreateAsync>d__10.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Inedo.Data.DatabaseContext.<ExecuteInternalAsync>d__33.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Inedo.Data.DatabaseContext.<ExecuteNonQueryAsync>d__31.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Inedo.ProGet.Executions.DeleteFeedExecution.<ExecuteAsync>d__8.MoveNext()
      --- End of stack trace from previous location where exception was thrown ---
      at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at Inedo.ProGet.Service.Executions.ActiveManualExecution.<ExecuteAsync>d__7.MoveNext()
      ClientConnectionId:2985cac8-067e-4032-bc3f-26359cfc0e5e
      Error Number:50000,State:42,Class:16

      Product: ProGet
      Version: 5.0.7

      posted in Support feeds proget
      Y
      ygeelen-tb
    • RE: Composer/Packagist feeds

      Any news on this? Composer is used a lot in our company as well. It would be nice to share the same tools. :-)

      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      Lucas, no I was told (I think unofficially) in a support ticket. They will announce it when they'd decide to go for it.

      posted in Support
      Y
      ygeelen-tb
    • Docker pull ERROR: filesystem layer verification failed for digest

      Since today we are getting an error when attempting to pull some Docker images:
      ERROR: filesystem layer verification failed for digest

      The strang thing is that after doing many pulls, it succeeds and it also occurs for very old unchanged images. It seems to be random..

      The only thing that changed is that we granted user Anonymous the View & Download permissions. However, undoing this change doesn't solve the issue.

      Product: ProGet
      Version: 4.7.13

      posted in Support proget
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      Thank you for your effort. Telerik is working on a long-term solution I understood.

      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      I already did and pointed them to this support question. Their reply: "We will log your feedback in our backlog and consider it when planning our future releases."

      We get different errors now (500 instead of 404) during npm install:

      npm ERR! fetch failed https://packages.tobania.be:443/npm/npm-telerik-proxy/@progress/kendo-data-query/-/kendo-data-query-0.5.2.tgz
      npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 500
      npm ERR! fetch failed https://packages.tobania.be:443/npm/npm-telerik-proxy/@progress/kendo-theme-default/-/kendo-theme-default-2.31.3.tgz
      npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 500

      I'll let Telerik know.

      PG-1019 doesn't seem to be solved:

      Getting metadata from https://registry.npm.telerik.com/-/all
      Finished downloading metadata. Indexing packages...
      Error indexing @progress/kendo-angular-buttons: "modified" property on "time" is missing or invalid.

      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      Current situation:

      • connector URL is https://registry.npm.telerik.com/ (before it was https://registry.npm.telerik.com/-/all)
      • connector shows "Error"
      • feed shows no error but no packages (before it was showing a "(404) Not Found" error)
      • npm install shows errors (the paths seem to be invalid (404) or the tgz files are missing):
        npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-data-query/-/kendo-data-query-0.5.1.tgz
        => the path https://packages.tobania.be/npm/npm-telerik-proxy/@progress/kendo-data-query/ seems to produce some JSON content though that contains relatively built URL's like the tgz file URL above
      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      Thanks, but will that solve the npm fetch error as well?
      The paths seem to be unexisting:
      /@progress/kendo-data-query/-/kendo-data-query-0.5.1.tgz

      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      We got rid of the error above by modifying the connector url by removing the trailing "/-/all". Now the feed indexing task succeeds, and npm install throws this error:

      npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-data-query/-/kendo-data-query-0.5.1.tgz
      npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
      npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-l10n/-/kendo-angular-l10n-0.3.0.tgz
      npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
      npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-dialog/-/kendo-angular-dialog-0.19.0.tgz
      npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
      npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-popup/-/kendo-angular-popup-0.17.0.tgz
      npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
      npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-upload/-/kendo-angular-upload-0.20.0.tgz
      npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
      npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-intl/-/kendo-angular-intl-0.12.0.tgz
      npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404
      npm ERR! fetch failed https://packages.xxx.be:443/npm/npm-telerik-proxy/@progress/kendo-angular-buttons/-/kendo-angular-buttons-0.24.0.tgz

      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      The connector is showing " Error (as of 13:10)" now though and npm install throws this error:

      npm ERR! 404 Package not found. Package was not found.: npm
      npm ERR! 404
      npm ERR! 404 'npm' is not in the npm registry.
      npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
      npm ERR! 404 It was specified as a dependency of 'xxx'
      npm ERR! 404
      npm ERR! 404 Note that you can also install from a
      npm ERR! 404 tarball, folder, http url, or git url.

      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      I just upgraded to ProGet 4.7.10 which includes following items:
      PG-1012 - Support for NPM feeds that authenticate via email address
      PG-1013 - Support for NPM connectors that don't provide the search API

      It seems that the error when viewing the feed is gone (so authentication seems to work). The packages are still not listed, although I'm not sure if that's supposed to be the case?
      What exactly does PG-1013 solve?

      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      Thanks a lot! I will report the NPM search API issue to Telerik.

      posted in Support
      Y
      ygeelen-tb
    • RE: Unable to connect to Telerik

      We also tried configuring an NPM connector for https://registry.npm.telerik.com/ including the correct credentials, but when accessing the feed we get the following error:
      The remote server returned an error: (404) Not Found.
      When leaving the credentials empty we get the same error.

      About scoping: I think the connector just requires an input field to define the scope like this: npm login --registry=https://registry.npm.telerik.com/ --scope=@progress

      See also https://docs.npmjs.com/misc/scope "You can associate a scope with a registry at login"

      posted in Support
      Y
      ygeelen-tb
    • 1 / 1