Hi, I’m attempting to install Discourse, but am failing so far. It appears that bootstrapping doesn’t want to… bootstrap? Anyhow, I read a couple of other threads about it and tried “./launcher rebuild app”, which gave the following output: WARNING: No memory limit support WARNING: No swap limit support Updating discourse docker Already up-to-date. Calculated ENV: -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_MALLOC_LIMIT=40000000 -e RUBY_HEAP_MIN_SLOTS=800000 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e HOME=/root -e DISCOURSE_DEVELOPER_EMAILS=myEmail -e DISCOURSE_HOSTNAME=myWebsite -e DISCOURSE_SMTP_ADDRESS=smtp.mandrillapp.com cd /pups && git pull && /pups/bin/pups --stdin From https://github.com/SamSaffron/pups f7a125b..ac9bdf8 master -> origin/master Updating f7a125b..ac9bdf8 Fast-forward README.md | 2 +- lib/pups/config.rb | 14 +++++++++++++- 2 files changed, 14 insertions(+), 2 deletions(-) I, [2014-09-13T20:18:17.839357 #47] INFO -- : Loading --stdin I, [2014-09-13T20:18:17.846012 #47] INFO -- : > mkdir -p /shared/postgres_run I, [2014-09-13T20:18:17.851117 #47] INFO -- : I, [2014-09-13T20:18:17.852106 #47] INFO -- : > chown postgres:postgres /shared/postgres_run I, [2014-09-13T20:18:17.856033 #47] INFO -- : I, [2014-09-13T20:18:17.857172 #47] INFO -- : > chmod 775 /shared/postgres_run I, [2014-09-13T20:18:17.861779 #47] INFO -- : I, [2014-09-13T20:18:17.862868 #47] INFO -- : > rm -fr /var/run/postgresql I, [2014-09-13T20:18:17.867169 #47] INFO -- : I, [2014-09-13T20:18:17.868189 #47] INFO -- : > ln -s /shared/postgres_run /var/run/postgresql I, [2014-09-13T20:18:17.872311 #47] INFO -- : I, [2014-09-13T20:18:17.873194 #47] INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 I, [2014-09-13T20:18:17.880853 #47] INFO -- : postgres already running stop container FAILED -------------------- RuntimeError: socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 failed with return # Location of failure: /pups/lib/pups/exec_command.rb:85: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" fe396f76ce0ba379260b0a625c3007cf1d2f13343b7de29f3376ffd5fbb02e2b FAILED TO BOOTSTRAP What am I doing wrong?

Hi. I have the same issue. Tried to run “./launcher start app” command from https://github.com/discourse/discourse/blob/master/docs/INSTALL-digital-ocean.md instructions on Amazon EC2 linux ami last version. Everything was fine but during running the command the connection was lost and after reconnecting I getting the same error when trying to run that command again.

./launcher bootstrap app which: no docker.io in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/aws/bin:/home/odesk/bin:/opt/aws/bin) Your Docker installation is not using the recommended AuFS (union filesystem) and may be unstable. If you are unable to bootstrap / stop your image please report the issue at: [https://]meta.discourse.org/t/discourse-docker-installation-without-aufs/15639 Calculated ENV: -e LANG=en_US.UTF-8 -e RAILS_ENV=production -e UNICORN_WORKERS=3 -e UNICORN_SIDEKIQS=1 -e RUBY_GC_MALLOC_LIMIT=40000000 -e RUBY_HEAP_MIN_SLOTS=800000 -e DISCOURSE_DB_SOCKET=/var/run/postgresql -e DISCOURSE_DB_HOST= -e DISCOURSE_DB_PORT= -e HOME=/root -e DISCOURSE_DEVELOPER_EMAILS=doe518875@gmail.comsmtp.example.co -e DISCOURSE_HOSTNAME=discourse.example.com -e DISCOURSE_SMTP_ADDRESS=smtp.mandrillapp.com cd /pups && git pull && /pups/bin/pups --stdin From github.com/SamSaffron/pups f7a125b..ac9bdf8 master -> origin/master Updating f7a125b..ac9bdf8 Fast-forward README.md | 2 +- lib/pups/config.rb | 14 +++++++++++++- 2 files changed, 14 insertions(+), 2 deletions(-) I, [2014-09-13T21:01:09.379800 #43] INFO -- : Loading --stdin I, [2014-09-13T21:01:09.388596 #43] INFO -- : > mkdir -p /shared/postgres_run I, [2014-09-13T21:01:09.408363 #43] INFO -- : I, [2014-09-13T21:01:09.409992 #43] INFO -- : > chown postgres:postgres /shared/postgres_run I, [2014-09-13T21:01:09.444893 #43] INFO -- : I, [2014-09-13T21:01:09.446697 #43] INFO -- : > chmod 775 /shared/postgres_run I, [2014-09-13T21:01:09.463053 #43] INFO -- : I, [2014-09-13T21:01:09.464424 #43] INFO -- : > rm -fr /var/run/postgresql I, [2014-09-13T21:01:09.479833 #43] INFO -- : I, [2014-09-13T21:01:09.481206 #43] INFO -- : > ln -s /shared/postgres_run /var/run/postgresql I, [2014-09-13T21:01:09.496822 #43] INFO -- : I, [2014-09-13T21:01:09.498387 #43] INFO -- : > socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 I, [2014-09-13T21:01:09.539816 #43] INFO -- : postgres already running stop container FAILED -------------------- RuntimeError: socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 failed with return # Location of failure: /pups/lib/pups/exec_command.rb:85: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" c284aef6888f612519acfd6fd42a21e81f1ac3e6e266244ba4c9a07a816f263d FAILED TO BOOTSTRAP

Installation is at /var/discourse, as per the official installation notes. Using Debian

Rebooting the whole system seems to have worked. It now passes the initial breaking point, and I’m awaiting full rebuild now. Thanks :slight_smile:

reboot as in type “reboot” in the cli? cause that didn’t work for me. Im on docker

I meant the whole server. Not just docker, not just cli, everything. All of it.

Done. Same results. I was doing the same thing before anyways. FAILED -------------------- RuntimeError: socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 failed with return # Location of failure: /pups/lib/pups/exec_command.rb:105: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" cb91b239e00fe5e4c1a0f4eb5eea26263eb6149df52db1c6cb6d81899e4cc510 FAILED TO BOOTSTRAP

[Solved]Bootstrap fails, Postgres already running

Product Support Self-hosting

sam (Sam Saffron) 29 במרץ,‏ 2015,‏ 10:52pm 18

well, if you app is running you can not bootstrap it.

Instead do:

./launcher rebuild app

נושא		תגובות	צפיות
FAILED TO BOOTSTRAP, even on a fresh installation Self-hosting	3	871	15 במרץ,‏ 2023
Building bootstrap error Self-hosting	45	2968	20 בנובמבר,‏ 2022
Failed to install Discourse in Ubuntu14.04: docker problems Self-hosting docker	19	8674	25 בינואר,‏ 2015
"postgres already running " on Self-hosting	1	1192	18 ביוני,‏ 2018
Postgres Errors on Rebuild Self-hosting	2	1771	16 בספטמבר,‏ 2015

[Solved]Bootstrap fails, Postgres already running

נושאים קשורים