Opened 13 years ago
Closed 10 years ago
#17581 closed Bug (fixed)
Development server errors
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Core (Management commands) | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Hi, I am running django 1.3.0 final, python 2.6.5, ubuntu 10.04 server, mysql 5.1.41. Note that I have this issue when running the development server ( python manage.py runserver). I have had this issue on other servers too. Every few times when saving files and the server starts to revalidate models it throws out the following exception. It does not stop the server from running but does cause the first page request to fail.
Development server is running at http://x.x.x.x:9206/ Quit the server with CONTROL-C. Unhandled exception in thread started by <bound method Command.inner_run of <django.contrib.staticfiles.management.commands.runserver.Command object at 0x9de50cc>> Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/apport_python_hook.py", line 48, in apport_excepthook if not enabled(): TypeError: 'NoneType' object is not callable Original exception was: Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/django/core/management/commands/runserver.py", line 107, in inner_run run(self.addr, int(self.port), handler, ipv6=self.use_ipv6) File "/usr/local/lib/python2.6/dist-packages/django/core/servers/basehttp.py", line 696, in run httpd.serve_forever() File "/usr/lib/python2.6/SocketServer.py", line 224, in serve_forever r, w, e = select.select([self], [], [], poll_interval) AttributeError: 'NoneType' object has no attribute 'select' Validating models... 0 errors found Django version 1.3, using settings 'x' Development server is running at http://x.x.x.x:9206/ Quit the server with CONTROL-C.
I am not sure if my application has simply become too big for django and it does not manage to revalidate all the stuff before trying to serve the request.
Change History (4)
comment:1 by , 13 years ago
Triage Stage: | Unreviewed → Accepted |
---|---|
Type: | Uncategorized → Bug |
comment:3 by , 12 years ago
Component: | Uncategorized → Core (Management commands) |
---|
comment:4 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I'm closing it since the bug is no longer relevant.
Not sure what causes that, but others have it on Python 2.6.X, too:
http://trac.edgewall.org/ticket/3957
http://trac.edgewall.org/ticket/9960