首页
学习
活动
专区
圈层
工具
发布
首页
学习
活动
专区
圈层
工具
MCP广场
社区首页 >问答首页 >Django 1.6w/ gunicorn - OperationalError:(2006年,'MySQL服务器已经消失‘)

Django 1.6w/ gunicorn - OperationalError:(2006年,'MySQL服务器已经消失‘)
EN

Stack Overflow用户
提问于 2015-07-29 13:31:57
回答 1查看 459关注 0票数 0

在升级到Django 1.6的过程中,我开始获得一条频繁的OperationalError: (2006, 'MySQL server has gone away')消息,用于运行django应用程序所用的gunicorn服务器的请求。从服务器启动的那一刻起,这些错误就会立即发生,因为请求只需要一秒时间,这使我怀疑这是一个超时问题。此错误不存在于项目的旧1.4分支中,如果仅通过django-admin.py runserver提供服务,则1.6分支的行为也不会这样。

我通常通过一个sv进程运行gunicorn (但如果我也手动运行它时会出错),使用命令django-admin.py run_gunicorn --workers=4 -b localhost:8000,这会导致许多请求,甚至是对静态媒体的请求,返回如下:

代码语言:javascript
运行
复制
[ERROR] 2015-07-29 14:30:27,931 - gunicorn.error:260 - Error handling request
Traceback (most recent call last):
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/gunicorn/workers/sync.py", line 125, in handle_request
    respiter = self.wsgi(environ, resp.start_response)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 187, in __call__
    self.load_middleware()
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 47, in load_middleware
    mw_instance = mw_class()
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/middleware/locale.py", line 24, in __init__
    for url_pattern in get_resolver(None).url_patterns:
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/core/urlresolvers.py", line 365, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/core/urlresolvers.py", line 360, in urlconf_module
    self._urlconf_module = import_module(self.urlconf_name)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
    __import__(name)
  File "/opt/apps/maplecroft/versions/current/websites/maplecroft/urls.py", line 2, in <module>
    from maplecroft.views import RiskAtlasesLandingView
  File "/opt/apps/maplecroft/versions/current/maplecroft/views.py", line 40, in <module>
    import maplecroft.search as _search
  File "/opt/apps/maplecroft/versions/current/maplecroft/search.py", line 71, in <module>
    class MaplecroftSearchForm(SearchForm):
  File "/opt/apps/maplecroft/versions/current/maplecroft/search.py", line 111, in MaplecroftSearchForm
    choices=model_choices(),
  File "/opt/apps/maplecroft/versions/current/maplecroft/search.py", line 57, in model_choices
    for category in reversed(Category.objects.filter(parent=None)):
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/models/query.py", line 77, in __len__
    self._fetch_all()
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/models/query.py", line 857, in _fetch_all
    self._result_cache = list(self.iterator())
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/models/query.py", line 220, in iterator
    for row in compiler.results_iter():
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 713, in results_iter
    for rows in self.execute_sql(MULTI):
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 786, in execute_sql
    cursor.execute(sql, params)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/backends/util.py", line 69, in execute
    return super(CursorDebugWrapper, self).execute(sql, params)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute
    return self.cursor.execute(sql, params)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/utils.py", line 99, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/backends/util.py", line 53, in execute
    return self.cursor.execute(sql, params)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/django/db/backends/mysql/base.py", line 124, in execute
    return self.cursor.execute(query, args)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/MySQLdb/cursors.py", line 174, in execute
    self.errorhandler(self, exc, value)
  File "/opt/envs/maplecroft/local/lib/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
OperationalError: (2006, 'MySQL server has gone away')

但是,如果我访问--workers=1,一切看起来都很顺利,所以我目前的想法是,这是一个线程工人特性的问题吗?

编辑:我刚刚尝试升级到最新版本(在0.17.2上),但这似乎没有什么区别。

我想知道这个问题:https://serverfault.com/questions/407612/error-2006-mysql-server-has-gone-away是否相关,但很难将它与我当前的问题重叠起来

EN

回答 1

Stack Overflow用户

回答已采纳

发布于 2015-07-29 14:50:14

看起来,这毕竟是古尼科恩的版本--我试着升级古尼科恩,但仍在使用启动服务器的django-admin.py run_gunicorn方法。升级后,切换到非反对的gunicorn wsgi:application方法解决了它。

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/31701939

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档