Extension "pg-gvm" has no update path

Building from Source and Advanced Topics
1

Hi,
I just rebuit GVM on a debian 11 server using:
export GVM_LIBS_VERSION=22.6.3
export GVMD_VERSION=22.6.0
export PG_GVM_VERSION=22.6.0
export GSA_VERSION=22.5.3
export GSAD_VERSION=22.5.1
export OPENVAS_SMB_VERSION=22.5.3
export OPENVAS_SCANNER_VERSION=22.7.3
export OSPD_OPENVAS_VERSION=22.5.3
export NOTUS_VERSION=22.5.0

GVMD would not start and in the gvmd logs i see:

md manage:MESSAGE:2023-07-26 07h47.22 utc:5572: check_db_versions: database version supported by manager: 255
md   main:CRITICAL:2023-07-26 07h47.22 utc:5572: gvmd: database is wrong version
md   main:MESSAGE:2023-07-26 07h47.22 utc:5575:    Greenbone Vulnerability Manager version 22.6.0 (DB revision 255)
md manage:MESSAGE:2023-07-26 07h47.22 utc:5575: check_db_versions: database version of database: 250
md manage:MESSAGE:2023-07-26 07h47.22 utc:5575: check_db_versions: database version supported by manager: 255
md   main:CRITICAL:2023-07-26 07h47.22 utc:5575: gvmd: database is wrong version
md   main:MESSAGE:2023-07-26 07h47.22 utc:5577:    Greenbone Vulnerability Manager version 22.6.0 (DB revision 255)
md manage:MESSAGE:2023-07-26 07h47.22 utc:5577: check_db_versions: database version of database: 250
md manage:MESSAGE:2023-07-26 07h47.22 utc:5577: check_db_versions: database version supported by manager: 255
md   main:CRITICAL:2023-07-26 07h47.22 utc:5577: gvmd: database is wrong version

so I ran “gvmd -m” but wasn’t very successful:

(gvmd:5130): md manage-WARNING **: 09:44:51.896: sql_exec_internal: PQexec failed: ERROR: extension "pg-gvm" has no update path from version "22.4.0" to version "22.6"

Any suggestions how to fix/solve this?

1 Like
2

This should be a duplicate of the existing topic here (i know that this topic is in the community containers category but the containers itself are not the problem):

3

To circumvent this fix you should downgrade to pg-gvm 22.5.1 for now. I’ll take a look at the issue today.

3 Likes
4

works for me.
thanks for the fast reply, much appreciated!

5

Should be fixed with the new pg-gvm 22.6.1 release.

3 Likes
6

also for docker image?

7

yes. the container images get published automatically after a new release.

1 Like
8

I can confirm that the problem is fixed in the pg-gvm 22.6.1 release. Thank you @bricks!

1 Like