-
-
Notifications
You must be signed in to change notification settings - Fork 340
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
Both regular scan and force scan error out #3408
Comments
This does not seem to happen on the current nightly release |
This apparently still happens in the current nightly. |
Not sure if this the same issue or something that needs a separate issue but I am experiencing something similar on both Scoop and Docker installs on Windows. My books are on a Windows mount if that makes a difference. No new books can be added and it errors out reading metadata on existing books when doing a forced scan.
|
Getting the same error as Yaiba. Install is on a Debian LXC container, using a TrueNAS drive for manga storage. |
What happened? What did you expect? Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists. What operating system is Kavita being hosted from? If the issue is being seen on Desktop, what OS are you running where you see the issue? If the issue is being seen in the UI, what browsers are you seeing the problem on? If the issue is being seen on Mobile, what OS are you running where you see the issue? If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on? Relevant log output:
|
What happened?
Scan starts and finishes a couple of seconds later, not picking up on new Comics.
What did you expect?
Scan to take longer than a few seconds and pick on new Comics.
Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.
0.8.4 - Stable
What operating system is Kavita being hosted from?
Docker (Dockerhub Container)
If the issue is being seen on Desktop, what OS are you running where you see the issue?
None
If the issue is being seen in the UI, what browsers are you seeing the problem on?
No response
If the issue is being seen on Mobile, what OS are you running where you see the issue?
None
If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?
No response
Relevant log output
Additional Notes
No response
The text was updated successfully, but these errors were encountered: