One of my projects has stopped working in trac

[josh@…]

I have several projects in a trac, one of them started giving the following traceback today…

If you think this really should work and you can reproduce it, you should consider reporting this problem to the Trac team.

Go to ​http://trac.edgewall.org/ and create a new ticket where you describe the problem, how to reproduce it. Don't forget to include the Python traceback found below.

TracGuide — The Trac User and Administration Guide Python Traceback

Traceback (most recent call last):
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 387, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 191, in dispatch
    chosen_handler = self._pre_process_request(req, chosen_handler)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 263, in _pre_process_request
    chosen_handler = f.pre_process_request(req, chosen_handler)
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/api.py", line 73, in pre_process_request
    self.get_repository(req.authname) # triggers a sync if applicable
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/api.py", line 101, in get_repository
    repos = self._connector.get_repository(rtype, rdir, authname)
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/svn_fs.py", line 260, in get_repository
    crepos = CachedRepository(self.env.get_db_cnx(), repos, None, self.log)
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/cache.py", line 34, in __init__
    self.sync()
  File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/cache.py", line 100, in sync
    (str(current_rev), path, kind, action,
  File "/usr/local/lib/python2.4/site-packages/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "/usr/local/lib/python2.4/site-packages/trac/db/sqlite_backend.py", line 56, in execute
    args or [])
  File "/usr/local/lib/python2.4/site-packages/trac/db/sqlite_backend.py", line 48, in _rollback_on_error
    return function(self, *args, **kwargs)
OperationalError: table node_change has no column named node_type

[ThurnerRupert]

the database is ok? if the database acts strange sometimse the following might repair it:

$ sqlite3 /your-trac-instance/db/trac.db
sqlite> PRAGMA integrity_check;
sqlite> vacuum;

[josh@…]

sqlite> PRAGMA integrity_check; ok sqlite> vacuum; sqlite>

The error seems to suggest that there is no column named node_type.

sqlite> .schema node_change CREATE TABLE node_change (

rev text, path text, node_type text, change_type text, base_path text, base_rev text, UNIQUE (rev,path,change_type)

); CREATE INDEX node_change_rev_idx ON node_change (rev);

Is it possible a field without a node_type set is causing the error or something?

[sid]

Sorry for delayed response. Did you ever figure this one out?

[Christian Boos]

I don't see what we can do here. If you ever resolved this, please drop a note here.

[gincantalupo@…]

I solved it adding the node_type column: alter table node_change ADD column node_type text; Hope it won't give problems in future but now it seems working fine.