#2005: SQLAlchemy Operational errors with SQLite: Database is locked
---------------------+--------------------
Reporter: abompard | Owner:
Type: defect | Status: new
Priority: critical | Milestone: 0.8.5
Version: 0.8.4 | Resolution:
Keywords: database |
---------------------+--------------------
Comment (by dustin):
I wonder if this is possibility number 4?
fcntl(3, F_SETLK call on DB file fails. This could be caused by an NFS
locking issue, for example. One solution for this issue, is to mv the DB
away, and copy it back so that it has a new Inode value.
I really can't see any other way to get this error in such a modern
version.
I'm working on a way to specify the concurrency level -- pool_size was not
it, sorry.
--
Ticket URL: <http://trac.buildbot.net/ticket/2005#comment:10>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
