Gem::RemoteFetcher::FetchError error during install

Product Support Self-hosting

AI-generated summary

The user obboy encountered a Gem::RemoteFetcher::FetchError error during the installation of Discourse using the ./discourse-setup script. The error message indicated a connection reset by the peer while trying to access https://api.rubygems.org/specs.4.8.gz.

Obboy suspected a network connection issue and asked for guidance on the next steps. codinghorror advised that either re-running ./discourse-setup or executing ./launcher rebuild app would resolve the issue.

1

when i execute ./discourse-setup script. I got message below:

I, [2016-05-22T10:46:17.514250 #36]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 235
235:signal-handler (1463913977) Received SIGTERM scheduling shutdown...
2016-05-22 10:46:17 UTC [110-2] LOG:  database system is shut down
235:M 22 May 10:46:17.534 # User requested shutdown...
235:M 22 May 10:46:17.536 * Saving the final RDB snapshot before exiting.
235:M 22 May 10:46:17.540 * DB saved on disk
235:M 22 May 10:46:17.541 # Redis is now ready to exit, bye bye...


FAILED
--------------------
RuntimeError: cd /var/www/discourse && gem update bundler failed with return #<Process::Status: pid 346 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "chown -R discourse $home"]}
440bda508369286c7ea776cfedfdc46e3909c216a8217a20d57a9a06350d0816
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
2

** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

You did not follow this advice. Find the error, you didn’t print it above.

3

thx, the error may occur by network connection. But what should i do next ? execute ./discourse-setup again， or ./launcher rebuild ？

I, [2016-05-22T10:46:13.799929 #36]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2016-05-22T10:46:13.801295 #36]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2016-05-22T10:46:13.802423 #36]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2016-05-22T10:46:13.803562 #36]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2016-05-22T10:46:13.804808 #36]  INFO -- : > echo "done configuring web"
I, [2016-05-22T10:46:13.806273 #36]  INFO -- : done configuring web

I, [2016-05-22T10:46:13.807578 #36]  INFO -- : > cd /var/www/discourse && gem update bundler
ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    Errno::ECONNRESET: Connection reset by peer - SSL_connect (https://api.rubygems.org/specs.4.8.gz)
I, [2016-05-22T10:46:17.507815 #36]  INFO -- : Updating installed gems
4

Either one will work, the command is ./launcher rebuild app