Migration 23 to 24 #2545

Closed
opened 2024-07-10 06:31:46 +00:00 by hackschnitzel09 · 4 comments

Description

Hi, when upgrading the docker image von version 0.23.0 to 0.24.0 I get a "migration error, table.reaction does not exits". Has anyone encountered the same issue?
Is it enought to just create that table? Is there a migration guide? I wasnt able to find one at the moment.

Vikunja Version

0.23.0 to 0.24.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description Hi, when upgrading the docker image von version 0.23.0 to 0.24.0 I get a "migration error, table.reaction does not exits". Has anyone encountered the same issue? Is it enought to just create that table? Is there a migration guide? I wasnt able to find one at the moment. ### Vikunja Version 0.23.0 to 0.24.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
hackschnitzel09 added the
kind/bug
label 2024-07-10 06:31:46 +00:00
Owner

The table should be created automatically. Can you check the contents of the migrations table?

The table should be created automatically. Can you check the contents of the `migrations` table?

Hi
the table exists but when I click on it #1932 - table doesn't exist in engine
The project_views, task_buckets and task_position table throws the same error

I am running on docker. I guess the latest migrations did not happen?

the migration content:
SCHEMA_INIT
20190324205606
20190328074430
20190430111111
20190511202210
20190514192749
20190524205441
20190718200716
20190818210133
20190920185205
20190922205826
20191008194238
20191010131430
20191207204427
20191207220736
20200120201756
20200219183248
20200308205855
20200308210130
20200322214440
20200322214624
20200417175201
20200418230432
20200418230605
20200420215928

Hi the table exists but when I click on it #1932 - table doesn't exist in engine The project_views, task_buckets and task_position table throws the same error I am running on docker. I guess the latest migrations did not happen? the migration content: SCHEMA_INIT 20190324205606 20190328074430 20190430111111 20190511202210 20190514192749 20190524205441 20190718200716 20190818210133 20190920185205 20190922205826 20191008194238 20191010131430 20191207204427 20191207220736 20200120201756 20200219183248 20200308205855 20200308210130 20200322214440 20200322214624 20200417175201 20200418230432 20200418230605 20200420215928

I guess a migration did not work properly.
I have managed to get things running again by deleting the *.frm and *.ibd Files but now my kanban view is empty.
In the logs I see handler/ReadAllWeb 49b status: 400 response: {"message": "Could not find a filter field named buckets in the schema."}

Which migrations need to run between 23 and 24.1? My backup already included the currupted files so I have to delete and remigrate I guess

I guess a migration did not work properly. I have managed to get things running again by deleting the *.frm and *.ibd Files but now my kanban view is empty. In the logs I see `handler/ReadAllWeb 49b status: 400 response: {"message": "Could not find a filter field named `buckets` in the schema."}` Which migrations need to run between 23 and 24.1? My backup already included the currupted files so I have to delete and remigrate I guess

I gave it another try. I disabled typesense and metrics and now it came up sucessfully after manually removing the mentioned tables :)

I gave it another try. I disabled typesense and metrics and now it came up sucessfully after manually removing the mentioned tables :)
Sign in to join this conversation.
No Milestone
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vikunja/vikunja#2545
No description provided.