Users are experiencing build failures due to RubyGems rate limiting, receiving HTTP 429 errors when running bundle install during Discourse updates. The issue appears to be triggered by high request rates from the Discourse bootstrap script, possibly exacerbated by plugins like discourse-backups-to-dropbox. While some users suggest the problem may be related to outdated bundler versions, others note that the rate limit is enforced at 10 requests per second, with potential exceptions for CDN-cached endpoints. The community discusses the need to contact RubyGems directly for resolution, as the Discourse team cannot reproduce the issue or provide diagnostic data. One user found a workaround by increasing swap space, while others recommend checking for plugin-related issues or updating bundler. The official RubyGems response indicates the problem may stem from older bundler versions sending excessive requests. hnaseri, mpalmer, robbyoconnor, pfaffman, dmitry_fedyuk, thabbs, codinghorror, watchmanmonitor, djensen47, parisa, sam, zogstrip
Hello. I wanted to update my discourse for new commits, it did fail. Then I rebuild app, it also failed with the following error. Any Idea?
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 13406 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
1202bf591b3bb66f4bb14db9ffd2761171eaaece447b8e3c00051fd4866d511c
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
I dont know its a lot of text. I searched for “error” and these are the lines I got:
HTTP 429 Too Many Requests https://index.rubygems.org/info/sprockets-rails
Bundler::HTTPError: Net::HTTPTooManyRequests: <html>
<head><title>429 Too Many Requests</title></head>
I, [2017-06-16T21:36:48.032740 #14] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!
Gem::MissingSpecError: Could not find 'http-cookie' (~> 1.0) among 248 total gem(s)
Checked in 'GEM_PATH=/var/www/discourse/vendor/bundle/ruby/2.4.0', execute `gem env` for more information
I got this rebuilding last week. I commented out a plugin. I built again. It worked. Then I couldn’t figure out why that plugin could have caused a problem, put it back in, rebuilt, and it worked. I had prepared a bug report plea for help, but since the problem went away, I never posted it.
There have been a handful of these “too many requests” errors from rubygems lately. I can’t make sense of them.
Removing old container
+ /usr/bin/docker rm app
Error response from daemon: Driver overlay failed to remove root filesystem abd13a925ecc025fb672e6ee0e594758f846f3ed393a8f647bb6cf1cf970fa6b: remove /var/lib/docker/overlay/d6866837ea0650d91bb09d012158ca82276cecc6d2c1c332d31e18c0651845dc/merged: device or resource busy
starting up existing container
+ /usr/bin/docker start app
Error response from daemon: Container is marked for removal and cannot be started.
Error: failed to start containers: app
Plugins get broken if Discourse gets updated in a way that breaks the plugin. The other plugin you listed is maintained by a team member, so it’s somewhat more likely he’ll notice something’s wrong before other people.