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

제품 지원 자체 호스팅
1 
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:  shutting down
118:M 20 May 2023 18:50:24.060 # User requested shutdown...
118:M 20 May 2023 18:50:24.060 * Saving the final RDB snapshot before exiting.
118:M 20 May 2023 18:50:24.066 * DB saved on disk
118:M 20 May 2023 18:50:24.067 # Redis is now ready to exit, bye bye...
2023-05-20 18:50:24.068 UTC [57] LOG:  database system is shut down

시스템에서 이러한 오류가 발생하며 작동하지 않습니다.

2

더 자세한 내용을 알려 주실 수 있을까요? 그 전에 어떤 일이 일어나고 있나요?

3 
이 조언을 끄려면 config 변수 advice.detachedHead를 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 -- : > install -d -m 0755 -g root -o root $LETSENCRYPT_DIR
I, [2023-05-20T18:50:20.325079 #1]  INFO -- : 
I, [2023-05-20T18:50:20.325219 #1]  INFO -- : > cd /root/acme.sh && LE_WORKING_DIR="${LETSENCRYPT_DIR}" ./acme.sh --install --log "${LETSENCRYPT_DIR}/acme.sh.log"
I, [2023-05-20T18:50:21.265616 #1]  INFO -- : [Sat 20 May 2023 06:50:20 PM UTC] Installing to /shared/letsencrypt
[Sat 20 May 2023 06:50:20 PM UTC] Installed to /shared/letsencrypt/acme.sh
[Sat 20 May 2023 06:50:20 PM UTC] Installing alias to '/root/.profile'
[Sat 20 May 2023 06:50:20 PM UTC] OK, Close and reopen your terminal to start using acme.sh
[Sat 20 May 2023 06:50:20 PM UTC] Installing cron job
[Sat 20 May 2023 06:50:20 PM UTC] Good, bash is found, so change the shebang to use bash as preferred.
[Sat 20 May 2023 06:50:21 PM UTC] OK

I, [2023-05-20T18:50:21.265799 #1]  INFO -- : > cd /root/acme.sh && LE_WORKING_DIR="${LETSENCRYPT_DIR}" ./acme.sh --upgrade --auto-upgrade
I, [2023-05-20T18:50:23.925000 #1]  INFO -- : [Sat 20 May 2023 06:50:21 PM UTC] Installing from online archive.
[Sat 20 May 2023 06:50:21 PM UTC] Downloading https://github.com/acmesh-official/acme.sh/archive/master.tar.gz
[Sat 20 May 2023 06:50:22 PM UTC] Extracting master.tar.gz
[Sat 20 May 2023 06:50:22 PM UTC] Installing to /shared/letsencrypt
[Sat 20 May 2023 06:50:22 PM UTC] Installed to /shared/letsencrypt/acme.sh
[Sat 20 May 2023 06:50:22 PM UTC] Good, bash is found, so change the shebang to use bash as preferred.
[Sat 20 May 2023 06:50:23 PM UTC] OK
[Sat 20 May 2023 06:50:23 PM UTC] Install success!
[Sat 20 May 2023 06:50:23 PM UTC] Upgrade success!

I, [2023-05-20T18:50:23.925858 #1]  INFO -- : > cd /root/acme.sh && LE_WORKING_DIR="${LETSENCRYPT_DIR}" ./acme.sh --set-default-ca  --server  letsencrypt
I, [2023-05-20T18:50:23.976164 #1]  INFO -- : [Sat 20 May 2023 06:50:23 PM UTC] Changed default CA to: https://acme-v02.api.letsencrypt.org/directory

I, [2023-05-20T18:50:23.980913 #1]  INFO -- : File > /etc/nginx/letsencrypt.conf  chmod:   chown: 
I, [2023-05-20T18:50:23.988140 #1]  INFO -- : File > /etc/runit/1.d/letsencrypt  chmod: +x  chown: 
I, [2023-05-20T18:50:23.989411 #1]  INFO -- : Replacing (?-mix:ssl_certificate.+) with ssl_certificate /shared/ssl/$$ENV_DISCOURSE_HOSTNAME.cer;
ssl_certificate /shared/ssl/$$ENV_DISCOURSE_HOSTNAME_ecc.cer;
 in /etc/nginx/conf.d/discourse.conf
I, [2023-05-20T18:50:23.990713 #1]  INFO -- : Replacing (?-mix:#?ACCOUNT_EMAIL=.+) with ACCOUNT_EMAIL=$$ENV_LETSENCRYPT_ACCOUNT_EMAIL
 in /shared/letsencrypt/account.conf
I, [2023-05-20T18:50:23.991830 #1]  INFO -- : Replacing (?-mix:ssl_certificate_key.+) with ssl_certificate_key /shared/ssl/$$ENV_DISCOURSE_HOSTNAME.key;
ssl_certificate_key /shared/ssl/$$ENV_DISCOURSE_HOSTNAME_ecc.key;
 in /etc/nginx/conf.d/discourse.conf
I, [2023-05-20T18:50:23.992752 #1]  INFO -- : Replacing (?-mix:add_header.+) with add_header Strict-Transport-Security 'max-age=63072000'; in /etc/nginx/conf.d/discourse.conf
I, [2023-05-20T18:50:23.993416 #1]  INFO -- : Replacing location @discourse { with location @discourse {
add_header Strict-Transport-Security 'max-age=31536000'; # remember the certificate for a year and automatically connect to HTTPS for this domain in /etc/nginx/conf.d/discourse.conf
I, [2023-05-20T18:50:23.994599 #1]  INFO -- : > echo "Beginning of custom commands"
I, [2023-05-20T18:50:23.998577 #1]  INFO -- : Beginning of custom commands

I, [2023-05-20T18:50:23.999094 #1]  INFO -- : > echo "End of custom commands"
I, [2023-05-20T18:50:24.002961 #1]  INFO -- : End of custom commands

I, [2023-05-20T18:50:24.006766 #1]  INFO -- : Terminating async processes
I, [2023-05-20T18:50:24.007874 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 57
I, [2023-05-20T18:50:24.008783 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 118
118:signal-handler (1684608624) Received SIGTERM scheduling shutdown...
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:  shutting down
118:M 20 May 2023 18:50:24.060 # User requested shutdown...
118:M 20 May 2023 18:50:24.060 * Saving the final RDB snapshot before exiting.
118:M 20 May 2023 18:50:24.066 * DB saved on disk
118:M 20 May 2023 18:50:24.067 # Redis is now ready to exit, bye bye...
2023-05-20 18:50:24.068 UTC [57] LOG:  database system is shut down
sha256:d0eaff2960589e6490608fa882bddaf493748f1b847d7006cae16765012af258
755217c749f30ea4e76a5d8b2493cf299cd2b598f6274255d5b88b045c3de430

`
4

데이터베이스 시스템이 일부 커스텀 명령을 실행한 후 종료되고 있는 것으로 보입니다. 이 오류는 데이터베이스에 문제가 있음을 의미하는 것 같습니다. (수정됨)
(아니면 완벽히 정상일 수도 있나요?)
기타 출처: LOG: database system is shut down. How to fix it - #2 by itsbhanusharma

5

이것은 재빌드가 성공했을 때의 출력입니다. 그래도 작동하지 않는다면 전체 로그가 필요합니다.

6

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