Thanks for the advice. I ran my python script using strace. It is failing under the fcntl() command. strace says that (Function not implemented). I did a search on google and found the following under the sqlite3 FAQ:
SQLite uses reader/writer locks to control access to the database...But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. This is because fcntl() file locking is broken on many NFS implementations... At this point, I guess my next step is to figure out how to get this fixed (any suggestions). Thanks, Kerry ________________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Roger Binns [rog...@rogerbinns.com] Sent: Monday, October 03, 2011 6:47 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] sqlite3.OperationalError: disk I/O error -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/03/2011 03:05 PM, Dungan, Kerry wrote: > the result: > An empty file.db is created, and I get "sqlite3.OperationalError: disk I/O > error" on the execute command. There could be any number of reasons. The message is coming from the SQLite library and it is doing that because of something that happened with the operating system. My best guess is that the journal can't be created for some reason. The server may have extra security rules, quotas etc causing this. The easiest way to find the problem is to run the program under strace which will show every system call made and the response. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6KO5EACgkQmOOfHg372QT59gCgsGUnfKkN0XvZoEB6ULgV1tQL 1YoAn3GNFXbOwyYQpJ6/VAO0rErdGWZA =6WFN -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
