-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Server crash during quick match #2650
Comments
Usually issues like this are related to the sqlite db being stored on a network drive. The sqlite db has to be on a local drive. |
The database is at "C:\Users\D-Admin\AppData\Local\Audiobookshelf\config\absdatabase.sqlite". |
I have not thouroughly checked the scan logs yet, but I have an intuition that this has to do with some addition->deletion->re-addition sequence. |
These unique constraint errors are usually from race conditions |
OK, I was able to reproduce it, and this one has nothing to do with race conditions, just a standard logic bug. TLDR: The bug is caused by duplicate authors extracted from the quick match result. I ran a quick match on a test book, using the same original title that was used in the original bug report for the quick match search on Google Books. The quick match result had the following author:
Then the following happens:
As you can see, the unique contraint error happens when we try to insert the BookAuthors table entry with the second instance of author I'll take a stab at fixing this (by not adding duplicate entries). There's also the separate issue of having Ph.D and other author titles separated from the author name by the simple comma-separation logic. I'll address that in a separate bug. |
Fixed in v2.8.1 |
The same issue appeares during Library Scan whet `General InformationID: 123 Media InformationSource: Book Description` |
Thanks for reporting. I'll handle this. |
Are you sure #3670 fixes the complaint above? The issue seems to be a SequelizeUniqueConstraintError when metadata is read from an nfo file containing duplicate authors. |
No it doesn't fix this issue. I meant to say that is the PR I opened to fix the issue in #3668. I thought it was relevant since there may be overlap in what you are working on but I wasn't clear in what I meant. |
Got it, thanks. I'll use your changes when working on this. |
@mikiher Are you still working on this? |
Not recently. I think this is still an issue. Can you reopen and assign this to me? |
Describe the issue
This was reported in an audiobookshelf-windows issue.
Combined audiobookshelf-windows log (app + server): logfile.txt
Library scan logs from just before the crash:
Some log lines before the crash and the crash message itself (from logfile.txt):
Steps to reproduce the issue
I don't fully understand what happened here yet, so I'm not sure how to reproduce.
Audiobookshelf version
v2.7.2
How are you running audiobookshelf?
Windows Tray App
The text was updated successfully, but these errors were encountered: