Question

我刚才有一个关于在Heroku上运行烧瓶的快速问题。我不确定我做错了什么，但我很新，所以请原谅愚蠢的错误。

我正在使用Flask在Heroku上部署应用程序。为确保实现中的错误最少，代码直接来自https://github.com/orf/simple。在遵循https://devcenter.heroku.com/articles/python时我做了一些小的调整。当我在dev机器上运行时（通过python simple.py）程序工作正常，程序在heroku上遇到一致的内部服务器错误。日志已附上。

有什么想法吗？

2012-06-23T02:43:47+00:00 heroku[api]: Deploy 69a4995 by *********@gmail.com
2012-06-23T02:43:47+00:00 heroku[web.1]: State changed from up to bouncing
2012-06-23T02:43:47+00:00 heroku[web.1]: State changed from bouncing to created
2012-06-23T02:43:47+00:00 heroku[web.1]: State changed from created to starting
2012-06-23T02:43:47+00:00 heroku[slugc]: Slug compilation finished
2012-06-23T02:43:49+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2012-06-23T02:43:49+00:00 heroku[web.1]: Starting process with command `gunicorn simple:app -b 0.0.0.0:25399 -w 3`
2012-06-23T02:43:49+00:00 app[web.1]: 2012-06-23 02:43:49 [5] [INFO] Worker exiting (pid: 5)
2012-06-23T02:43:49+00:00 app[web.1]: 2012-06-23 02:43:49 [7] [INFO] Worker exiting (pid: 7)
2012-06-23T02:43:49+00:00 app[web.1]: 2012-06-23 02:43:49 [2] [INFO] Handling signal: term
2012-06-23T02:43:49+00:00 app[web.1]: 2012-06-23 02:43:49 [6] [INFO] Worker exiting (pid: 6)
2012-06-23T02:43:49+00:00 app[web.1]: 2012-06-23 02:43:49 [2] [INFO] Shutting down: Master
2012-06-23T02:43:50+00:00 app[web.1]: 2012-06-23 02:43:50 [2] [INFO] Starting gunicorn 0.13.4
2012-06-23T02:43:50+00:00 app[web.1]: 2012-06-23 02:43:50 [2] [INFO] Listening at: http://0.0.0.0:25399 (2)
2012-06-23T02:43:50+00:00 app[web.1]: 2012-06-23 02:43:50 [2] [INFO] Using worker: sync
2012-06-23T02:43:50+00:00 app[web.1]: 2012-06-23 02:43:50 [6] [INFO] Booting worker with pid: 6
2012-06-23T02:43:50+00:00 app[web.1]: 2012-06-23 02:43:50 [5] [INFO] Booting worker with pid: 5
2012-06-23T02:43:50+00:00 app[web.1]: 2012-06-23 02:43:50 [7] [INFO] Booting worker with pid: 7
2012-06-23T02:43:50+00:00 heroku[web.1]: Process exited with status 0
2012-06-23T02:43:51+00:00 heroku[web.1]: State changed from starting to up
2012-06-23T02:45:00+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=21ms status=500 bytes=291
2012-06-23T02:45:01+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/favicon.ico dyno=web.1 queue=0 wait=0ms service=14ms status=404 bytes=238
2012-06-23T02:45:01+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=3ms status=500 bytes=291
2012-06-23T02:45:01+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/favicon.ico dyno=web.1 queue=0 wait=0ms service=15ms status=404 bytes=238
2012-06-23T02:45:02+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=5ms status=500 bytes=291
2012-06-23T02:45:02+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=2ms status=500 bytes=291
2012-06-23T02:45:02+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=4ms status=500 bytes=291
2012-06-23T02:45:02+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=3ms status=500 bytes=291
2012-06-23T02:45:02+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=3ms status=500 bytes=291
2012-06-23T02:45:02+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=5ms status=500 bytes=291
2012-06-23T02:45:02+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=2ms status=500 bytes=291
2012-06-23T02:45:03+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=2ms status=500 bytes=291
2012-06-23T02:45:03+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=4ms status=500 bytes=291
2012-06-23T02:45:03+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=4ms status=500 bytes=291
2012-06-23T02:45:03+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/favicon.ico dyno=web.1 queue=0 wait=0ms service=2ms status=404 bytes=238
2012-06-23T02:45:32+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=2ms status=500 bytes=291
2012-06-23T02:45:32+00:00 heroku[router]: GET deep-rain-4577.herokuapp.com/favicon.ico dyno=web.1 queue=0 wait=0ms service=13ms status=404 bytes=238

Answer 1

编辑：您的应用是否在本地运作？你的Procfile是什么样的？

此外，似乎Heroku在处理线程时表现得很时髦。看起来您的应用程序在几秒钟后获得了SIGTERM。我会放入一些打印语句来确定应用程序在终止之前所做的最后几件事。

这是你的第一个烧瓶应用吗？你的最终目标是什么？学习？如果是这样，我不会从这开始。尝试从头开始编写您的第一个应用程序，以便了解每一行的功能。我将从Flask教程开始：

http://flask.pocoo.org/docs/

然后可以查看以下关于在Heroku上部署flask应用程序的教程：

http://ryaneshea.com/lightweight-python-apps-with-flask-twitter-bootstrap-and-heroku

Heroku上的烧瓶有500个错误，在开发机器上运行

1 个答案: