[Trac-tickets] [The Trac Project] #1590: Trac can't handle errornous logs?

The Trac Project noreply at edgewall.com
Tue May 24 12:34:38 EDT 2005


#1590: Trac can't  handle errornous logs?
---------------------+------------------------------------------------------
       Id:  1590     |      Status:  new                     
Component:  general  |    Modified:  Tue May 24 11:34:32 2005
 Severity:  normal   |   Milestone:                          
 Priority:  high     |     Version:  0.8.1                   
    Owner:  jonas    |    Reporter:  orange <trac at fobie.net> 
---------------------+------------------------------------------------------
 I'm getting the 'database is locked' error. This seems to be caused
 because Trac fails when a log is corrupted. I had a server crash while
 commiting, which made the log for the commit errornous. It's missing
 author, date and message. The svn client shows it like this:
 {{{
 r142 | (no author) | (no date) | 2 lines
 }}}

 Trac seems not to be able to handle this, eg:
 {{{
 $ trac-admin /repos resync
 resyncing...
 Segmentation fault
 }}}

 This is what I get when I'm accessing the main site (anywhere):
 {{{
 Traceback (most recent call last):
   File "/usr/lib/python2.3/site-packages/trac/core.py", line 531, in
 cgi_start
     real_cgi_start()
   File "/usr/lib/python2.3/site-packages/trac/core.py", line 513, in
 real_cgi_start
     env = open_environment()
   File "/usr/lib/python2.3/site-packages/trac/core.py", line 190, in
 open_environment
     version = env.get_version()
   File "/usr/lib/python2.3/site-packages/trac/Environment.py", line 162,
 in get_version
     cursor.execute("SELECT value FROM system WHERE
 name='database_version'")
   File "/usr/lib/python2.3/site-packages/sqlite/main.py", line 244, in
 execute
     self.rs = self.con.db.execute(SQL)
 OperationalError: database is locked
 }}}

 To get trac somewhat useful in this state, remove the trac.db-journal
 which can be found in trac/project/db. Tho, in this state the browser or
 the timeline won't work (at least while that commit is accessed).

 Please tell me if you're intrested in the binary changeset. I've tried to
 get some additional information using the logging mechanism in Trac, but
 all I get is the 500 Internal Server Error.

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/1590>
The Trac Project <>


More information about the Trac-Tickets mailing list