Modify

#10606 closed defect (invalid)

OperationalError: database is locked

Reported by: eikos_kim Owned by:
Priority: highest Component: SELECT A HACK
Severity: blocker Keywords:
Cc: Trac Release:

Description

How to Reproduce

While doing a GET operation on /report/11, Trac issued an internal error.

(please provide additional details here)

Request parameters:

{'id': u'11'}

User agent: #USER_AGENT#

System Information

Trac 0.12.2
Trac 0.12.2
Docutils 0.5
Genshi 0.6
Pygments 1.0
pysqlite 2.5.5
Python 2.5.4 (r254:67916, Apr 9 2009, 07:57:21)
[GCC 4.1.2 20070626 (Red Hat 4.1.2-14)]
Python 2.5.4 (r254:67916, Apr 9 2009, 07:57:21)
[GCC 4.1.2 20070626 (Red Hat 4.1.2-14)]
pytz 2006p
pytz 2006p
setuptools 0.6c8
setuptools 0.6c8
SQLite 3.6.16
Subversion 1.7.2 (r1207936)
jQuery #JQUERY#

Enabled Plugins

IniAdmin 0.2
TracNav 4.0pre7
TracTags 0.6
TracTicketDelete 2.0
TracTocMacro 11.0.0.3

Python Traceback

Traceback (most recent call last):
  File "/usr/local/Python-2.5.2/lib/python2.5/site-packages/trac/web/main.py", line 511, in _dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/Python-2.5.2/lib/python2.5/site-packages/trac/web/main.py", line 260, in dispatch
    req.session.save()
  File "/usr/local/Python-2.5.2/lib/python2.5/site-packages/trac/web/session.py", line 105, in save
    @self.env.with_transaction()
  File "/usr/local/Python-2.5.2/lib/python2.5/site-packages/trac/db/api.py", line 78, in transaction_wrapper
    ldb.commit()
OperationalError: database is locked

Attachments (0)

Change History (1)

comment:1 Changed 21 months ago by anonymous

  • Resolution set to invalid
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from (none). Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.