after upgrade: database is locked

[anonymous]

I just updated svn and after upgrade I got this:

---

Traceback (most recent call last):

File "/usr/lib/python2.2/site-packages/trac/core.py", line 477, in cgi_start

real_cgi_start()

File "/usr/lib/python2.2/site-packages/trac/core.py", line 423, in real_cgi_start

env = open_environment()

File "/usr/lib/python2.2/site-packages/trac/core.py", line 178, in open_environment

version = env.get_version()

File "/usr/lib/python2.2/site-packages/trac/Environment.py", line 162, in get_version

cursor.execute("SELECT value FROM system WHERE name='database_version'")

File "/usr/lib/python2.2/site-packages/sqlite/main.py", line 237, in execute

self.con._begin()

File "/usr/lib/python2.2/site-packages/sqlite/main.py", line 508, in _begin

self.db.execute("BEGIN")

OperationalError?: database is locked

---

working revision is #602
broken revision is #620

Dmitry

[anonymous]

I didn't logged out before upgrade... I wonder if this can couse the problem...

[anonymous]

I moved back to the changeset [602]. And everything works fine. Than I logged out,
and tried to upgrade again but with the same bad result. So, problem is not related to login.

[anonymous]

it happened after i upgraded from db3 to db4....

[daniel]

Has anyone else experienced this?

[anonymous]

I mentioned, that it is important to properly close connection after use.
Even in case of exception, connection must be properly closed & cleaned up.
Otherwise in my environment I always hit database lock condition.
I think this is what is happening but unfortunately I do not have time to
test my theory.

Dmitry

[anonymous]

I am having the same problem with the latest bleeding edge version. 0.7.1 works fine. The output I get is:

Oops...

Trac detected an internal error:

database is locked
Traceback (most recent call last):

File "/usr/lib/python2.3/site-packages/trac/ModPythonHandler.py", line 174, in handler

core.dispatch_request(mpr.path_info, args, mpr, env)

File "/usr/lib/python2.3/site-packages/trac/core.py", line 389, in dispatch_request

req.session = Session.Session(env, req, newsession)

File "/usr/lib/python2.3/site-packages/trac/Session.py", line 50, in init

self.get_session(sid)

File "/usr/lib/python2.3/site-packages/trac/Session.py", line 106, in get_session

" WHERE sid=%s", self.sid)

File "/usr/lib/python2.3/site-packages/sqlite/main.py", line 237, in execute

self.con._begin()

File "/usr/lib/python2.3/site-packages/sqlite/main.py", line 508, in _begin

self.db.execute("BEGIN")

OperationalError?: database is locked

I can try it with cgi if you want. I just reverted back to 0.7.1

[anonymous]

I am happy to report I solved this problem by upgading to version 0.5 of pysqlite. Just in case anyone else is having this problem.

[jonas]

pysqlite 0.5 has been out for quite some time now so we can safely depend on
that version.

[dg@…]

Note to Ubuntu Warty users :

You'll need to upgrade to python2.3-sqlite v1.0-2 and python-sqlite v 1.0-2.
Warty's version is 0.4.3 which is not supported, and doesn't work.

(Sarge has the correct packages in, as does Ubuntu's Hoary)