Quote:
Originally Posted by mariosipad
@BJH
The only "solution" I can come up with is access rights.
Try to change the access rights to the calibre library to 777, then check if it works, then try 755 and so on.
COPS typically says it cannot find the database files if it cannot read or execute these files.
|
Thanks once again for the response mariospiad.
I can definitely see why you would offer permissions as a potential cause. It was one of the first things I checked, but I ruled it out because the current permissions for the Ebooks folder (which contains the metadata file) is:
I believe these are the correct permissions, because read is allowed for 'other' groups. It seems like it should be possible for COPS to read the file. But I don't claim to be an expert here, so if you or anyone else has some advice to offer on this it will be welcome.
The metadata.db file has similar permissions, except that it isn't "executable". I can't believe that it would need to be because it's just a data file. The permissions for metadata.db are:
The only difference in terms of the file attributes between the library that is currently working (exists in the same directory as COPS) and the library that is not working (exists in the ownCloud directory) is the owner of the file. For the working library, it is as follows:
Code:
-rw-r--r-- 1 root root 1490944 Jan 2 16:36 metadata.db
For the non-working (ownCloud) library, it is as follows:
Code:
-rw-r--r-- 1 www-data www-data 1490944 Mar 17 06:49 metadata.db
I have assumed this isn't a problem, because all users have permissions to read the file?