SQL logic error or missing database on syncing lastest subversion change

[Scott Windsor <swindsor@…>]

My trac instance broke recently after a subversion and now errors every time I pull up our trac page.

From the logs…

2007-11-29 11:00:10,339 Trac[cache] INFO: repos rev [498] != cached rev [497]
2007-11-29 11:00:10,369 Trac[cache] INFO: Trying to sync revision [498]
2007-11-29 11:00:10,529 Trac[cache] DEBUG: Caching node change in [498]: (u'web/trunk/app/models/location.rb', 'file', 'edit', u'web/trunk/app/models/location.rb', 496)
2007-11-29 11:00:10,544 Trac[cache] DEBUG: Caching node change in [498]: (u'web/trunk/app/models/region.rb', 'file', 'edit', u'web/trunk/app/models/region.rb', 496)
2007-11-29 11:00:10,570 Trac[main] ERROR: SQL logic error or missing database
Traceback (most recent call last):
  File "/home/freds/packages/lib/python/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/home/freds/packages/lib/python/trac/web/main.py", line 191, in dispatch
    chosen_handler = self._pre_process_request(req, chosen_handler)
  File "/home/freds/packages/lib/python/trac/web/main.py", line 263, in _pre_process_request
    chosen_handler = f.pre_process_request (req, chosen_handler)
  File "/home/freds/packages/lib/python/trac/versioncontrol/api.py", line 73, in pre_process_request
    self.get_repository(req.authname).sync()
  File "/home/freds/packages/lib/python/trac/versioncontrol/cache.py", line 185, in sync
    (str(next_youngest),
  File "/home/freds/packages/lib/python/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "/home/freds/packages/lib/python/trac/db/sqlite_backend.py", line 56, in execute
    args or [])
  File "/home/freds/packages/lib/python/trac/db/sqlite_backend.py", line 48, in _rollback_on_error
    return function(self, *args, **kwargs)
OperationalError: SQL logic error or missing database 

From what I can tell, there is a problem syncing our latest subversion checkin…

------------------------------------------------------------------------
r498 | freds | 2007-11-28 17:58:14 -0800 (Wed, 28 Nov 2007) | 1 line
Changed paths:
   M /web/trunk/app/models/location.rb
   M /web/trunk/app/models/region.rb
   M /web/trunk/app/models/region_type.rb
   A /web/trunk/db/migrate/006_create_region_types.rb (from /web/trunk/db/migrate/057_create_region_types.rb:495)
   D /web/trunk/db/migrate/007_create_locations.rb
   A /web/trunk/db/migrate/007_create_region_source_types.rb (from /web/trunk/db/migrate/058_create_region_source_types.rb:495)
   A /web/trunk/db/migrate/008_create_regions.rb (from /web/trunk/db/migrate/059_create_regions.rb:495)
   A /web/trunk/db/migrate/009_create_region_details.rb (from /web/trunk/db/migrate/061_create_region_details.rb:491)
   A /web/trunk/db/migrate/011_create_locations.rb (from /web/trunk/db/migrate/007_create_locations.rb:496)
   D /web/trunk/db/migrate/057_create_region_types.rb
   D /web/trunk/db/migrate/058_create_region_source_types.rb
   D /web/trunk/db/migrate/059_create_regions.rb
   D /web/trunk/db/migrate/061_create_region_details.rb
   M /web/trunk/lib/geocode_services.rb
   M /web/trunk/lib/region_import.rb
   M /web/trunk/public/javascripts/map/map.js

Dynamically updating Atlas code
------------------------------------------------------------------------

I can't see what would cause the problem here. Our database is fine, and if I take out subversion from our config, the server works fine.

Is there any way to get more information out of sqlite about the specific SQL error it's having?

[Christian Boos]

Sorry for not replying earlier:

• did a trac-admin path_to_the_env resync fix this issue?
• did it happen again?
• are you using a scoped repository and the trac-post-commit-hook?

[Christian Boos]

This looked like a serious error, but without more details I don't see how we can progress on this.

If you are still willing to solve this:

• try also with 0.11
• consider making a copy of the repository available so that I can try to reproduce the issue

[Scott Windsor <swindsor@…>]

Sorry about the delay. The issue must have been with that checkin, but once a new revision was created in subversion, I wasn't able to reproduce the problem - but I did end up getting corrupted records in my sqlite database. I have since migrated off sqlite and onto mysql and have yet to see any issues with database corruption.