2023-05-20 18:50:24.008 UTC [57] LOG: received fast shutdown request 2023-05-20 18:50:24.016 UTC [57] LOG: aborting any active transactions 2023-05-20 18:50:24.026 UTC [57] LOG: background worker "logical replication launcher" (PID 66) exited with exit code 1 2023-05-20 18:50:24.027 UTC [61] LOG:…

After checking @Wleksion server the problem was caused by a faulty DNS configuration and multiple rebuilds triggering the Let’s Encrypt Rate Limit.

Could you provide more details? What’s happening before that?

Turn off this advice by setting config variable advice.detachedHead to false I, [2023-05-20T18:50:20.309089 #1] INFO -- : I, [2023-05-20T18:50:20.309217 #1] INFO -- : > touch /var/spool/cron/crontabs/root I, [2023-05-20T18:50:20.316069 #1] INFO -- : I, [2023-05-20T18:50:20.316703 #1] INFO -- …

It appears that your database system is being shut down after executing some custom commands. I think this error means that there is an issue with your database. (edited) (or it could be perfectly fine?) Other sources: LOG: database system is shut down. How to fix it - #2 by itsbhanusharma

That’s the output of a successful rebuild. We need the full logs if it’s not working after that.

이 오류가 발생하고 있습니다

제품 지원 자체 호스팅

Falco (Falco) 5월 23, 2023, 7:58오후 6

@Wleksion 서버를 확인한 결과, 문제는 잘못된 DNS 구성과 여러 번의 재빌드로 인해 Let’s Encrypt 속도 제한이 발동되면서 발생했습니다.

Discourse does not work

글		댓글	조회수
"User requested shutdown" every time I run `./launcher rebuild app` although I never request shutdown Self-hosting	1	700	6월 24, 2019
Database shut down error at the end of discourse docker setup Self-hosting	6	1736	9월 17, 2020
Database system was not properly shut down error when rebuilding Self-hosting	3	7087	9월 19, 2019
LOG: database system is shut down. How to fix it Product Support	8	3193	1월 30, 2019
Upgrade failed due to unclean database shutdown Self-hosting	20	4463	12월 30, 2016

이 오류가 발생하고 있습니다

Related topics