Gvm-check-setup is OK, had download scap-data, but in SecInfo, still display The SCAP database is required

Archive Greenbone Community Edition
1

Hi Guys,

The problem makes me in trouble.

I had run gvm-feed-update to update data xml many times.

Then had run gvm-check-setup in Kali 2021, the result is OK.

gvm-check-setup
gvm-check-setup956×726 26.3 KB

But after gvm-start and visit GVM Web UI.
In SecInfo selection, always display The SCAP database is required (which can find in /var/lib/gvm/)

Please lent me a hand.

The environment infomation as fellow:

GVM versions

gsad: Greenbone Security Assistant 21.4.1~dev1
gvmd: Greenbone Vulnerability Manager 21.4.2

openvas-scanner:
OpenVAS 21.4.1
gvm-libs 21.4.1

postgresql
postgresql-13

Environment

Operating system: Kali 2021
Kernel: Linux kali 5.10.0-kali9-amd64 #1 SMP Debian 5.10.46-1kali1 (2021-06-25) x86_64 GNU/Linux
Installation method / source: gvm-setup

2

You need to differentiate between syncing the files and loading the files into the database. The gvm-check-setup script from Kali (not maintained by Greenbone at all) just checks for the first thing.

After the data files are synced the gvmd daemon needs to load the files and put their data into the postgres database. This can be seen in the gvmd.log file and just needs some time (up to several hours for the initial loading).

1 Like
3

I had wait the initial loading several days.

But tail the /var/log/gvm/gvmd.log , it always repeat display “No SCAP database found update_scap: No SCAP db present, rebuilding SCAP db from scratch …”

Is it normal?
So I still wait the initial loading or it means the initial loading failed?

gvmd.log as fellows:

md manage:   INFO:2021-07-26 01h31.33 UTC:159754: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2015.xml
md manage:   INFO:2021-07-26 01h32.04 UTC:159754: Updating OVAL data
md   main:MESSAGE:2021-07-26 01h32.32 utc:159926:    Greenbone Vulnerability Manager version 21.4.2 (DB revision 242)
md manage:MESSAGE:2021-07-26 01h32.33 utc:159927: No SCAP database found
md manage:WARNING:2021-07-26 01h32.39 UTC:159949: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage:   INFO:2021-07-26 01h32.41 UTC:159950: OSP service has different VT status (version 202107231028) from database (version 0, 0 VTs). Starting update ...
md manage:   INFO:2021-07-26 01h32.42 UTC:159949: update_scap: Updating data from feed
md manage:   INFO:2021-07-26 01h32.42 UTC:159949: Updating CPEs
md manage:   INFO:2021-07-26 01h34.30 UTC:159949: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2007.xml



md manage:   INFO:2021-07-26 01h31.33 UTC:159754: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2015.xml
md manage:   INFO:2021-07-26 01h32.04 UTC:159754: Updating OVAL data
md   main:MESSAGE:2021-07-26 01h32.32 utc:159926:    Greenbone Vulnerability Manager version 21.4.2 (DB revision 242)
md manage:MESSAGE:2021-07-26 01h32.33 utc:159927: No SCAP database found
md manage:WARNING:2021-07-26 01h32.39 UTC:159949: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage:   INFO:2021-07-26 01h32.41 UTC:159950: OSP service has different VT status (version 202107231028) from database (version 0, 0 VTs). Starting update ...
md manage:   INFO:2021-07-26 01h32.42 UTC:159949: update_scap: Updating data from feed
md manage:   INFO:2021-07-26 01h32.42 UTC:159949: Updating CPEs
md manage:   INFO:2021-07-26 01h34.30 UTC:159949: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2007.xml


md manage:WARNING:2021-07-26 01h42.03 UTC:160242: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage:   INFO:2021-07-26 01h42.05 UTC:160243: OSP service has different VT status (version 202107231028) from database (version 0, 0 VTs). Starting update ...
md manage:   INFO:2021-07-26 01h42.05 UTC:160242: update_scap: Updating data from feed
md manage:   INFO:2021-07-26 01h42.05 UTC:160242: Updating CPEs
md manage:   INFO:2021-07-26 01h43.50 UTC:160242: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2007.xml
md manage:   INFO:2021-07-26 01h44.13 UTC:160242: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2021.xml
md manage:   INFO:2021-07-26 01h44.24 UTC:160242: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2012.xml
md manage:   INFO:2021-07-26 01h44.32 UTC:160242: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2011.xml
md manage:   INFO:2021-07-26 01h44.43 UTC:160242: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2009.xml
4

From that log file it seems that the loading of the scap files was interrupted several times. Only if all times have been loaded initially the scap database is build. Otherwise the loading process is restarted from the beginning.

1 Like
5

I’m having the same problem. I’ve installed OpenVAS today and the update seems like looping. How to solve it?

6

Not sure why this happens. Maybe the partition has not sufficient free disk space or systemd is restarting gvmd?

1 Like
7

Any update on this issue? I’m also experiencing a loop when trying to sync the feeds.
The worked around the two times that I have this loop is stopping and restarting GVM and even, shutdown the Kali Linux VM machine force a task to scan a test VM PC and let the sync happen again.

I have not found any official documentation on how to address this loop issue. But, I experiencing at the beginning of the installation and I expended two days and the last time more than 16 hours.

Any official or more straight forward solution would be highly appreciated.

Thanks