Quote:
Originally Posted by DoctorOhh
I haven't attempted this, but if calibre-server has the library opened in dropbox then the metadata.db will be locked and it will not be updated via any external device while locked.
|
I use dropbox as my transport between the machine where I run calibre and the linux server that runs my content server. My experience indicates that dropbox uses a delete and create scheme on linux, which usually avoids the locked file problem. Unfortunately that also means that programs having the deleted file open (e.g., the content server) continue to see the deleted file, not the new file. I get around this by using monit to monitor the changed timestamp of metadata.db, restarting the content server. To be sure that I don't suffer from conflicts I copy the metadata.db file to /tmp and tell calibre to use the copy.
I agree with doctorohh - there must have been a conflict on metadata.db at some point. You need to ensure that all computers are seeing the same files.