Just finished building gvm source 20.08 on Centos8. The build process seems to have gone well, but I am seeing this in my gvmd.log over and over and over again.
Sadly, the log isn’t very helpful. I appreciate any help to isolate the issue here. (for example, is there a debugging option for gvmd…???)
Here is the repeating log segment. I am guessing this will impact the ability of scans to generate proper reports…
md manage: INFO:2020-08-27 15h22.03 utc:1685: Updating /opt/gvm/var/lib/gvm/scap-data/nvdcve-2.0-2002.xml
md manage: INFO:2020-08-27 15h22.08 utc:1685: Updating /opt/gvm/var/lib/gvm/scap-data/nvdcve-2.0-2003.xml
md manage: INFO:2020-08-27 15h22.09 utc:1685: Updating /opt/gvm/var/lib/gvm/scap-data/nvdcve-2.0-2004.xml
md manage: INFO:2020-08-27 15h22.12 utc:1685: Updating /opt/gvm/var/lib/gvm/scap-data/nvdcve-2.0-2005.xml
md manage:WARNING:2020-08-27 15h22.13 utc:1685: update_cve_xml: Failed to parse element
md manage:WARNING:2020-08-27 15h22.22 utc:2242: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2020-08-27 15h22.22 utc:2242: update_scap: Updating data from feed
md manage: INFO:2020-08-27 15h22.22 utc:2242: Updating CPEs
md manage: INFO:2020-08-27 15h23.25 utc:2242: Updating /opt/gvm/var/lib/gvm/scap-data/nvdcve-2.0-2002.xml
md manage: INFO:2020-08-27 15h23.29 utc:2242: Updating /opt/gvm/var/lib/gvm/scap-data/nvdcve-2.0-2003.xml
md manage: INFO:2020-08-27 15h23.31 utc:2242: Updating /opt/gvm/var/lib/gvm/scap-data/nvdcve-2.0-2004.xml
md manage: INFO:2020-08-27 15h23.34 utc:2242: Updating /opt/gvm/var/lib/gvm/scap-data/nvdcve-2.0-2005.xml
md manage:WARNING:2020-08-27 15h23.34 utc:2242: update_cve_xml: Failed to parse element
md manage:WARNING:2020-08-27 15h23.40 utc:2802: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2020-08-27 15h23.40 utc:2802: update_scap: Updating data from feed
md manage: INFO:2020-08-27 15h23.40 utc:2802: Updating CPEs