Install terminates while fetching source index from rubygems.org

تثبيت
1

Hello, I am running as root and trying to install via docker by the instructions at https://github.com/discourse/discourse/blob/master/docs/INSTALL-digital-ocean.md

I am getting this error.
This includes the error and some of the log before the error

& mkdir -p plugins
I, [2015-02-11T17:08:33.012194 #39]  INFO -- : 
I, [2015-02-11T17:08:33.012290 #39]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2015-02-11T17:08:40.782499 #39]  INFO -- : 
I, [2015-02-11T17:08:40.783920 #39]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2015-02-11T17:08:40.797983 #39]  INFO -- : 
I, [2015-02-11T17:08:40.804976 #39]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2015-02-11T17:08:40.807189 #39]  INFO -- : 
I, [2015-02-11T17:08:40.807502 #39]  INFO -- : > mkdir -p /var/nginx/cache
I, [2015-02-11T17:08:40.816406 #39]  INFO -- : 
I, [2015-02-11T17:08:40.825493 #39]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2015-02-11T17:08:40.826530 #39]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2015-02-11T17:08:40.827381 #39]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2015-02-11T17:08:40.836129 #39]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2015-02-11T17:08:40.838013 #39]  INFO -- : > echo "done configuring web"
I, [2015-02-11T17:08:40.846865 #39]  INFO -- : done configuring web

I, [2015-02-11T17:08:40.848126 #39]  INFO -- : > cd /var/www/discourse && gem update bundler
I, [2015-02-11T17:09:05.100549 #39]  INFO -- : Updating installed gems
Updating bundler
Successfully installed bundler-1.8.0
Gems updated: bundler

I, [2015-02-11T17:09:05.100906 #39]  INFO -- : > cd /var/www/discourse && chown -R discourse /var/www/discourse
I, [2015-02-11T17:13:07.923663 #39]  INFO -- : 
I, [2015-02-11T17:13:07.926861 #39]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --deployment --verbose --without test --without development'
I, [2015-02-11T17:47:11.883710 #39]  INFO -- : HTTP GET https://bundler.rubygems.org/api/v1/dependencies
HTTP 200 OK
Fetching source index from https://rubygems.org/

[220 | signal handler] (1423676832) Received SIGTERM scheduling shutdown...
I, [2015-02-11T17:47:11.899232 #39]  INFO -- : Terminating async processes
I, [2015-02-11T17:47:11.899343 #39]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.3/bin/postmaster -D /etc/postgresql/9.3/main pid: 107
2015-02-11 17:47:12 UTC LOG:  received fast shutdown request
2015-02-11 17:47:12 UTC LOG:  aborting any active transactions
2015-02-11 17:47:12 UTC LOG:  autovacuum launcher shutting down
I, [2015-02-11T17:47:12.124865 #39]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 220
2015-02-11 17:47:12 UTC LOG:  shutting down
[220] 11 Feb 17:47:12.305 # User requested shutdown...
[220] 11 Feb 17:47:12.305 * Saving the final RDB snapshot before exiting.
[220] 11 Feb 17:47:12.731 * DB saved on disk
[220] 11 Feb 17:47:12.731 # Redis is now ready to exit, bye bye...
2015-02-11 17:47:12 UTC LOG:  database system is shut down


FAILED
--------------------
RuntimeError: cd /var/www/discourse && su discourse -c 'bundle install --deployment --verbose --without test --without development' failed with return #<Process::Status: pid 329 exit 137>
Location of failure: /pups/lib/pups/exec_command.rb:105: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'"]}
2cb1048638f942b9f79fa20190f91ace620615e9cadde7ca73b750271534f7c9
FAILED TO BOOTSTRAP

I am experienced with linux / ubuntu systems but I have very little experience with ruby or gems. What am I doing wrong? I followed the initial instructions to the letter. The only things in the config file that I changed was the smtp server and the admin email.

2

This looks like a transient error because https://rubygems.org/ wasn’t responding in time; is your server behind a firewall that might block access to the RubyGems site?

3

Highly doubt it. I will try again later, is there anything I can do if the site is blocked?

4

Are there other things that can cause this?

5

Probably. The logged <Process::Status: pid 329 exit 137> indicates that bundler was killed with a KILL signal which, under normal circumstances, only happens

  • when issued manually with kill -9,
  • during system shutdown if the process didn’t respond to a TERM signal first,
  • or if the kernel has run out of memory and needs to free up some RAM…
إعجاب واحد (1)
6

Hrm, that RAM thing could be an issue, im running on 1.75 gb of RAM, but I have an apache server, phpmyadmin and mysql running on the vps already. Could that be the issue?

إعجاب واحد (1)
7

I’d say so. Even if the bootstrapping succeeds, it’ll be hard to get Discourse to run; and if you can get it to run, you’ll most likely not enjoy the performance…

1 GB + 1 GB swap is the minimum requirement for the default Discourse setup with nothing else running on the system.

إعجاب واحد (1)