Modify ↓
Opened 19 years ago
Closed 19 years ago
#3795 closed defect (duplicate)
SageTV community sites doesn't works
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | wiki system | Version: | 0.9.6 |
| Severity: | major | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
When visiting sites (sub sites) within the SageTV community I receive the error :
Trac detected an internal error: database is locked
Python traceback
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 526, in real_cgi_start
dispatch_request(path_info, args, req, env)
File "/usr/lib/python2.3/site-packages/trac/core.py", line 433, 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 114, in get_session
self.update_sess_time()
File "/usr/lib/python2.3/site-packages/trac/Session.py", line 99, in update_sess_time
self['last_visit'] = sess_time
File "/usr/lib/python2.3/site-packages/trac/Session.py", line 59, in __setitem__
return self.set_var(key, val)
File "/usr/lib/python2.3/site-packages/trac/Session.py", line 138, in set_var
self.purge_expired()
File "/usr/lib/python2.3/site-packages/trac/Session.py", line 175, in purge_expired
" AND var_value < %i)", mintime)
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 503, in _begin
self.db.execute("BEGIN")
OperationalError: database is locked
Attachments (0)
Change History (1)
comment:1 by , 19 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.



This is a known issue, duplicate of #1661 and some others one, see also #3503