Hello everyone, I’m running into an issue with PostgreSQL startup issue when I tried to rebuild my app, and I’m hoping to get some help. Here’s the log, it has been stuck on this status for more than 30 mins. Status: Image is up to date for discourse/base:2.0.20240825-0027 docker.io/discourse/bas…

@here It looks like older versions of Docker is incompatible with the newer Docker image which we have released. Here are the steps to fix the problem: apt update apt install docker.io cd /var/discourse ./launcher rebuild app I’ve also bumped our launcher script to abort if we do not at least de…

Having the same issue… DO Droplet on Ubuntu 20.04. Tried to Upgrade Docker from within Discourse first but it kept getting an error code 137. So then I tried to rebuild Discourse from the command line and it hung on The database is ready to accept connections. Ctrl+C wouldn’t do anything so clos…

Error 137 is out of memory. I would try adding more swap. If you have only 1gb of ram I might resize to 2gb and perhaps also have 3 or 4 gb of swap. You might try a ./launcher start app But I suspect that the database has migrated too far for the old container. If you’re stuck and want paid supp…

Hello, same error here. Workaround for now is to force version param in app.yml to v3.3.0. Arch AMD64, Ubuntu 18.04. Strange that a minor version failed, update to v3.3.0 passed without problem last week :neutral_face:

For anyone running into this problem and am comfortable giving me access to your server, please PM me so that I can debug the problem on a server that has the problem. I have tried multiple ways and cannot reproduce this problem which makes it harder to push a fix.

I don’t see a way in my profile to PM you…

You need to be at trust level 1 to send messages [이미지] Understanding Discourse Trust Levels Get to trust level 1 by… Entering at least 5 topics Reading at least 30 posts Spend a total of 10 minutes reading posts Looking at the stats in your profile, you’re pretty close already

For anyone that is stuck with this issue with Discourse down, I’ve found you can at least get the old version of the forum up by restarting the VM and then running ./launcher start app. This command won’t work after attempting a rebuild without restarting your instance / VM. I should be able to bum…

Ctrl+c doesn’t work when it is stuck, have to reboot system.

This command also doesn’t do anything. **/var/discourse**# ./launcher start app x86_64 arch detected. WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.yml + /usr/bin/docker run --shm-size=512m -d --restart=always -e LANG=en_US.UT…

I’ve another forum on another droplet and that doesn’t give any issue with updating. It is weird why with same server configuration one droplet has issues while other doesn’t?

PostgreSQL 재빌드 중 멈춤

제품 지원 자체 호스팅

Moin 8월 30, 2024, 12:13오후 29

메시지를 보내려면 신뢰 수준 1이 필요합니다

프로필의 통계를 보면 이미 거의 다 된 것 같습니다

글		댓글	조회수
Forum Full Crash (Test Pressing) Self-hosting	8	525	9월 4, 2024
Stuck on update Self-hosting	2	344	9월 4, 2024
Update Error Self-hosting	6	328	8월 30, 2024
Issue with rebuilding Self-hosting	2	104	9월 15, 2026
Postgres Errors on Rebuild Self-hosting	2	1734	9월 16, 2015

PostgreSQL 재빌드 중 멈춤

Related topics