# 개발용 Ubuntu 또는 Debian에 Discourse 설치하기
**URL:** https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727
**Category:** Developer Guides
**Tags:** dev-install, how-to
**Created:** [4월 12, 2014, 10:22오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727 "2014-04-12T22:22:07Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [10월 20, 2024, 11:16오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/687 "2024-10-20T23:16:57Z")
> [@darkpixlz](#):
>
> 아직도 postgres를 실행하지 못하겠습니다.
```plaintext
❯ sudo -i -u postgres
[sudo] password for scossar:
[postgres@rocknosh ~]$
```
postgres 프롬프트에 다음을 입력하세요:
```plaintext
initdb --locale en_US.UTF-8 -D /var/lib/postgres/data
exit
```
그런 다음 커맨드 라인에서:
```plaintext
# postgresql 서비스 활성화 및 시작
sudo systemctl enable postgresql
sudo systemctl start postgresql
# 현재 사용자를 postgres 그룹에 추가
# -a 플래그는 현재 사용자($USER)를 postgres 그룹(-G postgres)에 추가합니다
sudo usermod -aG postgres "$USER"
# 사용자 이름으로 postgresql 슈퍼유저 생성
sudo -u postgres createuser -s "$USER"
```
---
### Author:  [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [10월 20, 2024, 11:19오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/688 "2024-10-20T23:19:44Z")
감사합니다. 해결되었습니다. Rails에서 db create 작업을 root 권한으로 실행하면 안 되나요? root로 실행하면 `FATAL: role "root" does not exist (PG::ConnectionBad)` 오류가 발생하고, root가 아니면 권한 오류인 `LoadError: cannot load such file -- /usr/lib/ruby/gems/3.3.0/gems/colored2-4.0.0/lib/colored2.rb (LoadError)`가 나옵니다.
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [10월 20, 2024, 11:24오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/689 "2024-10-20T23:24:12Z")
> [@darkpixlz](#):
>
> Rails에서 db create 태스크를 root로 실행하지 않는 것이 맞나요?
아니요, 일반 사용자로 실행해야 합니다:
```plaintext
❯ bin/rails db:create
❯ bin/rails db:migrate
```
`colored2` 젬과 관련된 오류는 해당 젬이 누락되었음을 시사합니다.
`rake db:create`를 실행하기 전에 `bundle install`을 실행했는지 확인해 주세요.
---
### Author:  [@kuaza](https://meta.discourse.org/u/kuaza)
#### Post date: [10월 22, 2024, 7:53오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/690 "2024-10-22T19:53:19Z")
이런 화면이 표시되면 다음 명령을 실행하세요:
`bin/rails db:migrate`를 실행하면 문제가 해결됩니다.
이 플러그인을 설치했을 때 이 오류를 겪었고, 해결책을 고민한 지 이틀째 되던 날 갑자기 마이그레이션을 실행해야 한다는 생각이 떠올랐습니다…
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [10월 24, 2024, 11:10오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/691 "2024-10-24T11:10:43Z")
설치 파일에서 설치할 항목들을 복사해서 붙여넣는 중입니다.
다음과 같은 부분이 있습니다:
```plaintext
log_info "Installing image utilities ..."
sudo -E apt-get -y install advancecomp gifsicle jpegoptim libjpeg-progs optipng pngcrush pngquant
sudo -E apt-get -y install jhead
# Install oxipng
cd /tmp && \
wget https://github.com/shssoichiro/oxipng/releases/download/v8.0.0/oxipng-8.0.0-x86_64-unknown-linux-musl.tar.gz && \
tar -xzvf oxipng-8.0.0-x86_64-unknown-linux-musl.tar.gz && \
sudo cp oxipng-8.0.0-x86_64-unknown-linux-musl/oxipng /usr/local/bin
cd /tmp && \
rm oxipng-8.0.0-x86_64-unknown-linux-musl.tar.gz && \
rm -Rf oxipng-8.0.0-x86_64-unknown-linux-musl
```
이 내용을 실행한 후에도 여전히 `/tmp` 디렉터리에 있습니다. 여기서 빠져나와야 하는지, 아니면 나머지 설치 작업을 여기서 계속 진행해야 하는지 궁금합니다. `/tmp`에서 설치를 진행했는데, 이것이 올바른 방식이었나요? 파일을 전체로 실행하면 여전히 해당 디렉터리에서 설치될 것이라고 가정했습니다.
수정: Ruby가 설치되었습니다.
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [10월 24, 2024, 5:19오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/692 "2024-10-24T17:19:54Z")
> [@NateDhaliwal](#):
>
> `log_info "Installing image utilities ..."`
해당 줄 바로 앞 섹션에서는 pacman으로 `imagemagick`를 설치하세요. `libtool` 설치 명령은 무시해도 된다고 확신합니다:
```plaintext
❯ sudo pacman -S imagemagick
```
그 다음, 이미지 유틸리티 섹션의 대부분의 패키지는 다음 명령으로 설치할 수 있습니다:
```plaintext
❯ sudo pacman -S gifsicle jpegoptim libjpeg-turbo optipng pngcrush pngquant jhead
```
`advancecomp`는 Arch 메인 리포지토리에 없습니다. AUR의 이 패키지로 설치할 수 있습니다:
```plaintext
https://aur.archlinux.org/advancecomp-git.git
```
`oxipng`는 Arch 메인 리포지토리에 있으므로 스크립트의 `cd /tmp` 명령은 무시하고 다음만 실행하세요:
```plaintext
❯ sudo pacman -S oxipng
```
스크립트에서 조금 더 아래를 보면, `mailhog`은 AUR를 통해 사용할 수 있습니다:
```plaintext
https://aur.archlinux.org/mailhog-bin.git
```
다른 컴퓨터에서 Discourse를 설정하게 되면 다시 테스트하여 전체 가이드를 작성하겠습니다. 실제로는 Ubuntu에서 Discourse를 설치하는 것보다 약간 더 쉽습니다. 모든 패키지가 메인 리포지토리에 있거나 AUR에서 사용할 수 있기 때문입니다. 지금은 어디서 막히는지 알려주세요.
아마도 이 게시물들은 다른 토픽으로 이동할 수 있을까요?
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [10월 24, 2024, 11:06오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/693 "2024-10-24T23:06:52Z")
Ruby를 `/tmp`에 설치했어요. 괜찮을까요?
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [10월 24, 2024, 11:36오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/694 "2024-10-24T23:36:16Z")
> [@NateDhaliwal](#):
>
> Ruby를 `/tmp`에 설치했습니다.
Arch가 `/tmp` 디렉토리를 어떻게 처리하는지 정확히 모르겠습니다. systemd 작업에 의해 주기적으로 정리되는 것 같습니다. `/tmp` 디렉토리는 임시 파일을 위한 것입니다.
Ruby를 `~/` 디렉토리로 이동시키면 될 것 같습니다.
Arch에서 Ruby를 설치하는 과정은 다른 시스템에서 설치하는 것보다 다소 복잡했습니다. 저는 Rbenv를 통해 설치했습니다: [rbenv - ArchWiki](https://wiki.archlinux.org/title/Rbenv). rbenv로 ruby 버전을 설치하려면 [https://aur.archlinux.org/packages/ruby-build](https://aur.archlinux.org/packages/ruby-build) 도 설치해야 합니다.
그 과정을 건너뛰고 pacman으로 Ruby 패키지만 설치해도 될 것 같습니다: [Ruby - ArchWiki](https://wiki.archlinux.org/title/Ruby). 이렇게 하면 Ruby 3.3.5가 설치되는 것 같습니다. Discourse를 위해라면 충분할 것입니다.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [10월 25, 2024, 12:43오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/695 "2024-10-25T00:43:16Z")
더 명확하게 말해야 했어요: 저는 Pi에서 이 작업을 하고 있습니다.
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [10월 25, 2024, 1:54오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/696 "2024-10-25T01:54:44Z")
훌륭합니다! 아무것도 바뀌지 않을 것 같습니다. 컴퓨터에 영구적으로 설치하고 싶은 파일들은 `/tmp` 디렉터리에 두지 마세요. Ruby는 홈 디렉터리(`~/`)에서 정상적으로 실행될 것입니다.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [10월 25, 2024, 8:46오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/697 "2024-10-25T08:46:39Z")
> [@simon](#):
>
> `pacman`
`sudo apt install pacman`를 실행하여 설치하려고 했습니다. 그 다음 `pacman`이 실행 중인지 확인하기 위해 `pacman --help`를 입력했는데, 다음과 같은 메시지가 표시되었습니다:
```plaintext
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 45 (X_OpenFont)
Serial number of failed request: 27
Current serial number in output stream: 31
```
저는 리눅스와 명령줄에 익숙하지 않습니다.
---
### Author:  [@simon](https://meta.discourse.org/u/simon)
#### Post date: [10월 25, 2024, 9:05오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/698 "2024-10-25T09:05:46Z")
죄송합니다. 제가 아주 혼란스러웠습니다. 몇 개 위의 게시물에서 darkpixlz에게 답글을 달고 있는 줄 알았어요. 제 답글은 무시해 주세요. Arch Linux에만 관련이 있는 내용입니다.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [10월 25, 2024, 9:30오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/699 "2024-10-25T09:30:04Z")
다시 시도해 보고 있는데, 작동할 것 같아요.
---
### Author:  [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [10월 25, 2024, 10:21오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/700 "2024-10-25T10:21:28Z")
우연히 `/usr/games`에 설치된 건가요? ("X Error"를 고려하면, CLI 도구가 글꼴을 가져오려 할 이유는 없습니다…)
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [10월 25, 2024, 10:22오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/701 "2024-10-25T10:22:23Z")
그렇지 않다고 생각해요. 어쨌든, 이건 무관합니다(제가 올린 새로운 새 토픽을 참고하세요).
---
### Author:  [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [10월 25, 2024, 10:28오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/702 "2024-10-25T10:28:50Z")
방금 pi에서 확인해 보니, `pacman`은 게임인 것 같고, 패키지 매니저는 `pacman-package-manager`인 것 같습니다:
```plaintext
firepup650@firepi:~ $ apt search pacman 2>/dev/null|grep -e '^pacman' -1
pacman/stable,now 10-19+b1 arm64 [installed]
Chase Monsters in a Labyrinth
pacman-package-manager/stable,now 6.0.2-3 arm64 [installed]
Simple library-based package manager
pacman4console/stable,now 1.3-1+b4 arm64 [installed]
ncurses-based pacman game
firepup650@firepi:~ $
```
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [10월 27, 2024, 10:03오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/703 "2024-10-27T10:03:07Z")
> [@Discourse](#):
>
> images
이것은 어떤 모습이어야 하나요?
제가 보는 것은 `[ember-cli] ...[@embroider/webpack]` 문자열뿐입니다. 언젠가는 끝날까요?
수정:
이 오류도 보고 있습니다:
```plaintext
[ember-cli] ...[@embroider/webpack] D, [2024-10-27T18:11:10.974072 #18143] DEBUG -- : waiting 31.0s after suspend/hibernation Pipelining commands on a Redis instance is deprecated and will be removed in Redis 5.0.0. redis.multi do redis.get("key") end should be replaced by redis.multi do |pipeline| pipeline.get("key") end (called from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `public_send'} D, [2024-10-27T18:12:50.733620 #18143] DEBUG -- : waiting 31.0s after suspend/hibernation [ember-cli] ...[@embroider/webpack] [ember-cli] ...[@embroider/webpack] D, [2024-10-27T18:15:31.729849 #18143] DEBUG -- : waiting 31.0s after suspend/hibernation # 예외와 함께 종료되었습니다 (report_on_exception이 true): /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:58:in `block in _read_from_socket': 연결 시간 초과 (Redis::TimeoutError) /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `loop'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `_read_from_socket'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:47:in `gets'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:382:in `read'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:311:in `block in read'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:299:in `io'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:310:in `read'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `block in call'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:279:in `block (2 levels) in process'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:411:in `ensure_connected'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rack-mini-profiler-3.3.1/lib/mini_profiler/profiling_methods.rb:89:in `block in profile_method'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:270:in `block in send_command'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `synchronize'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `send_command'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/commands/hashes.rb:75:in `hget'에서 /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `public_send'에서 /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (3 levels) in '에서 /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:29:in `ignore_readonly'에서 /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (2 levels) in '에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/redis_store.rb:26:in `block in save'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/redis_store.rb:26:in `each'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/redis_store.rb:26:in `save'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/base_store.rb:223:in `report'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/logger.rb:167:in `report_to_store'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/defer_logger.rb:11:in `block in report_to_store'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/scheduler.rb:43:in `do_work'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/scheduler.rb:34:in `block (2 levels) in start_thread'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:58:in `block in _read_from_socket': Redis::TimeoutError (Redis::TimeoutError) /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `loop'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `_read_from_socket'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:47:in `gets'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:382:in `read'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:311:in `block in read'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:299:in `io'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:310:in `read'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `block in call'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:279:in `block (2 levels) in process'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:411:in `ensure_connected'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rack-mini-profiler-3.3.1/lib/mini_profiler/profiling_methods.rb:89:in `block in profile_method'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:270:in `block in send_command'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `synchronize'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `send_command'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/commands/hashes.rb:75:in `hget'에서 /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `public_send'에서 /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (3 levels) in '에서 /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:29:in `ignore_readonly'에서 /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (2 levels) in '에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/redis_store.rb:26:in `block in save'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/redis_store.rb:26:in `each'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/redis_store.rb:26:in `save'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/base_store.rb:223:in `report'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/logger.rb:167:in `report_to_store'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/defer_logger.rb:11:in `block in report_to_store'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/scheduler.rb:43:in `do_work'에서 /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/scheduler.rb:34:in `block (2 levels) in start_thread'에서
```
수정:
그리고 나서, 이것을 확인했습니다:
```plaintext
[ember-cli] ...[@embroider/webpack] D, [2024-10-27T18:21:32.809073 #18143] DEBUG -- : suspend/hibernation 후 31.0초 대기 중 [ember-cli] ...[@embroider/webpack] D, [2024-10-27T18:24:07.713356 #18143] DEBUG -- : suspend/hibernation 후 31.0초 대기 중 E, [2024-10-27T18:27:11.704108 #18143] ERROR -- : master loop 오류: 연결 시간 초과 (Redis::TimeoutError) E, [2024-10-27T18:27:11.768847 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:58:in `block in _read_from_socket' E, [2024-10-27T18:27:11.768930 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `loop' E, [2024-10-27T18:27:11.768979 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `_read_from_socket' E, [2024-10-27T18:27:11.769025 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:47:in `gets' E, [2024-10-27T18:27:11.769069 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:382:in `read' E, [2024-10-27T18:27:11.769145 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:311:in `block in read' E, [2024-10-27T18:27:11.769186 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:299:in `io' E, [2024-10-27T18:27:11.769222 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:310:in `read' E, [2024-10-27T18:27:11.769265 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `block in call' E, [2024-10-27T18:27:11.769297 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:279:in `block (2 levels) in process' E, [2024-10-27T18:27:11.769336 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:411:in `ensure_connected' E, [2024-10-27T18:27:11.769377 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process' E, [2024-10-27T18:27:11.769423 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging' E, [2024-10-27T18:27:11.769503 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process' E, [2024-10-27T18:27:11.769580 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call' E, [2024-10-27T18:27:11.769623 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rack-mini-profiler-3.3.1/lib/mini_profiler/profiling_methods.rb:89:in `block in profile_method' E, [2024-10-27T18:27:11.769667 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:270:in `block in send_command' E, [2024-10-27T18:27:11.769712 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `synchronize' E, [2024-10-27T18:27:11.769748 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `send_command' E, [2024-10-27T18:27:11.769792 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/commands/strings.rb:191:in `get' E, [2024-10-27T18:27:11.769831 #18143] ERROR -- : /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `public_send' E, [2024-10-27T18:27:11.769895 #18143] ERROR -- : /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (3 levels) in ' E, [2024-10-27T18:27:11.769940 #18143] ERROR -- : /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:29:in `ignore_readonly' E, [2024-10-27T18:27:11.769975 #18143] ERROR -- : /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (2 levels) in ' E, [2024-10-27T18:27:11.770020 #18143] ERROR -- : /home/natedhaliwal/discourse-f/app/jobs/regular/run_heartbeat.rb:16:in `last_heartbeat' E, [2024-10-27T18:27:11.770061 #18143] ERROR -- : /home/natedhaliwal/discourse-f/config/unicorn.conf.rb:191:in `check_sidekiq_heartbeat' E, [2024-10-27T18:27:11.770098 #18143] ERROR -- : /home/natedhaliwal/discourse-f/config/unicorn.conf.rb:278:in `master_sleep' E, [2024-10-27T18:27:11.770130 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/unicorn-6.1.0/lib/unicorn/http_server.rb:295:in `join' E, [2024-10-27T18:27:11.770179 #18143] ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/unicorn-6.1.0/bin/unicorn:128:in `' E, [2024-10-27T18:27:11.770217 #18143] ERROR -- : /home/natedhaliwal/discourse-f/bin/unicorn:93:in `load' E, [2024-10-27T18:27:11.770250 #18143] ERROR -- : /home/natedhaliwal/discourse-f/bin/unicorn:93:in `block in ' E, [2024-10-27T18:27:11.770292 #18143] ERROR -- : /home/natedhaliwal/discourse-f/bin/unicorn:92:in `fork' E, [2024-10-27T18:27:11.770326 #18143] ERROR -- : /home/natedhaliwal/discourse-f/bin/unicorn:92:in `' D, [2024-10-27T18:27:11.770480 #18143] DEBUG -- : suspend/hibernation 후 31.0초 대기 중 I, [2024-10-27T18:27:58.302988 #18143] INFO -- : 프로세스가 깨끗하게 종료되지 않아 강제 종료합니다. pid: 18423 Demon::Sidekiq # 예외와 함께 종료됨 (report_on_exception은 true): /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:58:in `block in _read_from_socket': 연결 시간 초과 (Redis::TimeoutError) from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `loop' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `_read_from_socket' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:47:in `gets' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:382:in `read' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:311:in `block in read' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:299:in `io' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:310:in `read' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `block in call' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:279:in `block (2 levels) in process' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:411:in `ensure_connected' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rack-mini-profiler-3.3.1/lib/mini_profiler/profiling_methods.rb:89:in `block in profile_method' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:270:in `block in send_command' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `synchronize' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `send_command' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/commands/sets.rb:131:in `smembers' from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `public_send' from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (3 levels) in ' from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:29:in `ignore_readonly' from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (2 levels) in ' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/redis_store.rb:329:in `get_patterns' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/pattern.rb:37:in `find_all' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/base_store.rb:188:in `block in report' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/cache.rb:13:in `fetch' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/base_store.rb:187:in `report' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/logger.rb:167:in `report_to_store' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/defer_logger.rb:11:in `block in report_to_store' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/scheduler.rb:43:in `do_work' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/scheduler.rb:34:in `block (2 levels) in start_thread' /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:58:in `block in _read_from_socket': Redis::TimeoutError (Redis::TimeoutError) from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `loop' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:54:in `_read_from_socket' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:47:in `gets' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:382:in `read' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:311:in `block in read' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:299:in `io' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:310:in `read' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `block in call' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:279:in `block (2 levels) in process' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:411:in `ensure_connected' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:269:in `block in process' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:356:in `logging' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:268:in `process' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/client.rb:161:in `call' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/rack-mini-profiler-3.3.1/lib/mini_profiler/profiling_methods.rb:89:in `block in profile_method' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:270:in `block in send_command' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `synchronize' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis.rb:269:in `send_command' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/commands/sets.rb:131:in `smembers' from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `public_send' from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (3 levels) in ' from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:29:in `ignore_readonly' from /home/natedhaliwal/discourse-f/lib/discourse_redis.rb:148:in `block (2 levels) in ' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/redis_store.rb:329:in `get_patterns' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/pattern.rb:37:in `find_all' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/base_store.rb:188:in `block in report' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/cache.rb:13:in `fetch' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/base_store.rb:187:in `report' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/logger.rb:167:in `report_to_store' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/defer_logger.rb:11:in `block in report_to_store' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/scheduler.rb:43:in `do_work' from /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/logster-2.20.0/lib/logster/scheduler.rb:34:in `block (2 levels) in start_thread' [ember-cli] ...[@embroider/webpack] I, [2024-10-27T18:28:06.724985 #19748] INFO -- : 프로세스 ID 19748에서 Sidekiq 로딩 중 [ember-cli] ...[@embroider/webpack]
```
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [10월 27, 2024, 1:41오후 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/704 "2024-10-27T13:41:17Z")
이것들은 오류가 아닙니다.
일부 Ember가 네이티브 JavaScript로 변환되는 과정을 포함하는 JavaScript 빌드 프로세스의 콘솔 로그입니다.
이것은 정상적인 진행 상황입니다.
이 시점에는 일반적으로 메모리와 CPU가 많이 사용되므로 시간이 좀 걸릴 수 있습니다.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [10월 28, 2024, 2:45오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/705 "2024-10-28T02:45:43Z")
@merefield 이건 어떨까요
> [@NateDhaliwal](#):
>
> ```plaintext
> ERROR -- : master loop error: Connection timed out (Redis::TimeoutError)
>
> ```
또는
> [@NateDhaliwal](#):
>
> ```plaintext
> ERROR -- : /home/natedhaliwal/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/redis-4.8.1/lib/redis/connection/ruby.rb:58:in `block in _read_from_socket'`
>
> ```
---
### Author:  [@gaoxue](https://meta.discourse.org/u/gaoxue)
#### Post date: [10월 28, 2024, 8:06오전 UTC](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727/706 "2024-10-28T08:06:02Z")
정말 도움이 됩니다!
[이전 페이지](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727.md?page=1)
[다음 페이지](https://meta.discourse.org/t/install-discourse-on-ubuntu-or-debian-for-development/14727.md?page=3)