I just tried on the console the upgrade from v2.0.0.beta10 +37 to the current 2.1.0.beta1 but it fails to upgrade:
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 14438 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'"]}
8135e947b32512a6358b8d257d2f3568c36bd4345c1702c4e2fcd7c537151b18
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
I scrolled further up and I do see quite some HTTP 429 errors, for example
HTTP GET https://index.rubygems.org/info/uglifier
HTTP GET https://index.rubygems.org/info/unf_ext
HTTP GET https://index.rubygems.org/info/unf
HTTP GET https://index.rubygems.org/info/unicorn
HTTP GET https://index.rubygems.org/info/webmock
HTTP GET https://index.rubygems.org/info/webpush
HTTP 200 OK https://index.rubygems.org/info/tilt
HTTP 200 OK https://index.rubygems.org/info/sprockets-rails
HTTP 429 Too Many Requests https://index.rubygems.org/info/r2
HTTP 200 OK https://index.rubygems.org/info/sshkey
HTTP 200 OK https://index.rubygems.org/info/unf_ext
HTTP 200 OK https://index.rubygems.org/info/unf
HTTP 200 OK https://index.rubygems.org/info/webmock
HTTP 200 OK https://index.rubygems.org/info/uglifier
HTTP 200 OK https://index.rubygems.org/info/unicorn
HTTP 429 Too Many Requests https://index.rubygems.org/info/rails_multisite
HTTP 200 OK https://index.rubygems.org/info/progress
HTTP 429 Too Many Requests https://index.rubygems.org/info/rqrcode
HTTP 429 Too Many Requests https://index.rubygems.org/info/ruby-readability
HTTP 200 OK https://index.rubygems.org/info/image_size
but other then that I have not seen any other error at least not as far as I could scroll up.
I expect that one of the plugins is creating the problem even though we only have very few plugins installed:
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-tagging
- git clone https://github.com/angusmcleod/discourse-locations.git
- git clone https://github.com/angusmcleod/discourse-events.git
# - git clone https://github.com/angusmcleod/discourse-category-moderator-lite.git
# - git clone https://github.com/angusmcleod/discourse-layouts.git
- git clone https://github.com/cpradio/discourse-plugin-checklist.git
- git clone https://github.com/discourse/discourse-chat-integration.git
- git clone https://github.com/DemokratieInBewegung/dc-plugins-moderation-plusplus.git
I will try another rebuild again tomorrow without our own moderation++ plugin
On other thing I noticed. For whatever reason since a couple of month I do always have to install the new betas with the ssh console. In the admin screen it does always show me that a new beta is available like currently:
but when I clicked on the admin/upgrade I do always get:
You are running an old version of the Discourse image.
Upgrades via the web UI are disabled until you run the latest image.
To do so log in to your server using SSH and run:
cd /var/discourse git pull ./launcher rebuild app
which I am therefore always doing but with the next beta I have to do it again.
How can I fix it that an upgrade with the web admin interface will be possible again?
I know that it worked a couple months ago with the web admin interface and only from time to time I had to use the ssh console for an upgrade, but at least the last ten upgrades or so I had to do with the ssh console.
