Edgewall Software

Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#2039 closed defect (worksforme)

Trac detected an internal error after upgrade from .84 to .9-beta1

Reported by: anonymous Owned by: Jonas Borgström
Priority: high Milestone:
Component: ticket system Version: 0.9b1
Severity: blocker Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Christopher Lenz)

After I upgraded from a working install, I run trac-admin upgrade and track-admin wiki upgrade. Restarted the apache. My trac install came up just fine, however when I got to the Tickets area I get an internal error.

Here is the error:

Traceback (most recent call last):
  File "C:\Python23\Lib\site-packages\trac\web\modpython_frontend.py", line 205, in handler
    dispatch_request(mpr.path_info, mpr, env)
  File "C:\Python23\Lib\site-packages\trac\web\main.py", line 139, in dispatch_request
  File "C:\Python23\Lib\site-packages\trac\web\main.py", line 107, in dispatch
    resp = chosen_handler.process_request(req)
  File "C:\Python23\Lib\site-packages\trac\ticket\web_ui.py", line 62, in process_request
    ticket = Ticket(self.env, db=db)
  File "C:\Python23\Lib\site-packages\trac\ticket\model.py", line 33, in __init__
    self.fields = TicketSystem(self.env).get_ticket_fields()
  File "C:\Python23\Lib\site-packages\trac\ticket\api.py", line 88, in get_ticket_fields
    options = [val.name for val in cls.select(self.env, db=db)]
  File "C:\Python23\Lib\site-packages\trac\Milestone.py", line 136, in select
  File "C:\Python23\Lib\site-packages\sqlite\main.py", line 244, in execute
    self.rs = self.con.db.execute(SQL)
DatabaseError: no such column: due

Attachments (0)

Change History (4)

comment:1 by Christopher Lenz, 15 years ago

Description: modified (diff)

The due column should have been added by the database upgrade scripts (see TracUpgrade). I'm not sure how you've circumvented the database version check ;-)

In any case, try running trac-admin /path/to/projenv upgrade and report the results.

comment:2 by randyjames@…, 15 years ago

I performed the trac-admin upgrade step as part of the overal upgrade.

  1. Ran the windows install package for .9
  2. Ran upgrade from the trac-admin interactive prompted.
  3. Ran a resync.

This all worked fine. Running the trac-admin upgrade again states that the DB is up to date.

comment:3 by randyjames@…, 15 years ago

Here is the sqlite dump of the schema for the milestone table. It appears that this is the table that is missing the due column.

sqlite> .schema milestone CREATE TABLE milestone (

id integer PRIMARY KEY, name text, time integer, owner text, descr text, UNIQUE(name)


comment:4 by Matthew Good, 15 years ago

Milestone: 0.9
Resolution: worksforme
Status: newclosed

Based on emails about this on the mailing list I believe that the user updated the "database_version" entry in Trac's "system" table to 8 either by hand or some other method besides Trac's own upgrade scripts. Due to this manipulation the upgrade script for version 8 of the DB was never run. We really can't guarantee proper application of the upgrade scripts in this situation.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.