in reply to Re: DBD::SQLite "file is encrypted or is not a database" in running application
in thread [SOLVED]: DBD::SQLite "file is encrypted or is not a database" in running application

This is where I was leaning as soon as I was able to get the error output of my crashes.

Tomorrow, in hopes of repro-ing in a more consistent way, I'm going to throw together a perl script that spawns off a bunch of children that continuously write to the db simultaneously to try to force the same crash, then I'll play around with locking code, and test it with this mentioned setup.

I'll post back on this thread with what I find, and how I get around to possibly solving it.

  • Comment on Re^2: DBD::SQLite "file is encrypted or is not a database" in running application

Replies are listed 'Best First'.
Re^3: DBD::SQLite "file is encrypted or is not a database" in running application
by Marshall (Canon) on Oct 10, 2016 at 00:38 UTC
    You might find this of interest: SQLite Locking.

    SQLite has a robust locking mechanism. For a write, a connection has to acquire an exclusive lock on the DB. This can significantly affect the performance in multi-writer situations. Any failure in the locking mechanism would be a high priority bug.