Ticket #1104 (closed defect: invalid)
Can't start Trac on Ubuntu+Python2.3
| Reported by: | carribeiro | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.8 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
I'm having a hard time trying to install Trac on my development PC. Initially I could not make the pre-built trac debian package work for me. It requires a pysqlite 0.5 or greater, and I could not find such a package pre-built for Python 2.3. After some failed attempts, I checked out the current 0.8 trunk code from the repository and installed it (python setup.py install). I've followed the advice on the Wiki page about Trac to configure Apache2. (I've read both TracOnDebian and TracOnDebianFromTrunk).
After all this was done, I could start Trac once. However, when I tried to edit the main page, it blocked. The curious part is that after that, I removed trac, reinstalled it, checked user permissions, and re-initialized the enviroment (with initenv) a few times, but it still gives the same message, and does not show the home page anymore:
Oops...
Trac detected an internal error:
database is locked
Traceback (most recent call last):
File "/usr/lib/python2.3/site-packages/trac/core.py", line 537, in cgi_start
real_cgi_start()
File "/usr/lib/python2.3/site-packages/trac/core.py", line 532, in real_cgi_start
dispatch_request(path_info, args, req, env)
File "/usr/lib/python2.3/site-packages/trac/core.py", line 435, in dispatch_request
req.session = Session.Session(env, req, newsession)
File "/usr/lib/python2.3/site-packages/trac/Session.py", line 51, in __init__
self.get_session(sid)
File "/usr/lib/python2.3/site-packages/trac/Session.py", line 107, 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
As I said, the most curious part is that I delete the DB, re-create it, and it still gives the same error. I don't have a clue about it, but I fear that it may be related to my use of Python 2.3.


