Install from source error with "public.meta"

Building from Source and Advanced Topics
1

Hi, All.
Build from source by following manual:

And when I try to create admin user, Ihave following error in /var/log/gvm/gvmd.log:

md manage:WARNING:2024-02-26 14h28.25 utc:18940: sql_exec_internal: SQL: SELECT value FROM public.meta WHERE name = 'database_version';
md manage:WARNING:2024-02-26 14h28.25 utc:18940: sql_x: sql_exec_internal failed
md manage:MESSAGE:2024-02-26 14h28.25 utc:18940: No SCAP database found
md manage:MESSAGE:2024-02-26 14h28.25 utc:18940: No CERT database found
md manage:MESSAGE:2024-02-26 14h28.25 utc:18940: db_extension_available: Extension 'pg-gvm' is not available.
md manage:WARNING:2024-02-26 14h28.25 utc:18940: check_db_extensions: A required extension is not available.
md manage:WARNING:2024-02-26 14h28.25 utc:18940: init_manage_create_functions: failed to create functions
md   main:MESSAGE:2024-02-26 14h28.25 utc:18942:    Greenbone Vulnerability Manager version 23.2.0 (DB revision 255)
md manage:WARNING:2024-02-26 14h28.25 utc:18942: sql_exec_internal: PQexec failed: ERROR:  relation "public.meta" does not exist
LINE 1: SELECT value FROM public.meta WHERE name = 'database_version...
                          ^
 (7)
md manage:WARNING:2024-02-26 14h28.25 utc:18942: sql_exec_internal: SQL: SELECT value FROM public.meta WHERE name = 'database_version';
md manage:WARNING:2024-02-26 14h28.25 utc:18942: sql_x: sql_exec_internal failed
md manage:MESSAGE:2024-02-26 14h28.25 utc:18942: No SCAP database found
md manage:MESSAGE:2024-02-26 14h28.25 utc:18942: No CERT database found
md manage:MESSAGE:2024-02-26 14h28.25 utc:18942: db_extension_available: Extension 'pg-gvm' is not available.
md manage:WARNING:2024-02-26 14h28.25 utc:18942: check_db_extensions: A required extension is not available.
md manage:WARNING:2024-02-26 14h28.25 utc:18942: init_manage_create_functions: failed to create functions

Installed SQL packages
postgresql-server-dev-15
postgresql-16
postgresql-client-15
postgresql-client-16
postgresql-client-common
postgresql-common
postgresql

2

Problem was solved by uninstall postgres 16 and install postgres 15.

2 Likes
3

Actually the correct solution for this problem would be to:

  1. keep PostgreSQL 16
  2. Make sure that the older PostgreSQL database has been “upgraded” to 16 (see e.g. pg_upgradecluster here in the forums or in the documentation)
  3. wipe all PostgreSQL 15 packages (including any “development” or “header” files)
  4. install Building 22.4 from Source - Greenbone Community Documentation

Otherwise you very likely keep an outdated PostgreSQL 15 installation which usually doesn’t receive any (security) updates anymore.

3 Likes