Could not open database file

Resolved islp
(@islp)

6 months, 2 weeks ago

By pure chance, since I was working locally with some sqlite dbs of mine, I opened one cache file produced by the plugin using a simple tool (DB Browser for SQLite). I found the file could not be opened (“Could not open database file. Reason: database disk image is malformed”). Is this normal? Can my website read and write the file?

Viewing 2 replies - 1 through 2 (of 2 total)

Plugin Author OllieJones
(@olliejones)

6 months ago

Thanks for the question.

SQLite has a weird possibility when compared to other DBMS types. It’s possible to try to read it with different versions of the database engine. If you look at Settings > Object Cache > Statistics and you see a list of items in the cache, you can be sure it’s working with your web server.

Two things are possible:

One is a version skew between the SQLite database engine in your php and the one in DB Browser. I don’t think that’s very likely, though because there’s a lot of forward and backward compatibility between database engines.

The other is some kind of permission collision between your web server and your desktop GUI account. On a typical Linux system the web server runs with user www-data:www-data. If you try to access the .sqlite file with a different user you’ll get a permission problem. It’s possible your desktop user can’t read the file at all, in which case it might tell you it’s malformed.
Thread Starter islp
(@islp)

6 months ago
Hi @olliejones , first of all thanks for the detailed answer. I don’t know if this is related to this issue, but in the site health screen I get:
Page cache is not detected but the server response time is OK Performance

Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.

Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.
- Median server response time was 191 milliseconds. This is less than the recommended 600 milliseconds threshold.
- No client caching response headers were detected.
- A page cache plugin was not detected.
Could this eventually be related in some way?

[update] sorry, don’t consider this question, it is completely unrelated 🙂
- This reply was modified 6 months ago by islp.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Could not open database file’ is closed to new replies.

Tags