I, [2025-08-23T07:21:01.134641 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'find /var/www/discourse/vendor/bundle -name cache -not -path "*/gems/*" -type d -exec rm -rf {} +' I, [2025-08-23T07:21:02.162053 #1] INFO -- : I, [2025-08-23T07:21:02.162765 #1] INFO -- : > cd /var/www/disc…

The thing that got the site back up, after the data container was gone, was to edit data.yml and change the template to the postgres13 templet and then rebuild the data container, then it was possible to start up the data container, destroy and start the web_only container (it won’t connect to a dif…

Hi there, does this help? [imagem] Upgrade to latest release failed 8/21/25 Self-hosting Cause The migration tries to upgrade the “vector” extension. The PostgreSQL user running the migration (e.g. discourse) must be the owner of the extension, but it’s owned …

That doesn’t make sense to me. I’m running the shell from Digital Ocean as I always do, never had an issue with ownership. Here’s another try. root@www:/var/discourse# ./launcher bootstrap web_only && ./launcher destroy web_only && ./launcher start web_only WARNING: Docker version 24.0.2 deprecate…

./launcher rebuild data fails with Upgrading PostgreSQL from version 13 to 15 ------------------------------------------------------------------------------------- WARNING: Upgrading PostgreSQL would require an additional 14G of disk space Please free up some space, or expand your disk, before con…

I’ve always just increased totally space, nothing else. Sure, big guys can do differently. You’ve propably already done ./launcher cleanup and destroyed old images.

I’ve got 90GB now, but it’s still failing on the PostgreSQL upgrade. fixing permissions on existing directory /var/lib/postgresql/13/main ... ok creating subdirectories ... ok selecting dynamic shared memory implementation ... posix selecting default max_connections ... 100 selecting default shared…

I looked at PostgreSQL 15 update but didn’t find anything that clearly addressed my problem.

root@www:/var/discourse# ./launcher start app WARNING: Docker version 24.0.2 deprecated, recommend upgrade to 24.0.7 or newer. x86_64 arch detected. ERROR: containers/app.yml does not exist or is not readable. Available configs ( data, mail-receiver, web_only ) root@www:/var/discourse#

root@www:/var/discourse# ./discourse-doctor DISCOURSE DOCTOR Sat Aug 23 20:24:54 UTC 2025 OS: Linux www 5.15.0-152-generic #162-Ubuntu SMP Wed Jul 23 09:48:42 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux YML=web_only.yml Found containers/web_only.yml ==================== YML SETTINGS =================…

This is a permission issue on Postgres. You need to manually enter the database and install or update the vector extension. More help here [imagem] Build error: permission denied to create extension "vector" Support Hi, I’m having problems rebuilding my…

I’m not sure how to get into PostgreSQL. Following came from @pfaffman in Update = ☠ - #37 by pfaffman : root@www:/var/discourse# ./launcher start web_only WARNING: Docker version 24.0.2 deprecated, recommend upgrade to 24.0.7 or newer. x86_64 arch detected. starting up existing container + /usr/…

Atualização falhando

Suporte Instalação

NateDhaliwal (Nate Dhaliwal) 23 Agosto , 2025 07:34 2

Olá, isso ajuda?

Tópico		Respostas	Vistas
PostgreSQL 15 update Announcements	107	6470	22 Outubro , 2025
Update from 2.9.0 beta2 to beta4 failed (my site is down) Self-hosting	25	1920	12 Maio , 2022
Update Not Completed and Discourse not opening Self-hosting	16	592	17 Junho , 2024
Discourse AI plugin failing container rebuilds/bootstrappings Self-hosting two-container , ai	7	256	9 Agosto , 2024
Rebuild fails: Data directory /shared/postgres_data must not be owned by root Self-hosting	4	649	5 Fevereiro , 2025

Atualização falhando

Related topics