Hi

We are running ProGet (2.5.30 build 4) in docker on a Linux host, with another container for MSSQL. Our current default feed directed for Nuget often (once a week:ish) get very slow and if you view it in the web interface you will get an error on top.
"There was an error with a connector: The operation has timed out."

And in admin UI we can see:

Request URL: https://nuget.org/api/v2/Search()?$top=25&$filter=IsAbsoluteLatestVersion&searchTerm=%27%27&targetFramework=%27%27&includePrerelease=true&semVerLevel=2.0.0

System.Net.WebException: The operation has timed out.
at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <4d8f95b7df544b3fa1a27dda924b4424>:0
at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <4d8f95b7df544b3fa1a27dda924b4424>:0
at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <c453bf849bb84e719dbec0475e99db95>:0
--- End of stack trace from previous location where exception was thrown ---

at Inedo.ProGet.Feeds.StrongConnector.GetDirectResponseAsync (System.String url) [0x000eb] in <dacb7de90ce24964b2da21b67ac5e1d1>:0
at Inedo.ProGet.Feeds.StrongConnector.GetCachedResponseAsync (System.String url) [0x000a8] in <dacb7de90ce24964b2da21b67ac5e1d1>:0
at Inedo.ProGet.Feeds.StrongConnector.GetCachedTextReaderAsync (System.String url) [0x00075] in <dacb7de90ce24964b2da21b67ac5e1d1>:0
at Inedo.ProGet.Feeds.NuGet.NuGetFeedClient.PerformRequestWithAbsoluteUrlAsync (System.String fullUrl) [0x000d9] in <dacb7de90ce24964b2da21b67ac5e1d1>:0

Actual host and container show very little activity and we can curl the requested URL both from the docker host and from within the container without delays.
And once it has started to behave like this, it will not get better until we restart the container.
We currently restart our container once a day due to a potential memory leak described in another issue.

--Magnus

Thanks for the answer!

@atripp said in ProGet in docker/linux hanging after using all memory:

Hello; we haven't had any other users report this, so I'm afraid I don't have any idea how to help. It certainly sounds like a memory leak, and it'st most definitely a mono-specific bug; unfortunately these are extremely hard to track down, and sometimes are even platform specific (i.e. depending on host operating system).

I would make sure to upgrade to latest version of container image.

If you're not already using SQL Server for Linux (and you're using Postgres), then switch to SQL Server.

We use SQL Server.

I would simplify configuration; if you have a lot of connectors, etc.

We have 3 feeds and 2 connectors.

Try putting a ngix proxy infront of it.

We have that! =).

Once we have a clue about where the mono-bug is, we can at least consider ways to work-around it.

Yes. Maybe someone else have clues or have seen something similar. Most "linux container progets" run mono.exe right?

BR

Hello.

We run proget in a container on linux. We experience that the proget container consumes more and more memory (looking at the mono.exe process it runs) and then finally freezes once all memory on host machine is consumed. Only solution then is to restart the container (not the DB container, which is running fine). We have a 8GB host linux machine. Almost all of that memory is consumed by the proget container.
It really does seem like a memory leak. We are currently, using crontab, restarting the container every day as a workaround.

Do you have any idea what could be causing this and how we can proceed in troubleshooting it?