dbconfig-common: writing config to /etc/dbconfig-common/gvmd-pg.conf
dbconfig-common: flushing administrative password
migrating the postgresql database...
(gvmd-pg:12180): md manage-WARNING **: 07:40:52.130: sql_open: PQconnectPoll failed
(gvmd-pg:12180): md manage-WARNING **: 07:40:52.130: sql_open: PQerrorMessage (conn): could not connect to server: Connection refused
Is the server running on host "localhost" (::1) and accepting
TCP/IP connections on port 5432?
could not connect to server: Connection refused
Is the server running on host "localhost" (127.0.0.1) and accepting
TCP/IP connections on port 5432?
(gvmd-pg:12180): md manage-WARNING **: 07:40:52.130: init_manage_open_db: sql_open failed
Creating admin user...
Prime generation might be too slow. To make it faster it is a good idea to perform some other action (type on the keyboard, move the mouse, utilize the disks).
Existing certificate infrastructure found, aborting.
Use '-f' parameter to overwrite existing certificates.
Configurazione di openvas-scanner (1:21.4.4-1)...
The user `gvm' is already a member of `redis'.
Configurazione di python3-distupgrade (1:20.04.38)...
Configurazione di locales (2.31-0ubuntu9.9)...
Generating locales (this might take a while)...
Yes, updates to the distro I upgraded postgres but nothing to do. I made all the updates to finally leave only those of openvas, so if I update only the openvas suite does not work.
once you upgrade the postgres version (you should have done with the pg_upgrade tool) you also need to recompile gvm-libs to match the postgres version. maybe you should recompile all components, to have the correct bindings.
First of all, thank you for your reply, however, the package I installed by openvas is not the version to compile, so the error probably as you write is due to the migration to the database. But what to do now?
first of all make sure you have migrated the database, let me just google a howto for you: https://www.kostolansky.sk/posts/upgrading-to-postgresql-12/
change it to your needs. don’t forget to configure your new postgres for the gvm needs (pg_hba.conf…) (also disable jit compiler for postgres etc.) normally you can copy the configuration files to the new DB.
than what you in the most cases need todo is compile the packages again:
You should contact https://github.com/admirito and ask him to update the packages so that everything match together. Or you keep your old version of postgres, if he is not provide the source to compile it again.