Install not completing

Installing on Digital Ocean on a 1 GB Memory / 25 GB Disk / TOR1 - Ubuntu 18.04.3 (LTS) x64 Droplet using instructions at discourse/INSTALL-cloud.md at master · discourse/discourse · GitHub,

Tried earlier and it got to here and terminal cursor just flashed with nothing happening for an hour

If you are starting a NEW Rails application, you can ignore this notice.

For more info see:
https://github.com/svenfuchs/i18n/releases/tag/v1.1.0

I, [2020-02-14T00:18:43.379786 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'

Made a new Droplet and tried again. This time I got to here and it stalled for 2 hours

I, [2020-02-14T01:54:09.349437 #15306]  INFO -- : Writing /var/www/discourse/public/assets/docs/yuidoc-15ccfbcbae101060b3998aa1cb2a9d148b96f81255484f265a5a883d05002f00.json
MaxMind IP database updates require a license
Please set DISCOURSE_MAXMIND_LICENSE_KEY to one you generated at https://www.maxmind.com
MaxMind IP database updates require a license
Please set DISCOURSE_MAXMIND_LICENSE_KEY to one you generated at https://www.maxmind.com
3490.114340044 Compressing: vendor-4f4368a583d345145d638162999fffbf3ee486a25870135c3643c32a50ba66b4.js
uglifyjs '/var/www/discourse/public/assets/_vendor-4f4368a583d345145d638162999fffbf3ee486a25870135c3643c32a50ba66b4.js' -m -c -o '/var/www/discourse/public/assets/vendor-4f4368a583d345145d638162999fffbf3ee486a25870135c3643c32a50ba66b4.js' --source-map "base='/var/www/discourse/public/assets',root='/assets',url='/assets/vendor-4f4368a583d345145d638162999fffbf3ee486a25870135c3643c32a50ba66b4.js.map'"

And then Connection reset by xxx.xxx.xxx.xxx port 22

I’ve only used SSH 4 or 5 times before so I have no clue what’s happening or what to do next. Do I just start from scratch again tomorrow?

2 Likes

Tried to install three times today, still no success. Is there anything I can try? If it is getting this far does that mean I’ve done everything correctly or is it possible I’m messing it up somehow. I had a friend just try on his DO and he says he got it up and running in 12 minutes

First quit on me:

Unable to find image 'discourse/base:2.0.20191219-2109' locally
2.0.20191219-2109: Pulling from discourse/base
000eee12ec04: Pulling fs layer
4f95a31a80b7: Pulling fs layer
/usr/bin/docker: error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/4a/4a99baef7044cc8d119f1b31243782eb3ba3c7f702d16007a835f34d86cda33d/data?verify=1581715165-%2Fxs%2BUO2uQqTZs7CqdnXb3NnTt98%3D: dial tcp: lookup production.cloudflare.docker.com: Temporary failure in name resolution.
See '/usr/bin/docker run --help'.
Your Docker installation is not working correctly

See: https://meta.discourse.org/t/docker-error-on-bootstrap/13657/18?u=sam
root@forum:/var/discourse#

Second got hung up here:

I, [2020-02-14T21:21:03.533406 #1]  INFO -- : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+
I, [2020-02-14T21:21:04.713476 #1]  INFO -- :
I, [2020-02-14T21:21:04.714818 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development'
[DEPRECATED] The `--deployment` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set deployment 'true'`, and stop using this flag
[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set without 'test development'`, and stop using this flag

Third stalled at the same spot again

I, [2020-02-14T22:49:24.201371 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development'
[DEPRECATED] The `--deployment` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set deployment 'true'`, and stop using this flag
[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set without 'test development'`, and stop using this flag
1 Like

Can you compare the OS version and Docker version between you and your friend’s system? Are they the same?

2 Likes

We were both using 1 GB Memory / 25 GB Disk / Ubuntu 18.04.3 (LTS) x64. He used the same install instructions I was using so I assume that means it’s the same version of Docker

If you do this on the command line you’ll get the exact versions:

docker version

There was just a new release of Docker for Ubuntu 18.04, so it’s possible the systems might be different depending on the day it was setup.

2 Likes

We both set them up this afternoon. I can’t check my version of Docker because I’ve destroyed the Droplet already, but I will reinstall again and check and I’ve asked him to check. My friend also suggested I run apt-get update && apt-get upgrade before trying to install.

Okay, I think he might post here and be more helpful since unlike me, he knows what he’s doing.

Here’s his docker verion

:~# docker version                                                      Client: Docker Engine - Community
     Version:           19.03.6
     API version:       1.40
     Go version:        go1.12.16

Okay, this time it quit before it finished installing Docker, but it was the same version

root@talk:~# docker version
Client: Docker Engine - Community
 Version:           19.03.6
 API version:       1.40
 Go version:        go1.12.16
 Git commit:        369ce74a3c
 Built:             Thu Feb 13 01:27:49 2020
 OS/Arch:           linux/amd64
 Experimental:      false

And here’s where it died this time

root@talk:/var/discourse# ./discourse-setup
Docker not installed. Enter to install from https://get.docker.com/ or Ctrl+C to exit
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 13216  100 13216    0     0   141k      0 --:--:-- --:--:-- --:--:--  143k
# Executing docker install script, commit: f45d7c11389849ff46a6b4d94e0dd1ffebca32c1
+ sh -c apt-get update -qq >/dev/null
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
Connection reset by 167.99.190.164 port 22
1 Like

I am aforementioned friend:

Added DNS A Record, spun up this Droplet:

1 GB Memory / 25 GB Disk / NYC3 - Ubuntu 18.04.3 (LTS) x64

root@pandiscourse:~# docker version

Client: Docker Engine - Community
Version: 19.03.6
API version: 1.40
Go version: go1.12.16
Git commit: 369ce74a3c
Built: Thu Feb 13 01:27:49 2020
OS/Arch: linux/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.6
API version: 1.40 (minimum version 1.12)
Go version: go1.12.16
Git commit: 369ce74a3c
Built: Thu Feb 13 01:26:21 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683

root@pandiscourse:~# history

1 200214 20:46:52 git clone https://github.com/discourse/discourse_docker.git /var/discourse
2 200214 20:46:56 cd /var/discourse/
3 200214 20:47:10 ./discourse-setup
4 200214 20:59:01 date

That was the entirety of my history file. Worked first try. I can provide any other info but I don’t know what would be different between our setups on a fresh Droplet.

2 Likes

@glassgorilla noted that there were a couple of Connection resets on my failed installs. That always happened long after the install had stopped progressing, but I tried installing again and ran a continuous ping and there were no timeouts and pings were consistently Reply from 8.8.8.8: bytes=32 time=9ms TTL=56. Same result. It hung up on this line again.

I, [2020-02-15T01:27:39.712008 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development'
[DEPRECATED] The `--deployment` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set deployment 'true'`, and stop using this flag
[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set without 'test development'`, and stop using this flag

Docker info:

Client: Docker Engine - Community
 Version:           19.03.6
 API version:       1.40
 Go version:        go1.12.16
 Git commit:        369ce74a3c
 Built:             Thu Feb 13 01:27:49 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.6
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.16
  Git commit:       369ce74a3c
  Built:            Thu Feb 13 01:26:21 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Are you doing a SSH connection using Putty from Windows?

SSH connection using Windows PowerShell. Can try with Putty instead tomorrow

Have tried twice more with putty. No luck. Got stuck here again

I, [2020-02-15T04:42:02.877212 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --deployment --retry 3 --jobs 4 --verbose --without test development'
[DEPRECATED] The `--deployment` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set deployment 'true'`, and stop using this flag
[DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set without 'test development'`, and stop using this flag

if you want help ,i can help you install over do for free

2 Likes

Thanks a lot. I appreciate the offer. I’m just concerned if I can’t even get it to install then I won’t be able to maintain the site and don’t want to have to go through all this again every time I need to do anything.

i would recommed share your app.yml to check whether there is something wrong with it
second pls use tmux since installation really takes time and if your ssh hang up you wont know what is going on here

3 Likes

Thanks but I’m new to all this and have used SSH and bash(?) more trying to get this installed than I had in my entire life up until now and have no idea how I would do any of the things you suggest.

I gave him my pubkey which he used for root on a fresh Droplet, again was able to install first try without issue, web interface up and running. I think it’s safe to say this is a Connection Issue and not a Discourse Setup issue. If that’s the correct assessment, would using mosh instead overcome the connection reset issues?

3 Likes

Yes. Mosh sounds like a great idea, especially if you know what mosh is. :grin:

1 Like

Thanks to everyone for all the help. Worked fine with Mosh. That was the longest 1/2 hour install of my life but at least I have no one to blame but myself.

4 Likes

I’ve gotten in the habit of whacking the ENTER key every minute or two on long-running remote SSH commands when I’m on a client/network that gets this problem!

Usually it’s a network middlebox with aggressive connection timeouts.

5 Likes

Configuring your ssh to send keepalives might help: How to Keep Alive SSH Sessions

The screen command allows you to leave a session and come back to it later: https://linuxize.com/post/how-to-use-linux-screen/

6 Likes