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!
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool
-
Hello; this is a sign of network connectivity being overloaded.
Ultimately your best bet is to use load balancing; see How to Prevent Server Overload in ProGet to learn more.
But I've heard that putting a NGIX reverse proxy in-front of the Linux container helps (due to some poor network handling/bugs by Mono's code) or moving to the Windows/IIS stack.
-
@atripp
Hi,
Do you have any links to people using nginx reverse-proxy setups?
We did have it running on Windows, but moved it to docker to simplify upgrades - i.e. less downtime.Are there any plans in future for proget to become a native .net standard application and therefore not require mono?
-
We don't document how to set-up the ngix proxy, but it's a fairly common setup, and the way to support HTTPS on Linux.
Yes, our plan is to move to .NET5 as Microsoft comes closer to releasing that and it's proven stable (likely next year).
-
@atripp Good to know that netcore is in the pipeline.
Regarding using nginx, not exactly sure how this would help with Mono's network handling.
I have the containerised instance in AWS, and SSL offloading is being handled by an Elastic Load Balancer.
If I have nginx between the ELB and the proget container, surely it is just going to pass the connections straight through, unless it is configured to cache as well? -
@abm_4780 said in Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool:
Regarding using nginx, not exactly sure how this would help with Mono's network handling.
I really don't remember the details, it was a while ago; it had something to do with keep-alive connections, perhaps? It made no sense, at all, but ngix fixed it. Later on, mono fixed whatever bug caused it.
-
@atripp
I shall try putting a proxy in front of it in due course."Later on, mono fixed whatever bug caused it."
Do you plan to release a version with the fixed mono libraries anytime soon?
Either way, thanks for your help so far.
-
The ProGet Dockerfile is based on
mono, which is the latest stable version; so, every maintenance release it's whatever the latest version is at the time. -
We are experiencing the same issue @abm_4780 has experienced. We have the Proget container behind an AWS application load balancer and see the timeouts when one teamcity build agent(4vCPU and 8GB) requests the nuget packages. @abm_4780, did putting the container behind nginx solve your issue? Also worth noting that this looks like Proget is using all pooled data connections, and increasing max pool size does not seem to have an impact. Moving to Microsoft IIS stack did solve the problem but we were trying to avoid using a Windows server.
Thanks,
Adam -
@wsah_6160 I have tried putting it behind nginx but the issue is still the same. For me, only one build agent with one build job overwhelms proget...
-
@wsah_6160 @pluskal_4199 assuming this is related to 5.3, then there should be a fix coming soon!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login