Christopher Lenz wrote:
Am 19.04.2006 um 10:06 schrieb Christian Boos:
Christian Boos wrote:
Christopher Lenz wrote:
Hi folks,
I've just upgraded projects.edgewall.com to Trac 0.10dev (r2300).
I got a ''Database is locked'' error just now on p.e.c.
While I think it was not a bug per se, I have two remarks:
Wait a minute, I'm really seeing this far too often to be
qualified as "normal" (not to mention the Internal Error I saw too...)
Could it be an interaction with the akismet SpamFilter?
User p.e.c akismet
---- ----- -------
ticket
change -> process
request
... -> validates
...
finish <-
result <-
I'm monitoring the log file on p.e.c, and I *think* the spamfilter is
being triggered way too rarely for it to be the cause... will continue
to investigate though.
Also note that directly after the upgrade the timeline wasn't
responding, even before I installed and enabled SpamFilter. It came back
for some reason a couple of minutes and a restart later, but somehow it
feels shaky. So I suspect the problem may be related to the timeline or
one of the event providers.
But anyway, will continue to monitor the system.
Jonas: what about installing sqlite/pysqlite on lynx?
Lynx currently has sqlite 3.2.1 and pysqlite 2.0.3 installed. I
can upgrade pysqlite tonight unless you want to give it a try before
that.
The "Database is locked" happens when an sqlite transaction was unable
to get an exclusive lock on the database (I think the current timeout
value is 5 seconds). Given the load on p.e.c I think it's not that
unlikely that there will be times when it will be impossible to get an
exclusive lock on the db.
I believe that recent versions of sqlite3 no longer requires an exlusive
lock for the entire lifespan of the transaction but that might only be
true if all transactions are started by the same process (which is not
true for p.e.c).
Cheers,
Jonas
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
