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

UpgradeIndex execution failed on every restart #1603

Closed
5 tasks done
lambdareader opened this issue Jun 8, 2024 · 2 comments
Closed
5 tasks done

UpgradeIndex execution failed on every restart #1603

lambdareader opened this issue Jun 8, 2024 · 2 comments
Labels
bug Something isn't working has workaround released

Comments

@lambdareader
Copy link

lambdareader commented Jun 8, 2024

Steps to reproduce

deleted lucene folder
started komga.jar
restarted
restarted again

Expected behavior

no exception / error in log

Actual behavior

every restart komga throws an exception.
It says it failed to upgrade the series index and throws it again next restart.

EDIT:
i downgraded to 1.11.0 and it works.
After letting the index rebuild and restarting there are no errors.
so i started it with 1.11.1 and it works, but as soon as i delete the lucene folder the same error happens.

1.11.0 deleted lucene folder: rebuilds with no problems
1.11.1 deleted lucene folder: 'java.lang.IllegalStateException: do not share IndexWriterConfig instances across IndexWriters' on every restart

EDIT 2:
tried again deleting and rebuilding (with original database) on 1.11.0 and now it does throw errors.
sometimes just one time. and sometimes every restart.
It is very confusing since i use the same original database.

EDIT 3:
deleted lucene folder again but did not replace the database with the original. it is now fixed more or less. no error messages anymore. but if i try it again with the original database it throws errors.

Logs

https://pastebin.com/jUWWEXJM

Komga version

1.11.1

Operating system

Linux

Installation method

jar

Other details

No response

Acknowledgements

  • I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I have checked the FAQ.
  • I have updated the app to the latest version.
  • I will fill out all of the requested information in this form.
@gotson
Copy link
Owner

gotson commented Jun 11, 2024

in the meantime you can delete the lucene folder and restart.

@gotson gotson added bug Something isn't working has workaround and removed triage labels Jun 12, 2024
@gotson gotson closed this as completed in 90db07c Jul 25, 2024
Copy link
Contributor

🎉 This issue has been resolved in 1.11.2 (Release Notes)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working has workaround released
Projects
None yet
Development

No branches or pull requests

2 participants