Changes between Initial Version and Version 1 of Ticket #82, comment 1


Ignore:
Timestamp:
Jun 9, 2014, 12:40:19 PM (5 years ago)
Author:
schwa
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #82, comment 1

    initial v1  
    3232The ftputil site currently runs Trac 0.12.2 (with Debian's security fixes I assume). This version is supposed to have the "database is locked" problem solved (see [http://trac.edgewall.org/ticket/3446]).
    3333
    34 [http://www.sqlite.org/lockingv3.html] mentions in the section "How To Corrupt Your Database Files" that SQLite uses advisory locking which might be broken on some Posix systems for NFS mounts. Since the ftputil website is hosted on a "virtual root" server, I have no control over how the file system visible from inside the environment is mounted. This ''might'' be a reason for the problems we see.
     34[http://www.sqlite.org/lockingv3.html] mentions in the section "How To Corrupt Your Database Files" that SQLite uses advisory locking which might be broken on some Posix systems for NFS mounts. Since the ftputil website is hosted on a "virtual root" server, I have no control over how the file system visible from inside the environment is mounted. This virtual machine mount ''may'' be a reason for the problems we see.
    3535
    36 Next I'm investigating if I can do anything to improve robustness on the SQLite side. Another - non-trivial - option would be to migrate to another database system, say PostgreSQL.
     36Next I'm investigating if I can do anything to improve robustness on the SQLite side. Another - although non-trivial - option would be to migrate to another database system, say PostgreSQL.