Closed noisyparker closed 5 years ago
As your database is sooo old I would suggest just starting with a new one rather than rebuilding it. It can be fixed manually but it may not be a trivial task. The current error you are getting is that we expect entries in the "seriesauthors" table to be unique, and in your database they are not. In addition some of the later updates are quite time consuming as you have seen.
You will lose your "wanted" books doing this, but if you want to keep them, export them from your old database first. You can start lazylibrarian ignoring the upgrade to do this, then go to the manage page and export csv.
If you stop lazylibrarian and delete your database, then restart lazylibrarian you will have a new clean database at level 44 (better still, switch to the new source over on gitlab and get a new level 46 database). Once you have a new database, run libraryscan on ebooks, magazines, audiobooks as appropriate to repopulate. If your cache is fairly up-to-date we will read most of the info from there, so it should be fairly quick, depending on how many authors/books. Once the database is rebuilt, go back to manage page and import csv to mark your wanted books as wanted again. Hope this helps.
My situation will be a weird one, since my lazylibrarian updates got stalled without my noticing it, and once I addressed the issue that was preventing them, the dbupdate script was faced with the task of updating the db from 21 to 44.
It proceeded gamely, but failed in the updates for v37:
To help with identifying and fixing issues, please include as much information as possible, including:
LazyLibrarian version number (at the bottom of config page)
ddeeb9faedff7c9b93d1c50fb98a13ca1e15e1b3 (the version it had long been stalled at was 8c53a90f8f6d13053a89d9d6a072ee120188a69e)
Operating system used (windows, mac, linux, NAS type)
linux
Interface in use (default, bookstrap)
legacy
Which api (Goodreads, GoogleBooks, both)
Goodreads
Source of your LazyLibrarian installation (git, zip file, 3rd party package)
git
Relevant debug log with api keys and any passwords redacted
I have to restart the server and wait through hours of some kind of update before it gets to the dbupgrade part. I can try to get a debug log with that but, in the meantime, there is the dbupgrade.log I quoted above, and here is the lazylibrarian.log from the end where the dbupgrade.py error occurred: lazylibrarian.log.zip
Please note - usually a single line of log is not sufficient. The lines just before the error occurs can give useful context and greatly assist with debugging.
There is a built-in debug log creator on the logs page which makes it easy to provide this information