@frank123 How did you installed it. sounds like installed incorrectly? If compiling by source, then follow the instructions or install kali packages.
Eero
Unfortunately I am facing the same problem right now. I have a Kali system running as VM on Proxmox and installed OpenVAS (as described in this guide), waited for the feed status to switch to Current for all of the available feeds.
Afterwards I wanted to start my first scan an received the same message. The gvm-check-setup script gives me for everything an OK, also I don’t see anything problematic in the log files.
With this limited background information, it’s impossible to guess the cause at all; the installation works well on Kali Linux — I’ve done it dozens of times over the past week. It’s worth checking that the machine has enough memory (at least 8GB), sufficient disk space (minimum 60GB), and enough processing power.
Eero
@Eero thanks for the information about the resources. I gave my Kali machine only about 6GB RAM, 6 cores and 80GB disk space. What I ended up doing is running this container which worked fine for the tests I needed to conduct. The machine the container is running on has 10GB RAM, 4 cores and 100GB disk space. Maybe you are right and the bottleneck is the RAM - I would have to check on that.
@DrStrangelove Not sure, but think that less than 8G is not enough for feedsync. Your issue looks like feedsync is not completed. (crash or incomplete due to ram issues).
Anyway, for scanning 10G is still very low amount of memory nowadays.
Eero