Skip to content
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

loop login #2351

Closed
404gods opened this issue Mar 27, 2022 · 7 comments
Closed

loop login #2351

404gods opened this issue Mar 27, 2022 · 7 comments

Comments

@404gods
Copy link

404gods commented Mar 27, 2022

I used the docker version of calibre-web and used the CDN service. I found that there would be a problem after about a day. After logging in, the user still returned to the login interface, and it was logged in circularly, unable to come to the console, there was no error in the logs, and it will return to normal after restarting the container, I don't know where the problem is.sorry for my bad English .

@AnonTester
Copy link
Contributor

debug log of login-loop on my system may be related. It appears that sometimes the db is locked and thus cannot store login details.
login-issue-locked-db-sesson-not-saved-calibre-web.log

@404gods
Copy link
Author

404gods commented Mar 28, 2022

我的系统上的登录循环的调试日志可能相关。有时数据库似乎被锁定,因此无法存储登录详细信息。 login-issue-locked-db-sesson-not-saved-calibre-web.log

Yes, I also found the same log content, it seems we have the same problem.

@LordZappZarapp
Copy link

Same here.
Running Calibre-web (0.6.17) in LXC-Container using Debian 11
Calibre.txt

@LordZappZarapp
Copy link

Issue #2350 and #2351 seem to be the same Problem.
The Logs are very similar.

OzzieIsaacs added a commit that referenced this issue Mar 29, 2022
Fix for #2309 (long unicode filenames could get to long)
@OzzieIsaacs
Copy link
Collaborator

If possible for you please try to update to the newest nightly version or alternatively if possible try to uninstall gevent

@LordZappZarapp
Copy link

If possible for you please try to update to the newest nightly version or alternatively if possible try to uninstall gevent

I switched to the latest nightly and could not recreate the error. Thanks a lot!

@OzzieIsaacs
Copy link
Collaborator

Awesome, was a tricky issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants