Doing the newest update (incl. postgresql) result in an error: root@community:/var/discourse# ./launcher rebuild app Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 60 app app cd /pups && git pull && /pups/bin/pups --std…

Running chown -R postgres postgres_data at /shared after entering the docker container has fixed it.

[圖片] noezDE: https://meta.discourse.org/t/postgresql-12-update/151236 Did you review this post?

[圖片] RiversideRocks: [圖片] noezDE: https://meta.discourse.org/t/postgresql-12-update/151236 Yes, i did it before. We couldnt get the update running.

[圖片] noezDE: The source cluster was not shut down cleanly. Read the entire faq section here: [圖片] PostgreSQL 12 update FAQ The source cluster was not shut down cleanly If you get a upgrade failed with the above message, you can try a simpler approach to get it back into a better state.

Already tried the workaround but it did not work.

The log is full of: 2020-06-03 16:01:21.074 UTC [693] FATAL: data directory “/shared/postgres_data” has wrong ownership 2020-06-03 16:01:21.074 UTC [693] HINT: The server must be started by the user that owns the data directory.

After loggin into the container i tried to shutdown it by myself: root@community-app:/etc/postgresql/10/main# service postgresql stop [FAIL] Stopping PostgreSQL 10 database server: main[…] Error: Config owner (postgres:106) and data owner (Debian-exim:105) do not match, and config owner is not roo…

更新失败 (postgresql)

支持安装

Falco (Falco) 2020年六月3日 16:04 4

在此处阅读整个常见问题解答部分：

話題		回覆	觀看
Upgrade of postgres failed Self-hosting	1	1168	2020年九月25日
PostgreSQL 13 update from PostgreSQL 10 fails Self-hosting	10	2706	2021年十月13日
Rebuild fails: Data directory /shared/postgres_data must not be owned by root Self-hosting	4	728	2025年二月5日
Trouble with postgre（maybe） Self-hosting	5	1796	2020年八月13日
Postgres upgrade success loop due to prior postgres 8 to 10 migration Self-hosting	3	1258	2020年五月26日

更新失败 (postgresql)

相關主題