2014-05-21 7 views
-2

나는 내 애플에게 Heroku에 배포 실행하려고 만하고 chrased지고 난 === 웹 (1X)라는 오류가 표시되어 Heroku가 추신 실행하면 gunicorn mysite.wsgi web.1 : 2014년 5월 24일 19 추락을 : 25 : 03 (~ 전에 1m)에게 Heroku의 응용 프로그램은

내 로그는 실수를 찾을 수 없습니다입니다 : -

2014-05-24T12:27:30.424427+00:00 heroku[api]: Enable Logplex by [email protected] 
2014-05-24T12:27:30.424600+00:00 heroku[api]: Release v2 created by [email protected] 
2014-05-24T12:28:23+00:00 heroku[slug-compiler]: Slug compilation started 
2014-05-24T12:29:12.587922+00:00 heroku[api]: Release v3 created by [email protected] 
2014-05-24T12:29:12.746669+00:00 heroku[api]: Attach HEROKU_POSTGRESQL_AQUA resource by [email protected] 
2014-05-24T12:29:12.746748+00:00 heroku[api]: Release v4 created by [email protected] 
2014-05-24T12:29:12.151217+00:00 heroku[api]: Scale to web=1 by [email protected] 
2014-05-24T12:29:12.587705+00:00 heroku[api]: Set DATABASE_URL config vars by [email protected] 
2014-05-24T12:29:12+00:00 heroku[slug-compiler]: Slug compilation finished 
2014-05-24T12:29:12.895151+00:00 heroku[api]: Release v5 created by [email protected] 
2014-05-24T12:29:12.895062+00:00 heroku[api]: Deploy 6e7d5c7 by [email protected] 
2014-05-24T12:29:24.060931+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T12:29:25.341505+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T12:29:25.341708+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T12:29:23.271631+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T12:29:25.328556+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T12:29:30.072705+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T12:29:31.260531+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T12:29:29.269791+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T12:29:31.252704+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T12:29:34.763604+00:00 heroku[api]: Scale to web=1 by [email protected] 
2014-05-24T12:30:20.760282+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=aqueous-ridge-4845.herokuapp.com request_id=86c3c70c-1028-410b-829c-5c165f04d1d6 fwd="117.212.87.180" dyno= connect= service= status=503 bytes= 
2014-05-24T12:41:42.756432+00:00 heroku[api]: Scale to web=1 by [email protected] 
2014-05-24T12:47:08.206557+00:00 heroku[api]: Scale to web=1 by [email protected] 
2014-05-24T12:47:43.117890+00:00 heroku[api]: Scale to web=1 by [email protected] 
2014-05-24T12:50:09.001444+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T12:50:14.143148+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T12:50:17.580432+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T12:50:20.225956+00:00 app[web.1]: Error waiting for network: Success 
2014-05-24T12:50:17.555111+00:00 heroku[web.1]: Process exited with status 128 
2014-05-24T12:59:07.811928+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T12:59:13.111829+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T12:59:12.352990+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T12:59:14.203104+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T12:59:14.193223+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T12:59:21.267040+00:00 heroku[api]: Scale to web=1 by [email protected] 
2014-05-24T12:59:38.001945+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T12:59:44.393012+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T12:59:45.408226+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T12:59:48.157597+00:00 heroku[api]: Scale to web=1 by [email protected] 
2014-05-24T12:59:47.592431+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T12:59:47.577828+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T13:00:18.994191+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T13:00:25.970227+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T13:00:28.008687+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T13:00:25.144999+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T13:00:27.998289+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T13:01:18.046519+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T13:01:24.527619+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T13:01:25.581345+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T13:01:22.643170+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T13:01:25.570127+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T13:22:52.908152+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T13:22:58.073706+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T13:22:59.352752+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T13:22:57.273896+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T13:22:59.341447+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T13:32:08.148926+00:00 heroku[api]: Attach HEROKU_POSTGRESQL_MAROON resource by [email protected] 
2014-05-24T13:32:08.148984+00:00 heroku[api]: Release v6 created by [email protected] 
2014-05-24T13:32:09.206013+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T13:32:15.071622+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T13:32:16.599065+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T13:32:13.998638+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T13:32:16.588110+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T13:34:21.057978+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T13:34:27.236589+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T13:34:28.414007+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T13:34:24.779198+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T13:34:28.401506+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T13:39:35.940063+00:00 heroku[api]: Starting process with command `pip install gunicorn` by [email protected] 
2014-05-24T13:39:40.974669+00:00 heroku[run.7945]: State changed from starting to up 
2014-05-24T13:39:44.453699+00:00 heroku[run.7945]: State changed from up to complete 
2014-05-24T13:39:40.965895+00:00 heroku[run.7945]: Awaiting client 
2014-05-24T13:39:41.289948+00:00 heroku[run.7945]: Starting process with command `pip install gunicorn` 
2014-05-24T13:39:44.440425+00:00 heroku[run.7945]: Process exited with status 0 
2014-05-24T13:51:38.308555+00:00 heroku[api]: Scale to web=1 by [email protected] 
2014-05-24T13:54:56.764314+00:00 heroku[web.1]: State changed from crashed to starting 
2014-05-24T13:55:02.931915+00:00 app[web.1]: bash: gunicorn: command not found 
2014-05-24T13:55:04.092574+00:00 heroku[web.1]: State changed from starting to crashed 
2014-05-24T13:55:02.067552+00:00 heroku[web.1]: Starting process with command `gunicorn mysite.wsgi` 
2014-05-24T13:55:04.082942+00:00 heroku[web.1]: Process exited with status 127 
2014-05-24T13:57:57.566477+00:00 heroku[api]: Starting process with command `pip install gunicorn` by [email protected] 
2014-05-24T13:58:04.884892+00:00 heroku[run.1999]: State changed from starting to up 
2014-05-24T13:58:05.993194+00:00 heroku[run.1999]: Awaiting client 
2014-05-24T13:58:06.027374+00:00 heroku[run.1999]: Starting process with command `pip install gunicorn` 
2014-05-24T13:58:10.033286+00:00 heroku[run.1999]: Process exited with status 0 
2014-05-24T13:58:10.047161+00:00 heroku[run.1999]: State changed from up to complete 

미리

+2

오류 메시지를 읽었습니까? "requirements.txt"의 2 행 및 9 행에 "이중 요구 사항"* 표시. ->'requirements.txt'를 고쳐서 모든 의존성을 한 번만 포함하도록하십시오. –

답변

0

오류가 답을 포함에 나와 감사를 도와주세요.

더블 요구 사항 주어진 : wsgiref의 == 0.1.2 (에서 -r requirements.txt (9 호선)) (이미에서 wsgiref의 == 0.1.2 (에서 -r requirements.txt (2 호선)), 이름 = 'wsgiref') 당신의 requirements.txt 파일에 따라서

. 지정한 "wsgiref"의 두 번째 복사본을 제거해야합니다. 중복 된 파일을 검색 할 줄을 알려줍니다.

관련 문제