mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: Migration failed #3189
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#3189
Reference in New Issue
Block a user
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?
Originally created by @magick93 on GitHub (Jan 16, 2026).
What happened?
Hello
I restarted my docker compose instance, and now it is failing to start. The logs show this error:
Any help is appreciated.
What did you expect to happen?
For the migration to complete succssfully
Steps to reproduce the issue
Unsure how to reproduce. I'm not sure what actual version I was running previously as I was using
latest.Audiobookshelf version
unsure - to latest
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
No response
@Vito0912 commented on GitHub (Jan 16, 2026):
When was the last time you updated/created the stack?
@magick93 commented on GitHub (Jan 16, 2026):
I believe it was 12 April 2025
@nichwall commented on GitHub (Jan 16, 2026):
Do you have any logs from before today to see what version you were running?
@magick93 commented on GitHub (Jan 16, 2026):
Unfortunately I dont have any logs that show the version prior to today.
@sir-wilhelm commented on GitHub (Jan 16, 2026):
If you were on vLatest as of 2025-04-12 then you would have been running v2.20.0.
@magick93 commented on GitHub (Jan 16, 2026):
Ok, I managed to locate the docker image diget. And I was running this image - https://github.com/advplyr/audiobookshelf/pkgs/container/audiobookshelf/438366074?tag=2.25.1
@magick93 commented on GitHub (Jan 16, 2026):
Ok, I've tried with the docker image tagged 2.26.0 and now this is the logs:
@magick93 commented on GitHub (Jan 16, 2026):
I've gone back to the version prior to trying to update and now get this error:
Is it possible to recreate the db file?
@advplyr commented on GitHub (Jan 17, 2026):
Hopefully you have backups.
Try opening the db in something like sqlitestudio.
There are 2 tables that are relevant to migrations.
SequelizeMeta- this stores the migrations that have already been run to make sure they aren't run again. You should see records up to v2.20.0 and not including v2.26.0.migrationsMeta- This stores the current version and the maxVersion. If the current version is greater than the max version than a migration is run.When a migration is run the first step is to copy the migration file into
/config/migrationsfolder. Check that the v2.26.0 migration file is being copied into that folder. From the error it doesn't seem to be.@DrLeh commented on GitHub (Jan 17, 2026):
EDIT: moving configs to local folder solved my issue but is not ideal
i'm having a similar issue, but i'm starting from scratch cause i lost my metadata / config folders somehow at some point. With empty folders, i get this on startup of latest. notably- i am using a NAS to store my metadata/config folders. wonder if thats related.
@advplyr commented on GitHub (Jan 17, 2026):
That is the issue then. The database cannot be stored on a NAS.
@nichwall commented on GitHub (Jan 17, 2026):
To clarify, you cannot store the database on a remote file system. If ABS is running on the same NAS and accessing it through the local filesystem then you can store the database on the NAS.
@magick93 commented on GitHub (Jan 18, 2026):
FYI, I am not using ABS on a NAS.