Hi, I am currently migrating from a classical two container setup (separated web_only and data containers) to a setup where the database is hosted on a central database server (not inside a docker container). The central database was created from the dump.sql which is part of the backup file. The…

[image] Thommie Rother: permission denied for table site_settings OK, as always, it was a “layer 8 problem” :smiling_face_with_tear: I already had a discourse database in the postgres but the discourse user/role had not all required privileges on it. And I did miss some major “behavioural” d…

Hi Jay, I followed the thread of Falco at Configure Discourse to use a separate PostgreSQL server The database server is available from the VM: root@docker2:/var/discourse# pg_isready -d discourse -h 10.10.10.18 -p 5432 -U discourse 10.10.10.18:5432 - Verbindungen werden angenommen (connecti…

[image] Thommie Rother: The DB name, user and password in web_only.yml are also correct. IN that case: [image] Thommie Rother: ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. What plugins do you have? Do you have the AI plugi…

PostgreSQL 13.12 no AI plugin plugins: cmd: - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/discourse/discourse-shared-edits.git - git clone https://github.com/discourse/discourse-chat-integration - git clone https:…

Can you [image] Thommie Rother: please scroll up and look for earlier error messages, there may be more than one. ? The exact error message in the backtrace will tell us exactly what is the problem :smile: [image] Thommie Rother: I am currently migrating from a classical two container …

error code: > FAILED > -------------------- > Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 816 exit 1> > Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn' > …

[image] Thommie Rother: DISCOURSE_DB_SOCKET: ‘’ I wonder if having this set to a blank value rather than unset will cause problems. In any case, please post the complete output.

the complete build log after ./launcher rebuild web_only web_only_build.zip (9.4 KB) the yaml web_only.zip (2.4 KB) Concerning the DISCOURSE_DB_SOCKET: ‘’: as we use a remote connection, I would guess that the socket value is not relevant in both cases (dockered data or remote data)

The error was farther up in the build log: … docker_manager is already at latest compatible version wp-discourse is already at latest compatible version I, [2023-11-10T21:08:17.388213 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' Plugin name is 'discourse-…

Hmmmm, strange, the discourse database user has postgres=# GRANT ALL ON DATABASE discourse TO discourse; on the central postgres server. Do we need anything else for this role?

Moving postgres db to central db server: build error

Product Support Self-hosting

pfaffman (Jay Pfaffman) November 8, 2023, 5:32am 2

Are you sure that the remote database is available from the server? It looks like it’s not. Can you telnet to the database port from the web server machine?

Topic		Replies	Views
Separate psql server / migrate Self-hosting	1	565	September 10, 2020
Configure Discourse to use a separate PostgreSQL server Self-Hosting how-to	53	30814	October 21, 2026
Postgres Errors on Rebuild Self-hosting	2	1735	September 16, 2015
Install the docker version with a remote postgresql Self-hosting	8	3800	February 23, 2017
Moving to New Server woes Product Support	16	616	March 10, 2025

Moving postgres db to central db server: build error

Related topics