Code

Opened 6 years ago

Closed 6 years ago

#9175 closed (invalid)

Changing TIME_ZONE causes restart loop of development server

Reported by: nileshashra Owned by: nobody
Component: django-admin.py runserver Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Changing TIME_ZONE to anything except the default "America/Chicago" (in my case "Europe/London") causes runserver to get into a restart loop.

The server starts successfully, but after a few seconds will restart itself and continue to do so forever.

Changing TIME_ZONE back to "America/Chicago" fixes it.

Attachments (0)

Change History (1)

comment:1 Changed 6 years ago by mtredinnick

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

Lots of people routinely run with the timezone setting set to things other than America/Chicago without problems. There's something else going on here that is specific to your system. What OS/platform are you running on?

One possibility is that one or more your Django source files are somehow timestamped with a time from the future, so, to the runserver, it looks like they have changed and so it restarts. Have a look at the timestamps on the files and see if any of them have timestamps that look incorrect. If you're on a Unix-like system, run "touch" on the source files to bring them into line with the current time and see if that changes things. However, it's not clear, in this case, why things would even work in the Chicago timezone unless your system time is set to something odd.

I'm going to close this because I'm positive there's no bug in Django here. If the timestamp on the source files isn't the problem, you probably want to post to django-users and provide as much relevant information as you can about your particular setup (OS type/version, where you got the source from, how you installed it, whether it was a fresh install or an upgrade, etc...).

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.