Thanks for confirmation, but we've a limit of 5000 concurrent requests on proget server

We only enabled v3 at feed level actully

And we didn't enable metadata caching, should we enable this to avoid these issues?

Hi Team

We've a question on nuget api calls blocking proget.

We've been facing issue while connecting to proget recently, after some investigation with our IS team they have provided below info.

Looking at one of the failures from this morning, we can see that ProGet served no requests while it was busy establishing >200 outgoing connections

For the above time (09:15 AEST), it was 23.46.10.74 and 23.46.10.19, which according to the DNS audit logs is api.nuget.org.

SQL server seems healthy. But perhaps ProGet holds a table lock for longer than we want it to. A client successfully holding a lock isn't a "problem" from the perspective of MSSQL itself.

Is there any possibility that api calls to nuget is blocking proget servers?

Proget version we're using: Version 2025.15 (Build 9)

If possible we would like to know what calls are being send to nuget to analyze the requests being made.

Thanks
Parthu

Hi Team

Any idea why we're getting this error.

Thanks
Parthu

Hi Team

We've few dump files(different times) that were created ruing proget restart. I don't see much issue in proget except for the sql error which caused proget restart.

This is continuation for below topic. Not able to attach them here. Is there any way we can send it to you so that you can check what could be the reason for these repeated restarts.

https://forums.inedo.com/topic/5662/http-logs-enabled-on-only-one-server/8

JFI - now after removal of Debian feed and connectors this issue is not occuring.

Thanks
Parthu

Hi @rhessinger

Recently we enabled Debian and added ubuntu connectors to it. Since then we had lot of exceptions for it.

And then server used to get stuck many times without responding.

We assume it could be because of this. And deleted all 4 connectors that we added.

Not it looks fine.

When we checked event logs we found above error. This happened for 2 days after these connectors are added. Today we didn't get this error after deleting all the connectors related to ubuntu. Let us know if this is an issue from proget.

Thanks
Parthu

Hi Team

We've removed debian feed due to some issue, but it's local index files are not deleted. What can be done for these files to be removed.

Thanks
Parthu

@rhessinger said in Http Logs enabled on only one server:

SQL Server

Hi @rhessinger

We're using SQL Server

Thanks

@rhessinger said in Http Logs enabled on only one server:

ude how to enable this when using a Load Balanced/HA configuration. I have also added a ticket, PG-3211, to update the UI to give guidance on this configuration.

Thanks for the info @rhessinger , can I also know details about the exception

Hi Team

We enabled http logs but it's only enabled on only one server. For other 2 servers in the cluster logs aren't enabled. How can I enable on all 3 servers

And I've another question, can I know when we'll get this exception.

Application: ProGet.Service.exe
CoreCLR Version: 8.0.2225.52707
.NET Version: 8.0.22
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AggregateException: One or more errors occurred. (One or more errors occurred. (The CancellationTokenSource has been disposed.))
---> System.AggregateException: One or more errors occurred. (The CancellationTokenSource has been disposed.)
---> System.ObjectDisposedException: The CancellationTokenSource has been disposed.
at System.Threading.CancellationTokenSource.get_Token()
at Inedo.ProGet.Messaging.DatabaseMessageQueue.<>c__DisplayClass10_0.<BroadcastMessageWithResponsesAsync>g__cancelTasks|1()
at System.Threading.CancellationTokenSource.Invoke(Delegate d, Object state, CancellationTokenSource source)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.CancellationTokenSource.ExecuteCallbackHandlers(Boolean throwOnFirstException)
--- End of inner exception stack trace ---
at System.Threading.CancellationTokenSource.ExecuteCallbackHandlers(Boolean throwOnFirstException)
at System.Threading.CancellationTokenSource.Invoke(Delegate d, Object state, CancellationTokenSource source)
at System.Threading.CancellationTokenSource.ExecuteCallbackHandlers(Boolean throwOnFirstException)
--- End of inner exception stack trace ---
at System.Threading.CancellationTokenSource.ExecuteCallbackHandlers(Boolean throwOnFirstException)
at System.Threading.TimerQueueTimer.Fire(Boolean isThreadPool)
at System.Threading.TimerQueue.FireNextTimers()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

Thanks
Parthu

Hi Team

Timout while searching in powershell gallery

It's working after we pull package locally

Thanks
Parthu