Just can’t seem to get Discourse to work with Opensuse 13.2. Please help me troubleshoot?

Merpdotcom · November 17, 2016 2:23pm

Okay, I'll give that a shot. I'm a total newbie to Docker & Discourse.
Will report back how the approach you suggested goes, shortly.
Thanks!

Merpdotcom · November 17, 2016 2:43pm

Pretty much same result?

 ./launcher bootstrap app
which: no docker.io in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/games)

cd /pups && git pull && /pups/bin/pups --stdin
fatal: unable to access 'https://github.com/SamSaffron/pups.git/': Could not resolve host: github.com
d2ce24f941f71a170a7ff1d6fb05b91137fbb0341376bb23bb018afa3a9aad7f
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

cat app.yml

## this is the all-in-one, standalone Discourse Docker container template
##
## After making changes to this file, you MUST rebuild
## /var/discourse/launcher rebuild app
##
## BE *VERY* CAREFUL WHEN EDITING!
## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
## visit http://www.yamllint.com/ to validate this file as needed

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
  - "templates/web.ssl.template.yml"
  - "templates/web.letsencrypt.ssl.template.yml"
 
## which TCP/IP ports should this container expose?
## If you want Discourse to share a port with another webserver like Apache or nginx,
## see https://meta.discourse.org/t/17247 for details
expose:
  - "4080:4080"   # http
  - "40443:40443" # https

params:
  db_default_text_search_config: "pg_catalog.english"

  ## Set db_shared_buffers to a max of 25% of the total memory.
  ## will be set automatically by bootstrap based on detected RAM, or you can override
  db_shared_buffers: "4096MB"
  
  ## can improve sorting performance, but adds memory usage per-connection
  #db_work_mem: "40MB"
  
  ## Which Git revision should this container use? (default: tests-passed)
  #version: tests-passed

env:
  LANG: en_US.UTF-8
  # DISCOURSE_DEFAULT_LOCALE: en

  ## How many concurrent web requests are supported? Depends on memory and CPU cores.
  ## will be set automatically by bootstrap based on detected CPUs, or you can override
  UNICORN_WORKERS: 8

  ## TODO: The domain name this Discourse instance will respond to
  DISCOURSE_HOSTNAME: d2.merp.com
  
  ## Uncomment if you want the container to be started with the same
  ## hostname (-h option) as specified above (default "$hostname-$config")
  DOCKER_USE_HOSTNAME: true

  ## TODO: List of comma delimited emails that will be made admin and developer
  ## on initial signup example 'user1@example.com,user2@example.com'
  DISCOURSE_DEVELOPER_EMAILS: 'remmed@gmail.com'

  ## TODO: The SMTP mail server used to validate new accounts and send notifications
  DISCOURSE_SMTP_ADDRESS: smtp.gmail.com
  DISCOURSE_SMTP_PORT: 587
  DISCOURSE_SMTP_USER_NAME: remmed@gmail.com
  DISCOURSE_SMTP_PASSWORD: "remmed"
  #DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)
  
  ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
  #LETSENCRYPT_ACCOUNT_EMAIL: me@example.com
  LETSENCRYPT_ACCOUNT_EMAIL: remmed@gmail.com

  ## The CDN address for this Discourse instance (configured to pull)
  ## see https://meta.discourse.org/t/14857 for details
  #DISCOURSE_CDN_URL: //discourse-cdn.example.com

## The Docker container is stateless; all data is stored in /shared
volumes:
  - volume:
      host: /var/discourse/shared/standalone
      guest: /shared
  - volume:
      host: /var/discourse/shared/standalone/log/var-log
      guest: /var/log

## Plugins go here
## see https://meta.discourse.org/t/19157 for details
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git

## Any custom commands to run after building
run:
  - exec: echo "Beginning of custom commands"
  ## If you want to set the 'From' email address for your first registration, uncomment and change:
  ## After getting the first signup email, re-comment the line. It only needs to run once.
  #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"
  - exec: echo "End of custom commands"

pfaffman · November 17, 2016 2:55pm

I was wrong about the docker error, but you're still not able to get to github from the container. Search for "Could not resolve host: github.com" here. I think this is it:

Merpdotcom · November 17, 2016 4:02pm

Thanks. I had mentioned earlier (but understandable to have missed with the growing length of this thread), that I did the following early on:

/etc/sysconfig/docker

## Path           : System/Management
## Description    : Extra cli switches for docker daemon
## Type           : string
## Default        : ""
## ServiceRestart : docker
#
DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4"

And just in case, symlinked it to /etc/docker/docker:

ln -s /etc/sysconfig/docker /etc/docker/docker

But, it still doesn't seem to be resolving. So I will back up and try digging deeper into docker to see why it isn't getting name resolution properly...
I will report back.

Crud, now I can't post this response, "You've reached the maximum number of replies a new user can create on their first day. Please wait 1 hour before trying again."
Now that is really compounding frustration.
Please, can someone please un-throttle me?

Merpdotcom · November 17, 2016 4:03pm

Oops, looks like I didn't restart the Docker service after making the changes to /etc/sysconfig/docker.

So, running again:

./launcher bootstrap app
which: no docker.io in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/games)

cd /pups && git pull && /pups/bin/pups --stdin
Already up-to-date.
I, [2016-11-17T23:09:11.260343 #14]  INFO -- : Loading --stdin
I, [2016-11-17T23:09:11.269033 #14]  INFO -- : > mkdir -p /shared/postgres_run
I, [2016-11-17T23:09:11.272431 #14]  INFO -- :
I, [2016-11-17T23:09:11.272668 #14]  INFO -- : > chown postgres:postgres /shared/postgres_run
I, [2016-11-17T23:09:11.275957 #14]  INFO -- :
I, [2016-11-17T23:09:11.276178 #14]  INFO -- : > chmod 775 /shared/postgres_run
I, [2016-11-17T23:09:11.278879 #14]  INFO -- :
I, [2016-11-17T23:09:11.279051 #14]  INFO -- : > rm -fr /var/run/postgresql
I, [2016-11-17T23:09:11.281939 #14]  INFO -- :
I, [2016-11-17T23:09:11.282114 #14]  INFO -- : > ln -s /shared/postgres_run /var/run/postgresql
I, [2016-11-17T23:09:11.284730 #14]  INFO -- :
I, [2016-11-17T23:09:11.284898 #14]  INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1
I, [2016-11-17T23:09:11.293513 #14]  INFO -- : postgres already running stop container

FAILED
--------------------
Pups::ExecError: socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 failed with return #<Process::Status: pid 21 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params "socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1"
7f24537d5bc82d13bed9da3c5de67121158a72c66c3580602a275bb8fc2daa11
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

Do I need to remove the current attempts from Docker, and delete the directory (again), and try to start over again? Or is there another approach to get this to continue from a partially failed install?

Thanks!

I'm trying just docker stop app.
And then re-run ./launcher bootstrap app, and will see how it goes now...

Merpdotcom · November 17, 2016 4:18pm

Okay. It looks like the base install finally completed:

Successfully bootstrapped, to startup use ./launcher start app
d2d203:/var/discourse # ./launcher start app
which: no docker.io in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/games)

starting up existing container
+ /usr/bin/docker start app
app

Ah, but the SSL still failed to setup properly. There isn't an access.log file, and the error.log file for nginx is complaining about no cert:

tail -f /var/discourse/shared/standalone/log/var-log/nginx
2016/11/18 00:16:20 [emerg] 1767#1767: BIO_new_file("/shared/ssl/66.165.236.129.cer") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/shared/ssl/66.165.236.129.cer','r') error:2006D080:BIO routines:BIO_new_file:no such file)
^C

I guess I could rem out the SSL options, and go without SSL just for the sake of trying to get the basics working?

I'll try that, re-run rebuild, and see if that will at least get the regular http working...

Merpdotcom · November 17, 2016 5:08pm

That didn't not resolve. It is still looking for the SSL errors, and still no access.log, only error.log.
I guess I'll try wiping it clean again, and try again with the new tweaks learned.
Remove the docker images. Delete the content from the /var/discourse dir.
Regrab it from github. Copy samples/standalone.yml to containers/app.yml. Edit the app.yml to not have ssl at this stage. Run the launcher bootstrap app. And see if that works any better.

And the final ludicrousness:

Wow, I still can't believe the moderator muted this call for help.
Since the moderator muted/killed this thread, hopefully I can figure out the rest on my own. I'll post the rest of my challenges, findings, and fixes to this blog posting instead. This will make for an interesting discussion for the show's next episode regarding community support approaches and attitudes.
http://techtalkhawke.com/news/discord-with-discourse
Sheesh.

UPDATE: 19:38, 20161117. Now the moderator completely suspended my account on meta.discourse.org!!! Wow, how childish! More fodder for the next show. Fun!

Just noticed, account banned for a year. Reason, "No longer welcome here".

Unbelievable. The level of immaturity is amazing. Was he a Reddit or 4Chan moderator moonlighting on the Discourse.org website? :-)

And a good thing I made a backup, sure enough the cofounder / moderator in a fit of pique, deleted both threads completely (or at least locked them from public view).

Childish Discord with Discourse.org Moderator

Discord With Discourse

Just can’t seem to get Discourse to work with Opensuse 13.2. Please help me troubleshoot?