Hey, I did a quick scan of the previous post (TLDR), but maybe this is a separate issue from the first one? eserves its own thread. can you identify the problem from:
I think this gives a fairly comprehensive output of which services are active.
Otherwise, does increasing the log level in the configuration files (
/etc/gvmd/*.conf) offer any extra debugging information?
Thanks. Ran it and gave me this
Test completeness and readiness of GVM-22.4.1
Step 1: Checking OpenVAS (Scanner)...
ERROR: OpenVAS Scanner too old or too new: 22.7.3
FIX: Please install OpenVAS Scanner >= 22.4.
ERROR: Your GVM-22.4.1 installation is not yet complete!
Please follow the instructions marked with FIX above and run this
└─$ sudo apt install openvas-scanner
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
openvas-scanner is already the newest version (22.7.3-0kali2).
Seems my installation is too new. How can that be?
could you take a look at error in the
/var/gvm/gvmd.log file? that file should give more hints about the real issue here. If I would bet it’s caused by an update of the postgres db.
gvm-check-setup script isn’t maintained by Greenbone and it is very likely that the Kali package maintainer missed to update it after the recent version bump.
Please raise an issue at https://bugs.kali.org to let them know.
You were right. DB issue
Any idea on how to fix that?
Please look up the Kali documentation (In
/usr/share/docs) how the database needs to be “upgraded” on Kali as AFAICT a special user is used and there are some notes on the correct call in the Kali docs.