Opened 17 years ago
Last modified 17 years ago
#4476 closed defect
Database lockup - regular but intermittent — at Version 8
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | highest | Milestone: | |
Component: | general | Version: | 0.10.3 |
Severity: | critical | Keywords: | needinfo |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
I am unable to logon to Trac. I get the error message shown below. If you believe it is a server issue please let me know. This problem has occurred about 5 times in the last 10 minutes. But seems to be an intermittent issue. I am fine when I go to the main page: https://develop.participatoryculture.org/trac/democracy/
However when I try to do anything like https://develop.participatoryculture.org/trac/democracy/query?status=new&milestone=Unassigned&order=id&desc=1 I get the error.
Python Traceback Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/trac/web/main.py", line 387, in dispatch_request dispatcher.dispatch(req) File "/usr/lib64/python2.4/site-packages/trac/web/main.py", line 192, in dispatch req.session = Session(self.env, req) File "/usr/lib64/python2.4/site-packages/trac/web/session.py", line 52, in __init__ self.promote_session(sid) File "/usr/lib64/python2.4/site-packages/trac/web/session.py", line 154, in promote_session db.commit() OperationalError: database is locked
Change History (8)
comment:1 by , 17 years ago
Description: | modified (diff) |
---|
comment:2 by , 17 years ago
Milestone: | 0.10.4 |
---|---|
Version: | 0.10.3 → 0.10.2 |
comment:3 by , 17 years ago
Priority: | highest → normal |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
comment:4 by , 17 years ago
Priority: | normal → highest |
---|---|
Resolution: | worksforme |
Status: | closed → reopened |
Our administrator updated our Trac system to 0.10.3 and I and a number of other people are still having issues using Trac. In general I get a message that state the Database is Locked when I try to query or update tickets.
comment:5 by , 17 years ago
Cc: | added |
---|---|
Version: | 0.10.2 → 0.10.3 |
Yes, the upgrade unfortunately did not resolve the problem. The database in question is sqlite, the system is running on Apache 2.0+mod_python.
While typing this, I believe I have discovered why, though:
The DB is *very* large (with plenty of open tickets ;-). Whereas I had doctored up the reports in the past so that they did not pull in the entire ticket under the hidden/RSS field _description (I encountered this awhile ago, but the symptom then for a report failure was a timeout in the web browser, not a Trac fatal error), I cannot do a similar fix to the query page.
Why is this a database locked' error? Why not a
database timeout out' or query result too large'? Or, perhaps the query page should have the very-useful
Show n results starting at result n' type of option?
comment:6 by , 17 years ago
Priority: | highest → low |
---|
comment:7 by , 17 years ago
Priority: | low → highest |
---|
Please do not tamper w/ the ticket status without explaining the reason about your change.
comment:8 by , 17 years ago
Description: | modified (diff) |
---|---|
Keywords: | needinfo added |
The site seems to be quite responsive - are you still experiencing locks?
The site reports "Powered by Trac 0.10.2 By Edgewall Software." - not 0.10.3