MobileRead Forums - View Single Post - Book exists in library error when it doesn't

grantonstar · 07-19-2018, 10:08 PM

Hi,

I'm using Ubuntu 18.04 and Calibre 3.27.1.

I've been trying to mass import my ebooks into a fresh Calibre DB and I am getting the same issue every time.

When I try to add books, frequently I get the following "The following books were not added as they already exist in the database (see --duplicates option):"

The issue is that the books are not in the database. If I do a calibredb --list I can see it is not in the library. Likewise, when I do an "ebook-meta" on the book I can see the data in it is correct and that there is not a record like that in the database.

I've deleted and recreated my database many times. I thought originally it was because I was adding files with the http path to the server location or that I was adding too many at once. So, instead I turned off the calibre daemon and added the files batch by batch locally. That has reduced the issue but it is still occurring.

Any ideas?

Thanks!

07-19-2018, 10:08 PM	#1
grantonstar Junior Member Posts: 3 Karma: 10 Join Date: Jul 2018 Device: Kindle	Book exists in library error when it doesn't Hi, I'm using Ubuntu 18.04 and Calibre 3.27.1. I've been trying to mass import my ebooks into a fresh Calibre DB and I am getting the same issue every time. When I try to add books, frequently I get the following "The following books were not added as they already exist in the database (see --duplicates option):" The issue is that the books are not in the database. If I do a calibredb --list I can see it is not in the library. Likewise, when I do an "ebook-meta" on the book I can see the data in it is correct and that there is not a record like that in the database. I've deleted and recreated my database many times. I thought originally it was because I was adding files with the http path to the server location or that I was adding too many at once. So, instead I turned off the calibre daemon and added the files batch by batch locally. That has reduced the issue but it is still occurring. Any ideas? Thanks!