Locked database errors

[kegsay]

{
  "error":"database is locked",
  "level":"error",
  "msg":"Failed to persist next_batch token",
  "next_batch":"s39513903_25872915_34252_3708100_14886_10006_12",
  "time":"2016-09-08T09:06:24+01:00",
  "user_id":"@neb_giphy:matrix.org"
}

[kegsay]

mattn/go-sqlite3#274

sqlite allows multiple readers but only a single writer at any one time. If you have multiple connections to the same DB, you will inevitably run into database is locked. This is an unavoidable consequence of sqlite's locking model, and therefore something your application needs to deal with. Possible solutions include:

• Only ever open a single connection to the DB (but note this can still result in multiple connections to the DB if a user runs multiple instances of your application at once)
• Set the busy timeout to something reasonably high (which causes sqlite to retry lock acquisition for a certain amount of time before returning database is locked). In go-sqlite3 this is achieved by appending eg. ?_busy_timeout=5000 to the filename passed to sql.Open, where 5000 is the number of milliseconds to retry.
  Also note that tx.Begin() and tx.Commit() are currently affected by issue Create a gitlab bot #184 which can result in a connection getting stuck in an inconsistent state if SQLITE_BUSY is encountered while commit is in progress. But setting an appropriate busy timeout should avoid this situation also (unless you have excessively long lived transactions in which case you might want to rethink your design and/or ensure that you're closing all your transaction/result objects in a timely manner).

Yay?