I did not create any vHost for the moment, I simply edited nf and changed the DocumentRoot. $q=$db->query("SELECT * FROM sqlite_master"),Īt the root of the Web server, I get the content of my database, so I guess the rights are good.Īs a precision, my project is stored in /var/www/myProjectFolder/. I've read many things about this error, but none of them worked for me.įunny thing, when running: php -r 'var_dump( OperationalError at /admin/login/ I am getting an attempt to write a readonly database error. I've set the rights to 777 for the whole folder (this is just a test, don't blame me), but still getting the error. So running chmod 664 /srv/mysite should help. You have to add writing rights to the directory in which your sqlite database is stored. The production server is a Centos 8 running Httpd (so Apache). In short, it happens when the application which writes to the sqlite database does not have write permission. I'm using PDO (a PHP DB interface) to access this DB, but whenever I try to write something in it, I get the error: SQLSTATE: General error: 8 attempt to write a readonly database unlinking the DB file, and then when the connection is opened the DB file gets automatically created if it doesn’t exist. I freshly deployed it on the production server, and it's not working as expected. This error usually happens when your database is accessed by one application already, and youre trying to access it. It looks like the unit tests recreate the DB on every test, i.e. Is it a reasonable fix to just manually change rep-cache. I'm using SQLite3 as a database engine for my Web app. rw-r-r- 1 svn svn 0 Apr 9 17:35 write-lock But those permissions were set up automatically by svn. The unit tests recreate DB schema on every test. Not a DB deadlock but a wrong assumption :). If you encounter problems with access to the database file. The most obvious pieces of advice were to check file permissions. It happens when the application which writes to the sqlite database does not have write permission. (maybe this question is suited for SO, but I don't think it's linked to my code). New issue SQLITEREADONLY: attempt to write a readonly database 2898 Closed Kriskasz opened this issue on 4 comments Kriskasz commented on Node.js version: 10.15.1 NPM version: 6.8.0 Strapi version: 3.0.0-alpha.24.1 Database: mongodb v4.0.6 Operating system: Ubuntu 16. SQLite Error 8: ‘attempt to write a readonly database’ I googled a lot trying to realize what could cause this error.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |