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

cluster_name_idx missing during db migration 57 -> 58 #454

Closed
wolfpld opened this issue May 6, 2024 · 2 comments
Closed

cluster_name_idx missing during db migration 57 -> 58 #454

wolfpld opened this issue May 6, 2024 · 2 comments
Labels
Milestone

Comments

@wolfpld
Copy link

wolfpld commented May 6, 2024

lms  | [2024-May-06 11:49:16.585] 1 - [info] "config: reading Wt config file: /var/lms/wt_config.xml (location = '/usr/bin/lms')"
lms  | [2024-May-06 11:49:16.585] 1 - [info] - 138353145462752 [MAIN] Starting init web server...
lms  | [2024-May-06 11:49:16.585] 1 - [info] "WServer/wthttp: initializing built-in wthttpd"
lms  | [2024-May-06 11:49:16.588] 1 - [info] "wthttp: started server: http://0.0.0.0:5082"
lms  | [2024-May-06 11:49:16.588] 1 - [info] - 138353145462752 [UTILS] Starting IO context with 2 threads...
lms  | [2024-May-06 11:49:16.589] 1 - [info] - 138353145462752 [DB] Creating connection pool on file /var/lms/lms.db
lms  | [2024-May-06 11:49:16.591] 1 - [info] - 138353145462752 [DB] Preparing tables...
lms  | [2024-May-06 11:49:16.592] 1 - [info] - 138353145462752 [DB] Database version = 57, LMS binary version = 59
lms  | [2024-May-06 11:49:16.592] 1 - [info] - 138353145462752 [DB] Migrating database from version 57 to 58...
lms  | [2024-May-06 11:49:16.593] 1 - [info] "WebController: shutdown: stopping 0 sessions."
lms  | [2024-May-06 11:49:16.593] 1 - [info] "WServer/wthttp: Shutdown: stopping web server."
lms  | Caught std::exception: Sqlite3: DROP INDEX cluster_name_idx: no such index: cluster_name_idx

I was able to work this around by manually creating a dummy cluster_name_idx in db.

@epoupon epoupon added the bug label May 6, 2024
@epoupon
Copy link
Owner

epoupon commented May 6, 2024

I now see the scenario that leads to this :(
Will issue a patch release for this. Thanks for reporting!

@epoupon epoupon added this to the v3.53.1 milestone May 6, 2024
@epoupon
Copy link
Owner

epoupon commented May 6, 2024

Note: another workaround is to first upgrade to v3.52.0, and then to v3.53.0

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

No branches or pull requests

2 participants