I’m having this identical problem, with a Kali VM install, I’ve installed three times now and can’t get past this point. Please Help!
From the Greenbone Community docs, this is the expected output when the VT syncronization begins. Regarding the time required to complete the first sync - this may take a significant amount of time - especially if you are using a low resourced VM.
Hi Joseph, Thank you for the reply. I have waited for the feeds to update, and setup of the database. Eventually I see this in the gvmd.log file, and it seems to update and then repeats:
md manage: INFO:2025-10-10 05h03.37 utc:909407: OSP service has different VT status (version 202510090701) from database (version (null), 0 VTs). Starting update …
md main:MESSAGE:2025-10-10 05h05.50 utc:910221: Greenbone Vulnerability Manager version 26.2.1 (DB revision 262)
md main: INFO:2025-10-10 05h05.51 utc:910224: gvmd is ready to accept GMP connections
md manage: INFO:2025-10-10 05h05.51 utc:910249: OSP service has different VT status (version 202510090701) from database (version (null), 0 VTs). Starting update …
Any thoughts? The Feed Status looks exactly like the screenshot above. Thanks for your time.
I’m not immediately sure. I would expect to see some errors related to accessing the socket, database permission error, or memory issue like OOM killer. Something like that. What’s the output of gvm-check-setup?
Can you post information about the resource allocated to your VM including RAM and drive space.
Just a moderator note: This thread has been split from the original, since it does not apply to community containers.
Hi Joseph, I was testing another install using the Docker containers and noticed some suggested hardware specs. I changed my Virtualbox settings to match those (4CPU cores and 8GB memory) and this has fixed the problem! I never saw a resource error in the gvmd.log file so didn’t suspect that but glad it’s working now. Thanks again for your help.
1 Like