Opened 15 years ago
Closed 15 years ago
#8983 closed defect (duplicate)
OperationalError: database is locked
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | |
Severity: | major | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Completely unable to access the BOS Architecture wiki http://vmbosl1.qcorpaa.aa.com/trac/amr/bos-architecture/wiki
Below is the error message…
Traceback (most recent call last): File "/usr/local/lib/python2.3/site-packages/trac/web/main.py", line 356, in dispatch_request dispatcher.dispatch(req) File "/usr/local/lib/python2.3/site-packages/trac/web/main.py", line 190, in dispatch req.perm = PermissionCache(self.env, req.authname) File "/usr/local/lib/python2.3/site-packages/trac/perm.py", line 267, in __init__ self.perms = PermissionSystem(env).get_user_permissions(username) File "/usr/local/lib/python2.3/site-packages/trac/perm.py", line 231, in get_user_permissions for perm in self.store.get_user_permissions(username): File "/usr/local/lib/python2.3/site-packages/trac/perm.py", line 111, in get_user_permissions cursor.execute("SELECT username,action FROM permission") File "/usr/local/lib/python2.3/site-packages/trac/db/util.py", line 48, in execute return self.cursor.execute(sql) File "/usr/local/lib/python2.3/site-packages/sqlite/main.py", line 244, in execute self.rs = self.con.db.execute(SQL) OperationalError: database is locked
Attachments (0)
Change History (3)
follow-up: 2 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Replying to joel.toland@…:
1/20/2010 update; aftger about 10 minutes the database locked issue appeared to resolve itself and I was able to access the wiki again - Joel
#3446: Rate of database is locked errors is too high (see all) This used to be a plague with the SQLite database backend, but it seems that things improved over time and this once #1 duplicate bug is less frequent those days. The problem should even be completely gone with 0.11.6 or 0.12dev. A more scary variant of #3446 is #4929, where the lock situation seems to persist and needs a server restart (rare).
comment:3 by , 15 years ago
Description: | modified (diff) |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Yes, this is a duplicate of #3446.
1/20/2010 update; aftger about 10 minutes the database locked issue appeared to resolve itself and I was able to access the wiki again - Joel