Out of nowhere, Discourse is no longer wanting to run and is not even rebuilding using ./launcher rebuild app. I commented out all plugins too. Here is the logs when I try to start it: https://codefile.io/f/8XUuOqyEDd Here are the logs when I use ./launcher rebuild app. I see something about “fail…

Yes, I did try to change after I saw the error. So, would I do rm /var/discourse/shared/standalone/postgres_data/postmaster.pid ? to delete the lockfile then try to rebuild Also thank you for helping me with this

[이미지] joshhabka: failed listening on port 6379 (TCP) I don’t think it’s related to your issue. This warning often (always?) appear during a rebuild. error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused I think your issue more likely comes fr…

This might give clues: [이미지] Cannot rebuild app, Support socat[33] E connect(, AF=1 “/shared/postgres_run/.s.PGSQL.5432”, 36): Connection refused Based on that error, it appears the database did not shut down cleanly when you stopped the app container. …

Would this be what is causing it to not work when I run it(without doing any ./launcher rebuild app)?

I stopped all other services on my server and updated to the latest Ubuntu LTS and it still shows this: PG::ConnectionBad: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: Connection refused (PG::ConnectionBad) Is the server running locally and accepting connection…

Swapping templates with 13 and even 15 did not solve the issue, which is what was shown in the referenced post. Caused by: PG::ConnectionBad: connection to server on socket “/var/run/postgresql/.s.PGSQL.5432” failed: No such file or directory (PG::ConnectionBad) Is the server running locally and …

[이미지] joshhabka: Here is the logs when I try to start it: https://codefile.io/f/8XUuOqyEDd timeout: down: postgres: 1s, normally up, want up Seems like the database isn’t starting up correctly. The logs show it appears to occasionally start up properly, but only for a short time, so that c…

Did you do the PostgreSQL 15 update I too think it’s about an unclean shutdown. If you’ve got a backup, what I would do is spin up a new vm and restore it. You can follow Move a Discourse site to another VPS with rsync and exclude postgres_*. The alternative, which is your only option if you don’t…

How can I access my backups if my forum is down(as in I cannot go to admin settings and download a backup)? I also did not try to migrate anything, I have been using it as normal and updating via the web ui? Why would the database have an unclean shutdown??

[이미지] mwaniki: tail -f shared/standalone/log/var-log/postgres/current I will provide the Postgres logs, one second

2025-03-22 00:30:44.110 UTC [4922] FATAL: lock file “postmaster.pid” is empty 2025-03-22 00:30:44.110 UTC [4922] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash. 2025-03-22 00:30:45.127 UTC [4964] FATAL: lock file “postmaster.pid” is e…

Discourse가 무작위로 실행되지 않거나 다시 빌드되지 않음

지원 자체 호스팅

Canapin (Coin-coin le Canapin) 3월 20, 2025, 10:17오후 4

This might give clues:

글		댓글	조회수
Newest Discourse Version breaks rebuild, Redis Port already in use Self-hosting	7	1498	12월 2, 2020
Error when starting Discourse, Redis port already in use Self-hosting	10	1301	5월 20, 2019
Moving to New Server woes Support	16	482	3월 10, 2025
Cannot rebuild app, Support	2	210	2월 3, 2025
Discourse update doesn't wait for Postgress DB to shut down Self-hosting	4	1186	12월 29, 2021

Discourse가 무작위로 실행되지 않거나 다시 빌드되지 않음

Related topics