Opened 9 years ago

Closed 7 years ago

#18542 closed Bug (worksforme)

Intermittent unhandled exception when killing runserver

Reported by: Roy Smith Owned by: nobody
Component: Core (Management commands) Version: 1.4
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


Starting from a brand new django 1.4 project with no user code, I started up runserver and got the usual "Congratulations on your first Django-powered page.". Then I killed runserver with a Control-C and got the following. I haven't been able to reproduce this, so I'm guessing it's some race condition. Doesn't seem to be a critical issue, so just opening this ticket to document what happened.

I'm running:

OSX 10.6.8
Python 2.7
Django 1.4

$ ./ runserver
Validating models...

0 errors found
Django version 1.4, using settings 'scoregatta.settings'
Development server is running at
Quit the server with CONTROL-C.
[29/Jun/2012 12:10:19] "GET / HTTP/1.1" 200 1961
^CUnhandled exception in thread started by <bound method Command.inner_run of < object at 0x1019cc6d0>>
Traceback (most recent call last):
  File "/Users/roy/scoregatta/env/lib/python2.7/site-packages/django/core/management/commands/", line 111, in inner_run
     ipv6=self.use_ipv6, threading=threading)
  File "/Users/roy/scoregatta/env/lib/python2.7/site-packages/django/core/servers/", line 253, in run

Change History (3)

comment:1 Changed 9 years ago by Aymeric Augustin

Triage Stage: UnreviewedAccepted

comment:2 Changed 9 years ago by Claude Paroz

Note the similarities with #14273 and #17581, even if the tracebacks are not identical.

comment:3 Changed 7 years ago by Tim Graham

Resolution: worksforme
Status: newclosed

Please reopen if it can be reproduced on a newer version of Django.

Note: See TracTickets for help on using tickets.
Back to Top