I removed the backup to dropbox plugin and added all others and now it rebuilded without any error.
In that case, @Falco might want to have a look at the dropbox plugin.
2 Likes
-
If you get rate-limited by rubygems, you need to talk to rubygems. They explain how in their rate-limiting documentation. We can do absolutely nothing to help with rate-limiting problems. (This doesnāt just apply to the OP; everyone giving advice on this problem any time it occurs needs to refer people to rubygems, loudly, explicitly, and using words of no more than two syllables.)
-
I canāt see any specific error messages relating to the dropbox plugin in this thread. Without a complete error message and backtrace (if displayed in the logs), @Falco isnāt going to be able to do anything to fix whatever error might be going wrong.
5 Likes
It doesnāt make sense to me why in such situations we need to talk to rubygems. We are installing/Updating something that passes their thresholds. So I think their response would simply be for us to check the plugins we are trying to install. Am I right?
1 Like
Thatās what I think too, but this has been coming up lately, and Iām using a host Iāve used for a while and have not had problems previously.
Their site says:
Is it possible that the bootstrap script is doing that as a matter of course? Hereās an excerpt from a build just now:
HTTP GET https://index.rubygems.org/info/aws-sdk-cloudwatchlogs
HTTP 200 OK https://index.rubygems.org/info/aws-sdk-cloudsearchdomain
HTTP 200 OK https://index.rubygems.org/info/aws-sdk-cloudwatchevents
HTTP 429 Too Many Requests https://index.rubygems.org/info/xattr
HTTP GET https://index.rubygems.org/info/aws-sdk-codecommit
HTTP 200 OK https://index.rubygems.org/info/aws-sdk-cloudsearch
HTTP 200 OK https://index.rubygems.org/info/aws-sdk-applicationdiscoveryservice
HTTP 200 OK https://index.rubygems.org/info/aws-sdk-cloudhsm
HTTP GET https://index.rubygems.org/info/aws-sdk-codedeploy
HTTP GET https://index.rubygems.org/info/aws-sdk-codepipeline
Bundler::HTTPError: Net::HTTPTooManyRequests: <html>
<head><title>429 Too Many Requests</title></head>
<body bgcolor="white">
<center><h1>429 Too Many Requests</h1></center>
<hr><center>nginx</center>
</body>
</html>
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/fetcher/downloader.rb:36:in `fetch'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/fetcher/compact_index.rb:116:in `call'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client/updater.rb:43:in `block in update'
/usr/local/lib/ruby/2.4.0/tmpdir.rb:89:in `mktmpdir'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client/updater.rb:30:in `update'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client.rb:81:in `update'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client.rb:97:in `update_info'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/compact_index_client.rb:54:in `block in dependencies'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/fetcher/compact_index.rb:87:in `block (3 levels) in compact_index_client'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:63:in `apply_func'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:58:in `block in process_queue'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:55:in `loop'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:55:in `process_queue'
/usr/local/lib/ruby/gems/2.4.0/gems/bundler-1.15.1/lib/bundler/worker.rb:89:in `block (2 levels) in create_threads'
HTTP GET https://index.rubygems.org/info/aws-sdk-cognitoidentity
HTTP GET https://index.rubygems.org/info/aws-sdk-cognitoidentityprovider
HTTP GET https://index.rubygems.org/info/aws-sdk-cognitosync
HTTP GET https://index.rubygems.org/info/aws-sdk-configservice
HTTP GET https://index.rubygems.org/info/aws-sdk-databasemigrationservice
HTTP 200 OK https://index.rubygems.org/info/aws-sdk-configservice
HTTP GET https://index.rubygems.org/info/aws-sdk-datapipeline
HTTP 200 OK https://index.rubygems.org/info/aws-sdk-cloudwatchlogs
HTTP GET https://index.rubygems.org/info/aws-sdk-devicefarm
And more disturbingly, at the end of that run:
Successfully bootstrapped, to startup use ./launcher start webonly-multi
So does that mean that Iām missing that gem and wonāt find out until something tries to call them? I donāt use AWS, so I guess I donāt care? Iām confused.
Iāve read where you (or someone on team) said that you guys arenāt using any kind of proxy and rebuild all the time, so I canāt make sense of what Iām seeing.
2 Likes
Because theyāre the ones rate-limiting your requests.
I have no idea what their response would be. I donāt presume to speak for rubygems, which is why I suggest talking to them, to find out what they would say, and save all this guesswork.
It also says
Some endpoints may be cached by our CDN at times and therefore may allow higher request rates.
and
The RubyGems.org team may occasionally blackhole user IP addresses for extreme cases to protect the platform.
Which means that the correct description of the rate limit is ā10 requests per second, unless it isnātā. Which is less than entirely helpful.
If there were timestamps on that log, it would help to identify how quickly requests are actually being made. As it is, all we can see is ārequests were made, and some got 429ādā. Also, according to that exerpt, as is, you got rate-limited after two successful requests, so either youāre hitting a blacklist (itās hard to see how making three requests could get you to hit a 10 req/sec limit) or thereās other requests you didnāt show. Either way, though, without timestamps nobody can tell whether you might be hitting a limit or not.
Exactly. Weāve got customers with some pretty monstrous plugin lists, and their rebuilds never get rate-limited that Iāve seen. Perhaps we do builds often enough that the CDN node we hit is kept constantly fresh with all the packages we need, which isā¦ nice, I guess, but not helpful to anyone else.
Which is why, if you are seeing this problem, you should talk to rubygems so you can make sense of what youāre seeing, because our pontificating on meta about what may or may not be going on isnāt going to get the problem solved. If rubygems comes back with some actionable advice as to how Discourse and its environs can be modified to work better with rubygems rate-limits, great. Let us know, and weāll look into it. However, having someone from Discourse directly talk to rubygems isnāt going to help, because weāre not seeing the problem. We canāt provide any useful diagnostic data (such as source IPs, timestamps, or anything) to rubygems, nor can we describe how to reliably (or otherwise) reproduce the problem.
Soā¦ once again, if you are seeing rate-limiting problems with rubygems, talk to rubygems. If youāre not willing to do that, then please donāt complain about being rate-limited here on meta, because all youāre doing is adding to the noise, not the signal, about this problem.
5 Likes
Iāve got an idea now. Iāll see if I can figure out how to ask ruby gems about the problem. If I find out anything useful, Iāll let you know. 
4 Likes
@pfaffman ā Why not work with @hnaseri ā I recall @11145 having an issue as well ā maybe the three of you gather: outputs, source ips and such and see if there is a common denominator (privately!)ā¦
2 Likes
Is there any update on this issue @pfaffman?
1 Like
Iāve not heard back from them.
1 Like
Has anybody solved the problem?
I have the same issue: every attempt to run ./launcher rebuild <container> fails with the Ā«429 Too Many RequestsĀ» from rubygems.org:
Here is the only solution I have found: The only solution I have found to workaround Ā«429 Too Many RequestsĀ» failure from rubygems.org
This issue still exists. āTalking to rubygemsā cannot be an option. If an application is hitting a ratelimit by 3rd party, the application has to take care of building requests not exceeding the limits and/or to retry failed downloads after a safe period until the downloads are done.
Probably interesting to know that rubygems.org is using GEO location based DNS. Therefore they are able to respond very fast at every location.
Nevertheless thereās a difference between aws.eu-central-1 and aws-us-east-1. In both datacenters rubygems.org is available with ~ 1ms latency. But, at least currently, I am not hit by ratelimits in us-east-1, but in eu-central-1.
This is the official rubygems response:
Hi Jeff!
I conferred with the bundler folks about this issue and they told me it was a known issue with older versions of bundler. If your users update their bundler version, the issue should go away.
The errors are actually fastly throttling individual users, which as you might expect means that those versions of bundler are sending A LOT of requests.
8 Likes
Awesome @codinghorror! Thank you for tracking that down & providing some resolution to this issue.
3 Likes
I had this issue when trying to do a web_only install. So I went back to try a standard install and the first thing it wanted me to do was increase the swap file. I did that, re-ran the install and it seems to have fixed it.
I faced this issue today and Iām a little confused. We donāt install bundler when we install discourse. Then how can we even update it at all?
UPDATE:
I realized that discourse installation tries to install bundle. and I can see its already the latest version:
Successfully installed bundler-1.16.2
So it seems its not fixing the problem. Is there any other solutions?
Very little we can do here, perhaps you can open an issue on rubygems here with some guidance?
3 Likes
It sounds like this might be a solution
2 Likes
They seem to have documented it a while back.
- API and website: 10 requests per second
- Dependency API: 15 requests per second
- Website sign up, sign in, api key, and forgot password: 100 requests per 10 minutes
Users who hit a rate limit will see HTTP 429 responses, for the remainder of the limit window. Usually this is just a few minutes.
5 Likes