I run Discourse on Debian 11 with Docker as a single container. I tried to update it using ./launcher rebuild app It fails with this message I, [2023-01-04T20:53:09.920876 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' rake aborted! I do not find a way to…

I was able to set the version to 2.9.0.beta2 (commit id: 88a8584348ed93a28286839bfc1c32b06bd50b3f) by setting the commit id as “version” in app.yml. This time the upgrade worked. After that I was able to upgrade to 3.0.0.beta16. Thanks to all.

I see that the owner is wrong drwxr-xr-x 15 sshd netdev 4096 Jan 4 21:43 . drwxr-xr-x 3 root root 4096 Jan 3 2018 .. drwxr-xr-x 3 1000 www-data 4096 Jan 3 2018 backups drwxr-xr-x 8 sshd netdev 4096 Feb 2 2…

This isn’t the error, it’s going to be higher up, we’re going to need to see more of the log.

2023-01-04 20:48:05.355 UTC [41] LOG: starting PostgreSQL 13.9 (Debian 13.9-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit 2023-01-04 20:48:05.377 UTC [41] LOG: listening on IPv4 address "0.0.0.0", port 5432 2023-01-04 20:48:05.377 UTC [41] LOG: lis…

Inside the container I try to start the service postgresql and get an error. root@server /var/discourse # ./launcher enter app x86_64 arch detected. root@discourse:/var/www/discourse# service postgresql start [FAIL] Starting PostgreSQL 13 database server: main[....] Error: Config owner (postgres:10…

If you have changed owners of the files inside the shared folder you will break the install. One option is reinstalling and restoring a backup, while the other is manually fixing those owners.

@Falco : thank you! I changed the owners after the upgrade failed. I found the chown hint somewhere in a post. How can I create a backup in the current state? How can I fix the owners manually? Thanks again!

inside the container I tried discourse backup. It reports that Redis is not running. In the “current” Redis log I found the following lines at the end… 10316:M 05 Jan 2023 08:05:27.314 # Server initialized 10316:M 05 Jan 2023 08:05:27.314 # WARNING overcommit_memory is set to 0! Background save may…

I fixed the permissions like this (inside the container): [grafik] Afterwards I restarted the container with ./launcher restart app Now I can access Discourse. But it’s the old version 2.8.3 that I tried to upgrade to 3.0.0.beta16 yesterday. I’m not sure how to proceed to upgrade Discourse.

I think my problem is related to this thread: Problem upgrading multi-site/multi-containers Discourse instance - #5 by jtraulle I remember that I had upgrade problems before but never investigated them.

[이미지] Ingo Karstein: I’m not sure how to proceed to upgrade Discourse. ./launcher rebuild app

업그레이드 실패

제품 지원 자체 호스팅

Stephen (Stephen) 1월 4, 2023, 9:17오후 3

이건 에러가 아닙니다. 더 위쪽에서 발생했을 가능성이 크니 로그를 더 많이 확인해야 합니다.

글		댓글	조회수
Failed web upgrade Self-hosting	18	1373	12월 1, 2022
Rebuild fails: Data directory /shared/postgres_data must not be owned by root Self-hosting	4	759	2월 5, 2025
Failing update Self-hosting	32	1066	8월 26, 2025
Site keeps stopping since upgrade Self-hosting	1	481	4월 10, 2023
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2387	11월 26, 2021

업그레이드 실패

Related topics