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!
ProGet crashing
-
Hello.
I have a problem with ProGet crashing consistently while accessing the one and only nuget feed.
The server is a win2012R2. I use the bundled webserver and db.
The only help I have found is in three errors in the event log:Any help is much appreciated. ProGet is not usable for me as it is now.
Thanks
NiklasFirst one (ASP.NET):
An unhandled exception occurred and the process was terminated. Application ID: ProGet.Service.exe Process ID: 4476 Exception: System.InvalidOperationException Message: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. StackTrace: at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.Open() at Inedo.Data.SqlServerDataFactory.CreateConnection() at Inedo.Data.SqlServerDataFactory.CreateCommand(String storedProcName, IEnumerable`1 parameters) at Inedo.Data.SqlServerDataFactory.ExecuteDataSet(String storedProcName, String[] tableNames, IList`1 parameters) at Inedo.ProGet.Data.StoredProcedures.Feeds_BeginSync.Execute() at Inedo.ProGet.Service.MyGetSyncExecuter.Execute() at Inedo.TimedExecuterBase.ExecuteMethodHost(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.TimerQueueTimer.CallCallback() at System.Threading.TimerQueueTimer.Fire() at System.Threading.TimerQueue.FireNextTimers()
The second (.NET runtime):
Application: ProGet.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
at Inedo.TimedExecuterBase.ExecuteMethodHost(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()The third:
Faulting application name: ProGet.Service.exe, version: 3.5.3.24, time stamp: 0x54ee4bfd
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xe0434352
Fault offset: 0x0000000000008b9c
Faulting process id: 0x128c
Faulting application start time: 0x01d08e891d668657
Faulting application path: C:\Program Files\ProGet\Service\ProGet.Service.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 881602a1-fa7c-11e4-80d6-00505685765d
Faulting package full name:
Faulting package-relative application ID:Product: ProGet
Version: 3.5.3
-
It should be "the one and only npm feed" above. Sorry.
-
I might also add that the feed is working for a while. It's crashing every 5 minutes or so if used.
-
Based on the symptom, this issue was resolved in 3.5.4 as PG-356 - FIX: SQL connections for some stored procedure calls are sometimes leaked.
-
I can't believe I missed that.
I upgraded and that problem is gone but with new issues. Will open a separate question for that problem.Suggestion: How about adding a new tag npm?
Thanks
Niklas