Gvmd migration error

Building from Source and Advanced Topics
1

Hi! I have an issue with update. Gvmd container not start with log:

md main:MESSAGE:2026-06-01 13h03.19 utc:35: Greenbone Vulnerability Manager version 26.28.0 (DB revision 274)
md manage:MESSAGE:2026-06-01 13h03.19 utc:35: check_db_versions: database version of database: 273
md manage:MESSAGE:2026-06-01 13h03.19 utc:35: check_db_versions: database version supported by manager: 274
md main:CRITICAL:2026-06-01 13h03.19 utc:35: gvmd: database is wrong version
md main:CRITICAL:2026-06-01 13h03.19 utc:35: gvmd: Your database is too old for this version of gvmd.
md main:CRITICAL:2026-06-01 13h03.19 utc:35: gvmd: Please migrate to the current data model.
md main:CRITICAL:2026-06-01 13h03.19 utc:35: gvmd: Use a command like this: gvmd --migrate

gvmd --migrate log:

md main:MESSAGE:2026-06-01 11h08.06 utc:1: Greenbone Vulnerability Manager version 26.28.0 (DB revision 274)
md main: INFO:2026-06-01 11h08.06 utc:1: Migrating database.
md main: INFO:2026-06-01 11h08.06 utc:1: Migrating to 274
md manage:WARNING:2026-06-01 11h08.06 utc:1: sql_exec_internal: PQexec failed: ERROR: relation “asset_snapshots” does not exist
(7)
md manage:WARNING:2026-06-01 11h08.06 utc:1: sql_exec_internal: SQL: CREATE TABLE IF NOT EXISTS asset_snapshot_identifiers (id SERIAL PRIMARY KEY, asset_snapshot integer REFERENCES asset_snapshots (id) ON DELETE CASCADE, identifier_type integer NOT NULL, identifier_value text NOT NULL, creation_time integer NOT NULL, modification_time integer NOT NULL, UNIQUE (asset_snapshot, identifier_type, identifier_value));
md manage:WARNING:2026-06-01 11h08.06 utc:1: sqlv: sql_exec_internal failed

How to fix?

2

I’m experiencing the same issue. I just pulled new container images (including gvmd) but the issue persists.

md   main:MESSAGE:2026-06-03 13h33.19 utc:1:    Greenbone Vulnerability Manager version 26.29.0 (DB revision 276)
md   main:   INFO:2026-06-03 13h33.19 utc:1:    Migrating database.
md   main:   INFO:2026-06-03 13h33.19 utc:1:    Migrating to 274
md manage:WARNING:2026-06-03 13h33.19 utc:1: sql_exec_internal: PQexec failed: ERROR:  relation "asset_snapshots" does not exist
 (7)
md manage:WARNING:2026-06-03 13h33.19 utc:1: sql_exec_internal: SQL: CREATE TABLE IF NOT EXISTS asset_snapshot_identifiers (id SERIAL PRIMARY KEY,  asset_snapshot integer    REFERENCES asset_snapshots (id) ON DELETE CASCADE,  identifier_type integer NOT NULL,  identifier_value text NOT NULL,  creation_time integer NOT NULL,  modification_time integer NOT NULL,  UNIQUE (asset_snapshot, identifier_type, identifier_value));
md manage:WARNING:2026-06-03 13h33.19 utc:1: sqlv: sql_exec_internal failed
3

Usually it is the best to discuss such SQL / error state situations directly with the development team (which is mostly not reachable via this community forums) directly via the issue trackers of the affected component over at GitHub: Greenbone · GitHub

In this case some one seems to have already raised an issue here which could be monitored for any suggestions or possible fixes:

1 Like
4

Seems this got fixed now already in the PR below and probably will be included in one of the next releases.