Django 管理员组问题
我希望你能帮助我。
问题是，我正在通过 Django Admin 编辑用户，并尝试从那里添加一个新组。添加组页面没有出现，uWSGI日志显示如下：
*** HARAKIRI ON WORKER 3 (pid: 4763) ***
HARAKIRI: --- uWSGI worker 3 (pid: 4763) WAS managing request /admin/auth/group/add/ since Mon Apr 18 13:00:19 2011 ---
DAMN ! process 4763 died :( trying respawn ...
然后我发现我根本无法访问组Admin！有谁知道这里发生了什么？
谢谢！
##### 编辑 #####
看来问题是请求需要花费很多时间来处理，uWSGI 会杀死它，而 django 测试服务器不会，所以在 django 测试服务器中，请求在虽然很长一段时间。 我正在使用 Django_debug_toolbar，这里有一些信息：
Resource Value
User CPU time 4364.273 msec
System CPU time 964.061 msec
Total CPU time 5328.334 msec
Elapsed time 5541.512 msec
Context switches 10983 voluntary, 1053 involuntary
SQL
346 queries in 177.71ms
如果更多数据有助于找到解决方案，请询问我，我想不出任何更相关的内容可以在此处添加。 谢谢！
I hope you can help me.
The thing is, I was editing a user via Django Admin, and tried to add a new group from there. The add group page didn't showed up, and uWSGI log showed as follow:
*** HARAKIRI ON WORKER 3 (pid: 4763) ***
HARAKIRI: --- uWSGI worker 3 (pid: 4763) WAS managing request /admin/auth/group/add/ since Mon Apr 18 13:00:19 2011 ---
DAMN ! process 4763 died :( trying respawn ...
Then I found out that I can't access group Admin at all! Does anyone knows what is happening here?
Thanks!
##### EDIT #####
It seems that the problem is the request takes to much time to process, and uWSGI kills it, while django test server doesn't, so in django test server the request is processed after a long while though.
I'm using Django_debug_toolbar, here is some info:
Resource Value
User CPU time 4364.273 msec
System CPU time 964.061 msec
Total CPU time 5328.334 msec
Elapsed time 5541.512 msec
Context switches 10983 voluntary, 1053 involuntary
SQL
346 queries in 177.71ms
If anymore data would help finding a solution, just ask me, I couldn't think of anything more relevant to add here.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这里没什么可继续的——看起来这个过程已经因为某种未知的原因而终止了。重启有帮助吗？
如果没有，请尝试使用 Django 开发运行服务器运行相同的代码并进行调试，看看是否可以找到潜在的错误。
There's not much to go on here - it looks like the process has died for some unknown reason. Does restarting it help?
If not, try running the same code with the Django development runserver and DEBUG on to see if you can find the underlying error.
其实是Django的问题...升级到1.3版本就好了。虽然没有解决问题，查询所有内容仍然需要很长时间......但它可以使用。谢谢大家，我正在将此线程移至 Django Bugs，因为这是他们的问题...不过，如果有人想发布补丁来修复它，那将非常受欢迎。我认为 Django 社区中已经有人做了这个补丁。谢谢
Actually, it is a problem with Django... Upgraded to version 1.3 and it got better. Didn't solved the problem though, it still takes a long time to query everything... But it's usable. Thanks everyone, I'm moving this thread to Django Bugs since it's their problem... Although, if anyone wants to post a patch to fix it would be really welcomed. I think someone already did this patch in Django community though. Thanks