I was able to resolve this.
I focused on the error from redis:
redis.exceptions.ResponseError: Command # 1 (DEL internal/notus/advisories/1.3.6.1.4.1.25623.1.1.4.2012.0033.1) of pipeline caused error: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.
What was suggested on a stackexchange thread, was to change the stop-writes-on-bgsave-error to = no. This is normally set to yes though (on Kali, as well as the current version of redis-openvast.conf on github). Setting it to no did allow everything to sync, but I didn’t think it was the correct move (as it seems to indicate some data could be dropped from the db).
My assumption was that there was some difference between the redis-config of Kali vs what is distributed with Greenbone, and I was correct. This commit on Github was the fix. It explicitly disables save on redis:
https://github.com/greenbone/openvas-scanner/pull/1199/commits/130a07177804262b0f0e80c72f89eccd473be132
Adding the same value (save “”) to the /etc/redis/redis-openvas.conf resolved the issue.
Step by step, to make get Greenbone to work on Kali (as of 02/20/2023):
cd /tmp
wget https://www.greenbone.net/GBCommunitySigningKey.asc
echo "8AE4BE429B60A59B311C2E739823FAA60ED1E580:6:" > /tmp/ownertrust.txt
export GNUPGHOME=/tmp/openvas-gnupg
mkdir -p $GNUPGHOME
gpg --import /tmp/GBCommunitySigningKey.asc
gpg --import-ownertrust < /tmp/ownertrust.txt
export OPENVAS_GNUPG_HOME=/etc/openvas/gnupg
sudo mkdir -p $OPENVAS_GNUPG_HOME
sudo cp -r /tmp/openvas-gnupg/* $OPENVAS_GNUPG_HOME/
sudo chown -R _gvm:_gvm $OPENVAS_GNUPG_HOME
After that, edit /etc/redis/redis-openvas.conf and around line 221, add:
save ""
The area around this will look like:
#save 900 1
#save 300 10
#save 60 10000
save ""
After these changes, reboot the machine. Run gvm-start and everything will work/sync properly.
After I did this, the logs look good and scans work properly:
OSPD[820] 2023-02-20 23:49:22,087: DEBUG: (paho.mqtt.client) Sending PINGREQ
OSPD[820] 2023-02-20 23:49:22,089: DEBUG: (paho.mqtt.client) Received PINGRESP
OSPD[820] 2023-02-20 23:49:31,869: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018
OSPD[820] 2023-02-20 23:49:31,869: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018
OSPD[820] 2023-02-20 23:49:41,871: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018
OSPD[820] 2023-02-20 23:49:41,871: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018
OSPD[820] 2023-02-20 23:49:51,873: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018
OSPD[820] 2023-02-20 23:49:51,874: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018
OSPD[820] 2023-02-20 23:50:01,876: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018
OSPD[820] 2023-02-20 23:50:01,877: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018
OSPD[820] 2023-02-20 23:50:11,878: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018
OSPD[820] 2023-02-20 23:50:11,878: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018
OSPD[820] 2023-02-20 23:50:21,880: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018
OSPD[820] 2023-02-20 23:50:21,880: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018
OSPD[820] 2023-02-20 23:50:22,158: DEBUG: (paho.mqtt.client) Sending PINGREQ
OSPD[820] 2023-02-20 23:50:22,159: DEBUG: (paho.mqtt.client) Received PINGRESP
I have submitted a bug report with Kali:
https://bugs.kali.org/view.php?id=8186