github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #103] Update via docker: Migration Error 1064 #5971

New Issue
Closed
opened 2026-04-20 16:26:30 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-20 16:26:30 -05:00
Owner
Copy Link

Originally created by @m50434 on GitHub (Dec 23, 2023).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/103

Description

Hi,
I just updated Vikunja API ("latest" in Docker) and im getting the following error when starting the container:

migration/Migrate 052 Migration failed: migration 20221113170740 failed: Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'COLUMN list_id TO project_id' at line 1

Any ideas what to do?

Vikunja Frontend Version

latest

Vikunja API Version

latest

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @m50434 on GitHub (Dec 23, 2023). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/103 ### Description Hi, I just updated Vikunja API ("latest" in Docker) and im getting the following error when starting the container: migration/Migrate 052 Migration failed: migration 20221113170740 failed: Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'COLUMN `list_id` TO `project_id`' at line 1 Any ideas what to do? ### Vikunja Frontend Version latest ### Vikunja API Version latest ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:26:31 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 23, 2023):

Which mariadb version are you using?

<!-- gh-comment-id:1868270047 --> @kolaente commented on GitHub (Dec 23, 2023): Which mariadb version are you using?
GiteaMirror commented 2026-04-20 16:26:32 -05:00
Author
Owner
Copy Link

@m50434 commented on GitHub (Dec 23, 2023):

mariadb 10.3.32 - 1040 (Im using Synology NAS. The system says its the newest version)

<!-- gh-comment-id:1868270679 --> @m50434 commented on GitHub (Dec 23, 2023): mariadb 10.3.32 - 1040 (Im using Synology NAS. The system says its the newest version)
GiteaMirror commented 2026-04-20 16:26:33 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 23, 2023):

Looks like your mariadb version is too old. You need at least 10.5.2 to run that migration.

10.3.32 was released in late 2021, you'll probably want to upgrade that anyway (even if Synology does not offer a newer version directly).

For Vikunja, you could switch to sqlite, probably the resource-friendlier option for a nas anyway.

<!-- gh-comment-id:1868278981 --> @kolaente commented on GitHub (Dec 23, 2023): Looks like your mariadb version is too old. You need at least 10.5.2 to run that migration. 10.3.32 was released in late 2021, you'll probably want to upgrade that anyway (even if Synology does not offer a newer version directly). For Vikunja, you could switch to sqlite, probably the resource-friendlier option for a nas anyway.
GiteaMirror commented 2026-04-20 16:26:34 -05:00
Author
Owner
Copy Link

@m50434 commented on GitHub (Dec 23, 2023):

Thanks for your fast reply.

Im sorry. I was using an old Firmware for the Synoloy as well. Therefore I couldnt update MariaDB.

Anyway, now I updated MariaDB (its now 10.11) and the vikunja-api seems to be fine (the log says the migration was succesful and there are no more errors).

Unfortunately something is wrong with the frontend:
If Im try to access vikunja I got a "502 Bad Gateway error".

The log of the frontend is "/bin/sh: /run.sh: not found".

<!-- gh-comment-id:1868325691 --> @m50434 commented on GitHub (Dec 23, 2023): Thanks for your fast reply. Im sorry. I was using an old Firmware for the Synoloy as well. Therefore I couldnt update MariaDB. Anyway, now I updated MariaDB (its now 10.11) and the vikunja-api seems to be fine (the log says the migration was succesful and there are no more errors). Unfortunately something is wrong with the frontend: If Im try to access vikunja I got a "502 Bad Gateway error". The log of the frontend is "/bin/sh: /run.sh: not found".
GiteaMirror commented 2026-04-20 16:26:36 -05:00
Author
Owner
Copy Link

@m50434 commented on GitHub (Dec 23, 2023):

Me again:
I installed a new frontend-container (with the same preferences). Now it works.

<!-- gh-comment-id:1868336958 --> @m50434 commented on GitHub (Dec 23, 2023): Me again: I installed a new frontend-container (with the same preferences). Now it works.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#5971
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?