I’ve been using that install a while now and something has gone wrong after doing normal system updates. Was seeing permission errors in gsad startup Failed to drop privileges so I removed that option from the system service script to get the GUI to start. Then my admin credentials were not recogized. After a reset, I can login but all data is gone with limited menu. I can login to the PostgreSQL database and see all the data is there, could GSA not be using the correct database now? Could someone offer some pointers on what to check or how to get GSA back to my data?
Thanks for the help, I was not able to find upgrading instructions, could you point me to where I can find the warnings next time?
I only have one cluster version 16…
$ pg_lsclusters Ver Cluster Port Status Owner Data directory Log file 16 main 5432 online postgres /var/lib/postgresql/16/main /var/log/postgresql/postgres
I am able to view my data using psql connecting to version 16.4. My gvm-check-setup reports all OK. Should I run gvm-setup again?
$ sudo gvm-check-setup
gvm-check-setup 23.11.0
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 prope
rly using the redis-server socket: /var/run/redis-openvas/re
dis-server.sock
OK: the mqtt_server_uri is defined in /etc/openvas/o
penvas.conf
OK: _gvm owns all files in /var/lib/openvas/plugins
OK: NVT collection in /var/lib/openvas/plugins conta
ins 93242 NVTs.
OK: The notus directory /var/lib/notus/products cont
ains 472 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.6.2.
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 valid
ation.
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.
gvmd | _gvm | UTF8 | libc | en_US.U
TF-8 | en_US.UTF-8 | | |
83303|pg-gvm|10|2200|f|22.6||
OK: At least one user exists.
Step 6: Checking Greenbone Security Assistant (GSA) …
OK: Greenbone Security Assistant is present in versi
on 22.11.0~git.
Step 7: Checking if GVM services are up and running …
OK: gvmd service is active.
OK: gsad service is active.
Step 8: Checking few other requirements…
OK: nmap is present.
OK: ssh-keygen found, LSC credential generation for
GNU/Linux targets is likely to work.
OK: nsis found, LSC credential package generation fo
r Microsoft Windows targets is likely to work.
OK: xsltproc found.
WARNING: Your password policy is empty.
SUGGEST: Edit the /etc/gvm/pwpolicy.conf file to set
a password policy.
Step 9: Checking greenbone-security-assistant…
OK: greenbone-security-assistant is installed
It seems like your GVM-23.11.0 installation is OK.
Thanks for letting me know. I ran another Kali system update, which gave me PostgreSQL 17. Upgraded the cluster as noted and all running again now. Doing some scans again now.