discourse dev 설치로 인해 redis가 손상되었습니다

NubeBuster · 3월 20, 2024, 2:02오후

다른 프로젝트들을 위해 Redis를 설치하고 설정해 두었습니다. 현재 서버가 시작되지 않습니다. 서버를 시작하면 즉시 종료됩니다. 로그에는 다음과 같이 표시됩니다.

#User requested shutdown…

이것이 Discourse 때문일까요? (Redis가 dev Discourse 설치 후 깨졌으므로 99.99% 확신합니다) Discourse가 제 Redis 서버를 종료하는 것을 어떻게 막을 수 있을까요?

현재 제 환경에서는 Discourse 서버가 실행되지 않고 있습니다.

923:M 20 Mar 2024 13:25:47.359 * Background saving terminated with success
923:M 20 Mar 2024 13:29:16.773 * User requested shutdown...
923:M 20 Mar 2024 13:29:16.773 * Saving the final RDB snapshot before exiting.
923:M 20 Mar 2024 13:29:16.958 * DB saved on disk
923:M 20 Mar 2024 13:29:16.959 * Removing the pid file.
923:M 20 Mar 2024 13:29:16.959 # Redis is now ready to exit, bye bye...
919:C 20 Mar 2024 13:30:00.782 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures withou>
919:C 20 Mar 2024 13:30:00.782 # systemd supervision requested or auto-detected, but Redis is compiled without libsystemd support!
951:C 20 Mar 2024 13:30:00.783 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
951:C 20 Mar 2024 13:30:00.783 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=951, just started
951:C 20 Mar 2024 13:30:00.783 * Configuration loaded
951:M 20 Mar 2024 13:30:00.784 * Increased maximum number of open files to 10032 (it was originally set to 1024).
951:M 20 Mar 2024 13:30:00.784 * monotonic clock: POSIX clock_gettime
951:M 20 Mar 2024 13:30:00.787 # Failed to write PID file: No such file or directory
951:M 20 Mar 2024 13:30:00.787 * Running mode=standalone, port=6379.
951:M 20 Mar 2024 13:30:00.788 * Server initialized
951:M 20 Mar 2024 13:30:00.790 * Loading RDB produced by version 7.2.4
951:M 20 Mar 2024 13:30:00.790 * RDB age 44 seconds
951:M 20 Mar 2024 13:30:00.790 * RDB memory usage when created 41.01 Mb
951:M 20 Mar 2024 13:30:00.813 * User requested shutdown...
951:M 20 Mar 2024 13:30:00.813 * Removing the pid file.
951:M 20 Mar 2024 13:30:00.813 # Redis is now ready to exit, bye bye...

NubeBuster · 3월 20, 2024, 2:18오후

다음 내용을 되돌렸습니다.

github.com/discourse/install-rails

linux

132883708


      
              wget https://download.redis.io/redis-stable.tar.gz && \
              tar -xzvf redis-stable.tar.gz && \
              cd redis-stable && \
              make && \
              sudo -E make install
            cd /tmp && \
              rm redis-stable.tar.gz && \
              rm -Rf redis-stable
          
            sudo adduser --system --group --no-create-home redis
            FILE="/etc/systemd/system/redis-server.service"
            if [ ! -f "$FILE" ]; then
              sudo bash -c "cat > $FILE" <<EOF
          [Unit]
          Description=redis in-memory data store
          After=network.target
          
          [Service]
          User=redis
          Group=redis
          ExecStart=/usr/local/bin/redis-server /etc/redis/redis.conf

아래 명령어를 사용했습니다.

sudo systemctl stop redis-server
sudo rm /etc/systemd/system/redis-server.service
sudo systemctl daemon-reload
sudo systemctl enable redis-server
sudo systemctl start redis-server
sudo systemctl status redis-server
redis-cli ping

글		댓글	조회수
Redis trouble: "Job exception: MISCONF Redis is configured to save RDB snapshots..." Self-hosting	0	1479	3월 1, 2022
Error connecting to Redis Self-hosting	17	7413	3월 21, 2023
Install fails because of other Redis container? Self-hosting	1	1250	4월 5, 2020
Error setting up with separate Redis Self-hosting	5	887	4월 7, 2023
Error when starting Discourse, Redis port already in use Self-hosting	10	1410	5월 20, 2019

discourse dev 설치로 인해 redis가 손상되었습니다

Related topics