-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Unrecoverable 500 Error (with readonly database) #2325
Comments
Had the same issue. Fixed after restart 👍
|
User has been able to provoke the issue again. I can repro: Clicking on 'top rated' gives this message for the url:
|
Thanks. this is something I can look after |
The problem occurs if the user tries to rename a author in the books table. I'll fix this. Side question: If you are having a read only database, why do you allow users to edit books? |
Please update to the newest nightly version (there should be a docker image for this) and the application should not crash any more |
I can still provoke the issue. from docker inspect of the container:
Apart from the admin account no user is allowed to edit books. I don't think I can disable it for admin. I have rolled back to previous releases and found the following: This version doesn't 500 when I visit the top rated page:
And this is the first one where I get the 500:
Let me know I I can help with any other details. PS: Thanks for looking into this. Such a useful piece of software. |
Yes you can, also the admin can't edit the books. It's possible to remove the rights from admin. Admin doesn't me the account has all rights, it can only get all rights |
I think I found it |
I think you are having a database error, book 449 has two "author sort" strings, which aren't matching any entry in the authors table. The relevant authors having the number 201 and 200. Book 449 is displayed in the rated section on the first page, on the other pages it's displayed on one of the later pages. The newest nightly version from now can deal with this. Don't forget to backup before doing changes If you are happy, please close the issue |
🥳 Nightly image no longer throws 500 when I go to top-rated. Thank you! Also thanks for the tip with the db. I'll investigate that. |
@MinchinWeb Does this also fix it for you? I can't close the issue. Could you please close it if it resolves the issue for you as well? |
@erkannt Yes, the nightly version seems to fix this! @OzzieIsaacs Thanks you for the amazingly fast fix! |
Describe the bug/problem
Calibre-web's epub reader stopped working for a user, and just spits out a stack trace and returns an HTTP 500 error. Reloading the page (or any page) won't let the user get past it.
To Reproduce
Steps to reproduce the behavior:
Stack Trace
This is the "error" webpage the user got.
Logfile
Sorry, I don't have one.
Expected behavior
Re-loading the page should allow calibre-web to recover.
Screenshots
see stack trace
Environment (please complete the following information):
0.6.16-ls150 Build-date:- 2022-03-01T10:44:08+01:00
, so sometime before that.Additional context
Add any other context about the problem here. [e.g. access via reverse proxy, database background sync, special database location]
Trimmed docker-compose:
The text was updated successfully, but these errors were encountered: