Opened 13 years ago
Closed 13 years ago
Last modified 13 years ago
#9403 closed defect (worksforme)
ValueError: timestamp out of range for platform time_t
|Reported by:||anderson||Owned by:|
This error is happing on any page, after I upgraded to the 1.2b1 version.
How to Reproduce
While doing a GET operation on
/ticket/1101, Trac issued an internal error.
(please provide additional details here)
User Agent was:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_3; en-us) AppleWebKit/531.22.7 (KHTML, like Gecko) Version/4.0.5 Safari/531.22.7
Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 423, in _dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 197, in dispatch resp = chosen_handler.process_request(req) File "/usr/lib/python2.5/site-packages/trac/ticket/web_ui.py", line 170, in process_request return self._process_ticket_request(req) File "/usr/lib/python2.5/site-packages/trac/ticket/web_ui.py", line 435, in _process_ticket_request ticket = Ticket(self.env, id, version=version) File "/usr/lib/python2.5/site-packages/trac/ticket/model.py", line 44, in __init__ self.fields = TicketSystem(self.env).get_ticket_fields() File "/usr/lib/python2.5/site-packages/trac/ticket/api.py", line 224, in get_ticket_fields options = [val.name for val in cls.select(self.env, db=db)] File "/usr/lib/python2.5/site-packages/trac/ticket/model.py", line 715, in select milestone._from_database(row) File "/usr/lib/python2.5/site-packages/trac/ticket/model.py", line 631, in _from_database self.due = due and datetime.fromtimestamp(int(due), utc) or None ValueError: timestamp out of range for platform time_t
Change History (2)
comment:1 by , 13 years ago
|Status:||new → closed|
comment:2 by , 13 years ago
I just upgraded from .11 to .12 and I get the same issue. How to fix?
Note: See TracTickets for help on using tickets.
This is an InstallationIssue.
Look again at the report above: you said you have upgraded to Trac 0.12b1, yet you're still using Trac 0.11.1. But the upgrade of the environment happened nevertheless, as one step of the upgrade is to change the resolution of the timestamps from seconds to microseconds. This makes it impossible to continue using Trac 0.11 with an environment that has been upgraded to 0.12…
Newer versions are more robust about this kind of issue (e.g. Trac 0.12 will refuse to work on a 0.13 environment and will tell you that with a clear error message).
So basically you need to stop your server, make sure the new version of Trac will be used to serve the upgraded environments and restart it.