# 컨테이너가 빌드되지 않고, 실수로 두 인스턴스를 실행한 후 기존 컨테이너도 시작되지 않습니다
**URL:** https://meta.discourse.org/t/container-wont-build-and-existing-container-wont-start-after-accidentally-running-two-instances/310774
**Category:** Self-hosting
**Created:** [6월 6, 2024, 9:39오전 UTC](https://meta.discourse.org/t/container-wont-build-and-existing-container-wont-start-after-accidentally-running-two-instances/310774 "2024-06-06T09:39:07Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Joshua1985](https://meta.discourse.org/u/Joshua1985)
#### Post date: [6월 6, 2024, 9:39오전 UTC](https://meta.discourse.org/t/container-wont-build-and-existing-container-wont-start-after-accidentally-running-two-instances/310774/1 "2024-06-06T09:39:07Z")
호스팅 제공업체에 의해 서버가 재시작되면서, 지난 주 업그레이드된 새 컨테이너와 함께 구 컨테이너(롤백이 필요한 경우를 대비해 남겨둔 것)가 동시에 실행되었습니다.
현재 새 컨테이너는 아래와 같은 로그가 반복되며 아무것도 서빙하지 않고 있습니다:
```plaintext
(42) Waiting for new unicorn master pid...
(42) Waiting for new unicorn master pid... 1265109
(42) Old pid is: 1264439 New pid is: 1265109
Shutting Down
run-parts: executing /etc/runit/3.d/01-nginx
ok: down: nginx: 0s, normally up
run-parts: executing /etc/runit/3.d/02-unicorn
(42) exiting
ok: down: unicorn: 1s, normally up
run-parts: executing /etc/runit/3.d/10-redis
ok: down: redis: 0s, normally up
run-parts: executing /etc/runit/3.d/99-postgres
ok: down: postgres: 0s, normally up
ok: down: nginx: 2s, normally up
ok: down: postgres: 1s, normally up
ok: down: redis: 1s, normally up
ok: down: unicorn: 2s, normally up
ok: down: cron: 0s, normally up
ok: down: rsyslog: 0s, normally up
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/01-cleanup-web-pids
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
Started runsvdir, PID is 34
ok: run: redis: (pid 48) 0s
ok: run: postgres: (pid 44) 0s
supervisor pid: 45 unicorn pid: 76
(45) Reopening logs
Shutting Down
run-parts: executing /etc/runit/3.d/01-nginx
ok: down: nginx: 1s, normally up
run-parts: executing /etc/runit/3.d/02-unicorn
(45) exiting
ok: down: unicorn: 0s, normally up
run-parts: executing /etc/runit/3.d/10-redis
ok: down: redis: 1s, normally up
run-parts: executing /etc/runit/3.d/99-postgres
ok: down: postgres: 1s, normally up, want up
ok: down: nginx: 2s, normally up
ok: down: postgres: 1s, normally up, want up
ok: down: redis: 1s, normally up
ok: down: unicorn: 1s, normally up
ok: down: cron: 0s, normally up
ok: down: rsyslog: 0s, normally up
run-parts: executing /etc/runit/1.d/00-ensure-links
run-parts: executing /etc/runit/1.d/00-fix-var-logs
run-parts: executing /etc/runit/1.d/01-cleanup-web-pids
run-parts: executing /etc/runit/1.d/anacron
run-parts: executing /etc/runit/1.d/cleanup-pids
Cleaning stale PID files
run-parts: executing /etc/runit/1.d/copy-env
Started runsvdir, PID is 34
ok: run: redis: (pid 48) 0s
ok: run: postgres: (pid 44) 0s
supervisor pid: 49 unicorn pid: 70
config/unicorn_launcher: line 71: kill: (70) - No such process
config/unicorn_launcher: line 15: kill: (70) - No such process
(49) exiting
ok: run: redis: (pid 48) 5s
ok: run: postgres: (pid 86) 1s
supervisor pid: 88 unicorn pid: 92
config/unicorn_launcher: line 71: kill: (92) - No such process
config/unicorn_launcher: line 15: kill: (92) - No such process
(88) exiting
ok: run: redis: (pid 48) 7s
ok: run: postgres: (pid 109) 0s
supervisor pid: 106 unicorn pid: 112
config/unicorn_launcher: line 71: kill: (112) - No such process
config/unicorn_launcher: line 15: kill: (112) - No such process
(106) exiting
ok: run: redis: (pid 48) 10s
ok: run: postgres: (pid 121) 0s
supervisor pid: 128 unicorn pid: 132
config/unicorn_launcher: line 71: kill: (132) - No such process
config/unicorn_launcher: line 15: kill: (132) - No such process
(128) exiting
ok: run: redis: (pid 48) 13s
ok: run: postgres: (pid 149) 0s
supervisor pid: 146 unicorn pid: 152
config/unicorn_launcher: line 71: kill: (152) - No such process
config/unicorn_launcher: line 15: kill: (152) - No such process
(146) exiting
ok: run: redis: (pid 48) 16s
ok: run: postgres: (pid 171) 0s
supervisor pid: 168 unicorn pid: 174
config/unicorn_launcher: line 71: kill: (174) - No such process
config/unicorn_launcher: line 15: kill: (174) - No such process
(168) exiting
ok: run: redis: (pid 48) 20s
ok: run: postgres: (pid 193) 1s
```
또한 `./launcher rebuild` 명령은 PostgreSQL 연결 오류(“/var/run/postgresql/.s.PGSWL.5432” No such file or directory)로 인해 새 컨테이너를 빌드하지 못하고 있습니다.
두 앱이 동시에 실행되어 동일한 DB에 접근하던 기간 동안 문제가 발생한 것으로 보입니다.
이를 어떻게 복구해야 할까요?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [6월 6, 2024, 10:16오전 UTC](https://meta.discourse.org/t/container-wont-build-and-existing-container-wont-start-after-accidentally-running-two-instances/310774/2 "2024-06-06T10:16:54Z")
가장 쉬운 방법은 클린 설치 후 백업을 복원하는 것입니다. 저는 새 VM에서 이렇게 할 것입니다.
---
### Author:  [@Joshua1985](https://meta.discourse.org/u/Joshua1985)
#### Post date: [6월 6, 2024, 10:21오전 UTC](https://meta.discourse.org/t/container-wont-build-and-existing-container-wont-start-after-accidentally-running-two-instances/310774/3 "2024-06-06T10:21:26Z")
답장 주셔서 감사합니다!
그렇게 하기 전에 제가 직접 시도해 볼 수 있는 방법이 있을까요?
빌드 로그를 보면 postgres가 어떤 이유에서인지 시작되지 않는 것 같습니다. 이 문제를 디버깅할 수 있는 방법이 있을까요?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [6월 7, 2024, 12:37오전 UTC](https://meta.discourse.org/t/container-wont-build-and-existing-container-wont-start-after-accidentally-running-two-instances/310774/4 "2024-06-07T00:37:19Z")
무슨 일이 있었을지 추측할 수 없습니다. 표준 설치 방식으로 진행하신다면, 제안하신 내용은 말이 안 됩니다.
문제를 해결하기 위해 돈을 쓰시려면 저에게 연락 주시면, 작동할 수 있는 방법을 찾아볼 수도 있지만, 현재 말씀하신 내용만으로는 딱히 아이디어가 없습니다.