Hello, I have been having issues with the most recent Kali Linux update as it has changed the base version of PSQL therefore breaking the gvm-setup script.
I have installed an older kali version wich has the older PSQL version before upgrading and installed gvm as normal. The whole setup sctipt ran with no errors and gvm-check setup is giving me the ‘It seems like your GVM-23.11.0 installation is OK’ message. The issue is that when I log in to the GUI I only have 3 tabs with no dropdown menus…
When trouble shooting software application bugs, the standard process is to start by looking for some clues about what the problem might be. These clues are typically found in the log files. The log files for gvm are located in the /var/log/gvm directory. You should look for items with an error or fatal error status.
My best guess is that you have more than one version of PostgreSQL running on the Kali Linux instance. I believe that gvm-check-status may only check that there is a version of PostgtreSQL running on port 5432. However, since you downgraded some packages, you may have inadvertently swapped the version of PostgreSQL running on port 5432.
That would be a good guess, but I actually just installed an older version of kali from the ground up and then didnt upgrade the to the most recent update package.
I am trying to look through logs to find errors but I was wondering if that is a known issue with the recent kali updates?
Oh, that would be an issue you need to scan the forum for. When posting to the forum, it’s important to provide technical details so others can truly understand your situation. Otherwise, we cannot relate to your issue(s). For example, which version of Kali did you install on? As a VM? You can also post details as formatted text, such as log errors, or the output of gvm-check-setup.
I have been looking for a post about the new kali PSQL version but haven’t found one yet… Is there somewhere you suggest i start a topic for that issue? I havent been desperate enough for an answer until today
I added the technical specs to the OP
The only error I can find in the logs is in gvmd.log: sql_exec_internal: PQexec failed: ERROR: tuple concurrently updated (7)
Here is the gvm-check-setup output after full-upgrade as suggested in the linked bug tracker post:
Test completeness and readiness of GVM-23.11.0
Step 1: Checking OpenVAS (Scanner)...
OK: OpenVAS Scanner is present in version 23.8.5.
OK: Notus Scanner is present in version 22.6.4.
OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.
Checking permissions of /var/lib/openvas/gnupg/*
OK: _gvm owns all files in /var/lib/openvas/gnupg
OK: redis-server is present.
OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock
OK: the mqtt_server_uri is defined in /etc/openvas/openvas.conf
OK: _gvm owns all files in /var/lib/openvas/plugins
OK: NVT collection in /var/lib/openvas/plugins contains 92176 NVTs.
OK: The notus directory /var/lib/notus/products contains 469 NVTs.
Checking that the obsolete redis database has been removed
OK: No old Redis DB
OK: ospd-openvas service is active.
OK: ospd-OpenVAS is present in version 22.7.1.
Step 2: Checking GVMD Manager ...
OK: GVM Manager (gvmd) is present in version 23.8.1.
Step 3: Checking Certificates ...
OK: GVM client certificate is valid and present as /var/lib/gvm/CA/clientcert.pem.
OK: Your GVM certificate infrastructure passed validation.
Step 4: Checking data ...
OK: SCAP data found in /var/lib/gvm/scap-data.
OK: CERT data found in /var/lib/gvm/cert-data.
Step 5: Checking Postgresql DB and user ...
OK: Postgresql version and default port are OK.
WARNING: database "postgres" has a collation version mismatch
DETAIL: The database was created using collation version 2.38, but the operating system provides version 2.40.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
gvmd | _gvm | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | |
WARNING: database "gvmd" has a collation version mismatch
DETAIL: The database was created using collation version 2.38, but the operating system provides version 2.40.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE gvmd REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
16436|pg-gvm|10|2200|f|22.6||
Database is wrong version.
ERROR: Database is wrong version. You have installed a new gvmd version
FIX: Run 'sudo runuser -u _gvm -- gvmd --migrate'
ERROR: Your GVM-23.11.0 installation is not yet complete!
Here are the results of the sudo runuser -u _gvm – gvmd --migrate command:
WARNING: database "gvmd" has a collation version mismatch
DETAIL: The database was created using collation version 2.38, but tting system provides version 2.40.
HINT: Rebuild all objects in this database that use the default colld run ALTER DATABASE gvmd REFRESH COLLATION VERSION, or build Postgre the right library version.
WARNING: database "gvmd" has a collation version mismatch
DETAIL: The database was created using collation version 2.38, but tting system provides version 2.40.
HINT: Rebuild all objects in this database that use the default colld run ALTER DATABASE gvmd REFRESH COLLATION VERSION, or build Postgre the right library version.
Warning: program compiled against libxml 212 using older 209
Warning: program compiled against libxml 212 using older 209
