[Bugs] #698 UNSP: OperationalError: database is locked

Sugar Labs Bugs bugtracker-noreply at sugarlabs.org
Tue Feb 23 06:39:51 EST 2010

#698: OperationalError: database is locked
    Reporter:  sascha_silbe               |          Owner:  bernie                     
        Type:  defect                     |         Status:  assigned                   
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  trac                       |        Version:  Unspecified                
    Severity:  Minor                      |       Keywords:                             
Distribution:  Unspecified                |   Status_field:  Unconfirmed                
Changes (by sascha_silbe):

  * owner:  krstic => bernie
  * status:  new => assigned
  * component:  infrastructure => trac


 This still happens occasionally, e.g. recently to Tabitha (#1745).
 Upstream bugs related to this issue are
 [http://trac.edgewall.org/ticket/3446 Trac#3446],
 [http://trac.edgewall.org/ticket/3503 Trac#3503]. It is believed to have
 been fixed in Trac 0.11.6 (which we run), but only in combination with
 mod_python >= 3.3.1 (do we use that at all?), SQLite 3.3.8 and PySqlite
 2.5.0. Since I don't have shell access I cannot check the latter versions.
 It has been [http://trac.edgewall.org/ticket/3446#comment:9 pointed out]
 this only happens with sqlite, so we might want to move to PostgreSQL
 instead; this would also be a small step in preparing Trac for redundant
 operation. We can do that once it got moved to sunjammer.

Ticket URL: <http://bugs.sugarlabs.org/ticket/698#comment:2>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system

More information about the Bugs mailing list