Hi OpenObserve community, I am trying to restore an OpenObserve instance from an EFS backup, but the container fails during database initialization with this error:

Error: backend job init failed, exiting

db init failed: Custom Error:
Migration file of version 'm20260622_000001_add_org_id_to_short_urls' is missing,
this migration has been applied but its file is missing

DB_SCHEMA_VERSION mismatch : expected 45, found 46; running db upgrade

Environment: • OpenObserve image:

public.ecr.aws/zinclabs/openobserve:v0.91.5

• Previous deployment was using: •

public.ecr.aws/zinclabs/openobserve:latest

• The previous deployment was running successfully until last Friday. • The last ECS deployment before the issue was around May 25, 2026. • Data is restored from EFS backup. I checked the SQLite migration table:

SELECT * FROM seaql_migrations ORDER BY version;

and it contains:

m20260622_000001_add_org_id_to_short_urls|1782944723

So the database shows that this migration was applied, but the OpenObserve binary cannot find the migration file. Does anyone could provide some hints?

Hey @José Daniel Ramos Chaves looking into it, coming back in couple of minutes

@José Daniel Ramos Chaves - The Migration is fine and it is still active. The real issue is that you moved from the

latest

image to

v0.91.5

, and that is actually a downgrade for your database. Our

latest

is a release candidate for

v0.92

and we are currently in the testing/beta phase for that. So you can either use that beta version (might have unresolved bugs) or you can keep using it with the manual row deletion that is already done as I read your messages.

Regarding that particular migration file,

m20260622_000001_add_org_id_to_short_urls

was added in PR #12829 on 2026-06-23. It adds an

org_id

column to the

short_urls

table so short URLs can be scoped to an organization. It was never removed or reverted. It exists in every build from that date onward, including our current code. The reason your image doesn't have it is simply that

v0.91.5

was built before that date, so the migration file isn't compiled into it.

Once, we make a fresh stable release, the db issue will handle itself Cc - @Gorakhnath Yadav (OpenObserve) @Yashodhan @Prabhat Sharma

Hi @Shrinath Rao I initially thought that was the issue as well. However, after checking ECR, I noticed that the

latest

tag is actually pointing to version 0.91.1. As part of my troubleshooting, I updated the ECS task definition to pin the image to 0.91.5 instead of using

latest.

Let me look into this and revert ! @José Daniel Ramos Chaves

Thanks a lot for all your help! @Shrinath Rao

@José Daniel Ramos Chaves - We just shipped

v0.92.0

! Try if upgrading the version helps your case !

Thanks @Shrinath Rao will be trying today and let you know the outcome !