Installation Failed: Plugins

Support Self-hosting

AI-generated summary

The discussion revolves around a failed Discourse installation due to plugin issues. barreeeiroo initially encountered an error while rebuilding Discourse with ./launcher rebuild app, which was later revealed to be caused by the docker_manager plugin being listed twice in the app.yml file, as pointed out by david.

After resolving this issue, barreeeiroo encountered another error related to the bundle exec rake db:migrate command, which was suspected to be caused by a Rubygems rate limit issue, as explained by elijah. Despite trying multiple times and manually installing the gems, barreeeiroo was unable to resolve the issue.

1

I’m trying to rebuild Discourse with ./launcher rebuild app but I get the following error:

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git failed with return #<Process::Status: pid 260 exit 128>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"/var/www/discourse/plugins", "cmd"=>["git clone https://github.com/discourse/docker_manager.git", "git clone https://github.com/discourse/docker_manager.git", "git clone https://github.com/davidtaylorhq/discourse-whos-online.git", "git clone https://github.com/discourse/discourse-translator.git", "git clone https://github.com/discourse/discourse-solved.git", "git clone https://github.com/discourse/discourse-cakeday.git", "git clone https://github.com/discourse/discourse-assign.git", "git clone https://github.com/xfalcox/discourse-signatures.git", "git clone https://github.com/discourse/discourse-push-notifications.git", "git clone https://github.com/discourse/discourse-staff-notes.git", "git clone https://github.com/vinkas0/discourse-branding.git", "git clone https://github.com/discourse/discourse-presence.git", "git clone https://github.com/discourse/discourse-voting.git", "git clone https://github.com/Ebsy/discourse-nationalflags.git", "git clone https://github.com/discourse/discourse-adplugin.git", "git clone https://github.com/sekhat/discourse-yuml.git", "git clone https://github.com/davidtaylorhq/discourse-telegram-notifications.git", "git clone https://github.com/discourse/discourse-chat-integration.git"]}
9989d6efc0cc514dcd63e4ce0141b175b4094abca671622878b2faf176a1d403
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Any idea of what can it be causing?

2

^^ please can you scroll up and find the error, the bit you’ve posted doesn’t really help track it down

3

There are no more errors
I’ve already checked that :confused:

https://pastebin.com/H9teZBXi

I can’t post it directly due to post lenght limit :sweat:

4 
destination path 'docker_manager' already exists and is not an empty directory.

Have you got docker_manager listed twice in your app.yml?

5

Oh, yeah :sweat_smile::sweat:
I was restoring a backup of the community and I forgot it :pray:

Thanks a lot @david :smile::+1:

6

Now I get this :tired_face:

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 502 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'"]}
10e358782174bb619bcfda02feb0506c7e2daa2a25fc172ce07d57f625d2317d
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

https://pastebin.com/7ZGAEHLF

7

It’s our old “friend” Rubygems giving a 429 error.

Lots of people have been getting that, no one is quite sure why. Critically, it has not been happening for Discourse’s own builds, so it’s not something inherent in Discourse. The people at Rubygems have not been forthcoming with an answer. The recommended “fix” is just try again in a little while. And maybe complain to Rubygems.

Search for “rubygems rate limit” or “rubygems 429” for other topics on this.

8

I tried again and again but nothing :disappointed:

I’ve also tried to install manually the gems that couldn’t be download inside the Docker container; they are installed with gem install x after ./launcher enter app but there stills download them automatically and showing 429 Error