No SCAP database found, please help me

gpgp01 · August 20, 2023, 1:05pm

Hello,
thanks in advance for your help.

I have kali linux 2023.3
Greenbone Vulnerability Manager version 22.5.5 (DB revision 255)

but i have this problem , messagg in loop in /var/log/gvm/gvmd.log:

Greenbone Vulnerability Manager version 22.5.5 (DB revision 255)*
md manage:MESSAGE:2023-08-20 12h54.29 utc:1397: No SCAP database found*
md manage:WARNING:2023-08-20 12h54.32 UTC:1444: update_scap: No SCAP db present, rebuilding SCAP db from scratch*
md manage: INFO:2023-08-20 12h54.32 UTC:1445: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting*
md manage: INFO:2023-08-20 12h54.32 UTC:1444: update_scap: Updating data from feed*
md manage: INFO:2023-08-20 12h54.32 UTC:1444: Updating CPEs*

THIS IS MY CHECK OK

gvm-check-setup

gvm-check-setup 22.5.0*
Test completeness and readiness of GVM-22.5.0*
Step 1: Checking OpenVAS (Scanner)…*
OK: OpenVAS Scanner is present in version 22.7.3.*
OK: Notus Scanner is present in version 22.5.0.*
OK: Server CA Certificate is present as /var/lib/gvm/CA/servercert.pem.*
Checking permissions of /var/lib/openvas/gnupg/**
OK: _gvm owns all files in /var/lib/openvas/gnupg*
OK: redis-server is present.*
OK: scanner (db_address setting) is configured properly using the redis-server socket: /var/run/redis-openvas/redis-server.sock*
OK: the mqtt_server_uri is defined in /etc/openvas/openvas.conf*
OK: _gvm owns all files in /var/lib/openvas/plugins*
OK: NVT collection in /var/lib/openvas/plugins contains 86318 NVTs.*
OK: The notus directory /var/lib/notus/products contains 440 NVTs.*
Checking that the obsolete redis database has been removed*
OK: No old Redis DB*
OK: ospd-openvas service is active.*
OK: ospd-OpenVAS is present in version 22.5.3.*
Step 2: Checking GVMD Manager …*
OK: GVM Manager (gvmd) is present in version 22.5.5.*
Step 3: Checking Certificates …*
OK: GVM client certificate is valid and present as /var/lib/gvm/CA/clientcert.pem.*
OK: Your GVM certificate infrastructure passed validation.*
Step 4: Checking data …*
OK: SCAP data found in /var/lib/gvm/scap-data.*
OK: CERT data found in /var/lib/gvm/cert-data.*
Step 5: Checking Postgresql DB and user …*
OK: Postgresql version and default port are OK.*
gvmd | _gvm | UTF8 | en_US.UTF-8 | en_US.UTF-8 | | libc |*
16435|pg-gvm|10|2200|f|22.5||*
OK: At least one user exists.*
Step 6: Checking Greenbone Security Assistant (GSA) …*
OK: Greenbone Security Assistant is present in version 22.05.1~git.*
Step 7: Checking if GVM services are up and running …*
OK: gvmd service is active.*
OK: gsad service is active.*
Step 8: Checking few other requirements…*
OK: nmap is present.*
OK: ssh-keygen found, LSC credential generation for GNU/Linux targets is likely to work.*
OK: nsis found, LSC credential package generation for Microsoft Windows targets is likely to work.*
OK: xsltproc found.*
WARNING: Your password policy is empty.*
SUGGEST: Edit the /etc/gvm/pwpolicy.conf file to set a password policy.*
Step 9: Checking greenbone-security-assistant…*
OK: greenbone-security-assistant is installed*
It seems like your GVM-22.5.0 installation is OK*.

gpgp01 · August 21, 2023, 2:40pm

Hello,
please help me,
No SCAP database found, please help me

I would like to avoid reinstalling everything and losing all the scans already done.

thanks

rippledj · August 21, 2023, 4:25pm

Hi gpgp01 it looks like you have started the feed-sync, but the data has not been parsed into the
database yet. It generally takes some time for the feeds to be parsed into the database to become available.

gpgp01 · August 22, 2023, 2:26pm

Hello rippledj,
thanks for you replay, but four days have passed and the problem is still present, this error is random in the file /var/log/gvm/gvmd.log

md main:MESSAGE:2023-08-22 14h22.16 utc:1315190: Greenbone Vulnerability Manager version 22.5.5 (DB revision 255)
md manage:MESSAGE:2023-08-22 14h22.16 utc:1315191: No SCAP database found
md manage:MESSAGE:2023-08-22 14h22.19 utc:1315191: manage_schedule: Task timed out: 5c671527-bd00-475e-afbc-6c0e84592ae4
md manage:MESSAGE:2023-08-22 14h22.19 utc:1315191: manage_schedule: Task timed out: 8b970b81-50e7-4ac9-9c56-53011e29b63e
md manage:MESSAGE:2023-08-22 14h22.19 utc:1315191: manage_schedule: Task timed out: 823ef809-62ea-4af6-9984-6d17204d862f
md manage:MESSAGE:2023-08-22 14h22.19 utc:1315191: manage_schedule: Task timed out: 3f1f3bbc-3826-4251-9fe8-bfe965ab7455
md manage:MESSAGE:2023-08-22 14h22.19 utc:1315191: manage_schedule: Task timed out: 6d17785e-9d36-453c-ad0b-c9282cdcf582
md manage:MESSAGE:2023-08-22 14h22.19 utc:1315191: manage_schedule: Task timed out: 5a80305f-58ae-4dff-80b4-a43764933efc
md manage:MESSAGE:2023-08-22 14h22.19 utc:1315191: manage_schedule: Task timed out: c44d6394-5de0-4305-ace2-7296a415f1fa
md manage:WARNING:2023-08-22 14h22.19 UTC:1315268: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2023-08-22 14h22.19 UTC:1315267: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage: INFO:2023-08-22 14h22.20 UTC:1315268: update_scap: Updating data from feed
md manage: INFO:2023-08-22 14h22.20 UTC:1315268: Updating CPEs

rippledj · August 22, 2023, 4:26pm

What is the output if you run the command:

sudo greenbone-feed-sync --type scap

gpgp01 · August 23, 2023, 6:28am

Hello,
this output with Greenbone stop:

greenbone-feed-sync --type scap

Running as root. Switching to user ‘_gvm’ and group ‘_gvm’.
Trying to acquire lock on /var/lib/gvm/feed-update.lock
Acquired lock on /var/lib/gvm/feed-update.lock
⠹ Downloading SCAP data from rsync://feed.community.greenbone.net/community/vulnerability-feed/22.04/scap-data/ to
/var/lib/gvm/scap-data
Releasing lock on /var/lib/gvm/feed-update.lock

This output with Greenbone start:

greenbone-feed-sync --type scap

Running as root. Switching to user ‘_gvm’ and group ‘_gvm’.
Trying to acquire lock on /var/lib/gvm/feed-update.lock
/var/lib/gvm/feed-update.lock is locked by another process. Waiting 5 seconds before next try.

thanks

rippledj · August 23, 2023, 4:31pm

It looks like the command was successful. Perhaps the database has been rebuilt as suggested by the logs. If you log into Greenbone, can you view data that pertains to SCAP such as the CVE and CPE pages?

Go to the menu: SecInfo -> CVEs and SecInfo -> CPEs. Do you see items on those pages?

gpgp01 · August 23, 2023, 6:23pm

Hello,
no good notice:

into Greenbone i see The SCAP database is required
see attached file
help me

thanks

rippledj · August 23, 2023, 7:32pm

I guess this is likely an issue with the Postgres database. Maybe you have more than one version installed or some other issue. Personally, I would suggest starting with a fresh installation of Kali since it would be difficult for me to troubleshoot this issue via the forum. However, maybe someone else can suggest something else to try.

HangGlider · August 24, 2023, 7:42pm

FWIW I have the exact same issue.

Identical log entries as OP, and identical results for the commands you suggested.

gpgp01 · August 25, 2023, 5:46am

Thanks for the reply,
in fact you can not understand the problem.

please is there anyone who can help us?

DeeAnn · August 25, 2023, 9:28am

Hi @gpgp01 and welcome to the forum @HangGlider

It’s interesting you are both seeing the same thing and I also suspect an underlying database issue. @HangGlider is this a new install or an existing install?

HangGlider · August 25, 2023, 1:52pm

Actually, on two new installs - on two different VMs. One using the latest OVA, and one using the latest ISO.

gpgp01 · August 27, 2023, 4:45am

Hello DeeAnn, thanks for you replay.
mine is an existing install that has received some system update.

please is there anyone who can help me?

bricks · August 27, 2023, 12:20pm

If you get the message “The SCAP database is required” the scap data from the feed hasn’t been loaded yet. Especially if “Feed Status” page shows “Update in progress”. You need to be patient until the gvmd log says “update_scap_end: Updating SCAP info succeeded”. Please take a look at Building 22.4 from Source - Greenbone Community Documentation for some more details and background about the feed synchronization.

gpgp01 · August 31, 2023, 2:30pm

Hello bricks,
thanks for your replay, but the problem is not solved.
I have start this command:
greenbone-feed-sync
systemctl start notus-scanner
systemctl start ospd-openvas
systemctl start gvmd
systemctl start gsad

I Recived alway this log in /var/log/gvm/gvmd.log:

tail -f gvmd.log

md manage:WARNING:2023-08-25 05h41.55 UTC:1182229: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage:   INFO:2023-08-25 05h41.56 UTC:1182229: update_scap: Updating data from feed
md manage:   INFO:2023-08-25 05h41.56 UTC:1182229: Updating CPEs
md manage:   INFO:2023-08-25 05h46.05 UTC:1182229: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2005.xml
md manage:   INFO:2023-08-25 05h46.15 UTC:1182229: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2006.xml
md manage:   INFO:2023-08-25 05h46.32 UTC:1182229: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2008.xml
md manage:   INFO:2023-08-25 05h46.47 UTC:1182229: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2010.xml
md manage:   INFO:2023-08-25 05h46.57 UTC:1182229: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2002.xml
md manage:   INFO:2023-08-25 05h47.06 UTC:1182229: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2003.xml
md manage:   INFO:2023-08-25 05h47.08 UTC:1182229: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2020.xml
md   main:MESSAGE:2023-08-31 14h11.41 utc:6249:    Greenbone Vulnerability Manager version 22.5.5 (DB revision 255)
md manage:MESSAGE:2023-08-31 14h11.41 utc:6250: No SCAP database found
md manage:MESSAGE:2023-08-31 14h12.02 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.100509:6 has changed from 'Report vulnerabilities of inactive Linux Kernel(s) separately' to 'Report vulnerabilities of inactive Linux Kernel(s) separately (only for GOS 21.04 and older)'.
md manage:MESSAGE:2023-08-31 14h12.02 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
md manage:MESSAGE:2023-08-31 14h12.03 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.111091:1 has changed from 'Report NVT debug logs' to 'Report VT debug logs'.
md manage:MESSAGE:2023-08-31 14h12.05 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.100509:6 has changed from 'Report vulnerabilities of inactive Linux Kernel(s) separately' to 'Report vulnerabilities of inactive Linux Kernel(s) separately (only for GOS 21.04 and older)'.
md manage:MESSAGE:2023-08-31 14h12.05 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
md manage:MESSAGE:2023-08-31 14h12.06 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.111091:1 has changed from 'Report NVT debug logs' to 'Report VT debug logs'.
md manage:MESSAGE:2023-08-31 14h12.07 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
md manage:MESSAGE:2023-08-31 14h12.07 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
md manage:MESSAGE:2023-08-31 14h12.09 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.100509:6 has changed from 'Report vulnerabilities of inactive Linux Kernel(s) separately' to 'Report vulnerabilities of inactive Linux Kernel(s) separately (only for GOS 21.04 and older)'.
md manage:MESSAGE:2023-08-31 14h12.09 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
md manage:MESSAGE:2023-08-31 14h12.09 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.111091:1 has changed from 'Report NVT debug logs' to 'Report VT debug logs'.
md manage:MESSAGE:2023-08-31 14h12.12 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.100509:6 has changed from 'Report vulnerabilities of inactive Linux Kernel(s) separately' to 'Report vulnerabilities of inactive Linux Kernel(s) separately (only for GOS 21.04 and older)'.
md manage:MESSAGE:2023-08-31 14h12.12 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
md manage:MESSAGE:2023-08-31 14h12.13 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.111091:1 has changed from 'Report NVT debug logs' to 'Report VT debug logs'.
md manage:MESSAGE:2023-08-31 14h12.15 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.100509:6 has changed from 'Report vulnerabilities of inactive Linux Kernel(s) separately' to 'Report vulnerabilities of inactive Linux Kernel(s) separately (only for GOS 21.04 and older)'.
md manage:MESSAGE:2023-08-31 14h12.15 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
md manage:MESSAGE:2023-08-31 14h12.16 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.111091:1 has changed from 'Report NVT debug logs' to 'Report VT debug logs'.
md manage:MESSAGE:2023-08-31 14h12.17 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.10870:1 has changed from 'NTLMSSP' to 'This configuration (NTLMSSP) is deprecated as of 2022-09-23.'.
md manage:MESSAGE:2023-08-31 14h12.19 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.111091:1 has changed from 'Report NVT debug logs' to 'Report VT debug logs'.
md manage:MESSAGE:2023-08-31 14h12.19 utc:6250: get_nvt_preference_by_id: name of preference 1.3.6.1.4.1.25623.1.0.100509:6 has changed from 'Report vulnerabilities of inactive Linux Kernel(s) separately' to 'Report vulnerabilities of inactive Linux Kernel(s) separately (only for GOS 21.04 and older)'.
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: 5c671527-bd00-475e-afbc-6c0e84592ae4
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: 8b970b81-50e7-4ac9-9c56-53011e29b63e
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: 823ef809-62ea-4af6-9984-6d17204d862f
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: 6b2d3e47-a023-4de7-9b23-1aaa9d68fecf
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: 31561f2d-fa4b-4e20-8bcc-903819035335
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: 3f1f3bbc-3826-4251-9fe8-bfe965ab7455
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: 6d17785e-9d36-453c-ad0b-c9282cdcf582
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: aac17a95-f397-4c27-bb85-622845986b98
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: f75dcf59-5466-4d53-9d37-9f5798bef6a6
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: 5a80305f-58ae-4dff-80b4-a43764933efc
md manage:MESSAGE:2023-08-31 14h12.20 utc:6250:  manage_schedule: Task timed out: c44d6394-5de0-4305-ace2-7296a415f1fa
md manage:   INFO:2023-08-31 14h12.20 UTC:6869: sync_cert: Updating data from feed
md manage:WARNING:2023-08-31 14h12.20 UTC:6868: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage:   INFO:2023-08-31 14h12.20 UTC:6871: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
md manage:   INFO:2023-08-31 14h12.20 UTC:6869: update_dfn_xml: dfn-cert-2016.xml
md manage:   INFO:2023-08-31 14h12.20 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2016.xml
md manage:   INFO:2023-08-31 14h12.20 UTC:6869: update_dfn_xml: dfn-cert-2012.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2012.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: update_dfn_xml: dfn-cert-2009.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2009.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: update_dfn_xml: dfn-cert-2017.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2017.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: update_dfn_xml: dfn-cert-2020.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2020.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: update_dfn_xml: dfn-cert-2013.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2013.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: update_dfn_xml: dfn-cert-2022.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2022.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: update_dfn_xml: dfn-cert-2014.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2014.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: update_dfn_xml: dfn-cert-2010.xml
md manage:   INFO:2023-08-31 14h12.21 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2010.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: update_dfn_xml: dfn-cert-2021.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2021.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: update_dfn_xml: dfn-cert-2008.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2008.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: update_dfn_xml: dfn-cert-2023.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2023.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6868: update_scap: Updating data from feed
md manage:   INFO:2023-08-31 14h12.22 UTC:6868: Updating CPEs
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: update_dfn_xml: dfn-cert-2011.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2011.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: update_dfn_xml: dfn-cert-2018.xml
md manage:   INFO:2023-08-31 14h12.22 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2018.xml
md manage:   INFO:2023-08-31 14h12.23 UTC:6869: update_dfn_xml: dfn-cert-2019.xml
md manage:   INFO:2023-08-31 14h12.23 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2019.xml
md manage:   INFO:2023-08-31 14h12.23 UTC:6869: update_dfn_xml: dfn-cert-2015.xml
md manage:   INFO:2023-08-31 14h12.23 UTC:6869: Updating /var/lib/gvm/cert-data/dfn-cert-2015.xml
md manage:   INFO:2023-08-31 14h12.23 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K14.xml
md manage:   INFO:2023-08-31 14h12.23 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K20.xml
md manage:   INFO:2023-08-31 14h12.24 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K15.xml
md manage:   INFO:2023-08-31 14h12.24 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K13.xml
md manage:   INFO:2023-08-31 14h12.24 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K21.xml
md manage:   INFO:2023-08-31 14h12.24 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K17.xml
md manage:   INFO:2023-08-31 14h12.25 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K16.xml
md manage:   INFO:2023-08-31 14h12.25 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K22.xml
md manage:   INFO:2023-08-31 14h12.25 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K23.xml
md manage:   INFO:2023-08-31 14h12.26 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K19.xml
md manage:   INFO:2023-08-31 14h12.26 UTC:6869: Updating /var/lib/gvm/cert-data/CB-K18.xml
md manage:   INFO:2023-08-31 14h12.26 UTC:6869: SCAP database does not exist (yet), skipping CERT severity score update
md manage:   INFO:2023-08-31 14h12.26 UTC:6869: sync_cert: Updating CERT info succeeded.
md manage:   INFO:2023-08-31 14h17.30 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2005.xml
md manage:   INFO:2023-08-31 14h17.36 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2006.xml
md manage:   INFO:2023-08-31 14h17.45 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2008.xml
md manage:   INFO:2023-08-31 14h17.59 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2010.xml
md manage:   INFO:2023-08-31 14h18.09 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2002.xml
md manage:   INFO:2023-08-31 14h18.17 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2003.xml
md manage:   INFO:2023-08-31 14h18.19 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2020.xml
md manage:   INFO:2023-08-31 14h18.50 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2023.xml
md manage:   INFO:2023-08-31 14h19.10 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2016.xml
md manage:   INFO:2023-08-31 14h19.24 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2015.xml
md manage:   INFO:2023-08-31 14h19.33 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2009.xml
md manage:   INFO:2023-08-31 14h19.44 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2004.xml
md manage:   INFO:2023-08-31 14h19.48 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2018.xml
md manage:   INFO:2023-08-31 14h20.27 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2014.xml
md manage:   INFO:2023-08-31 14h20.37 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2013.xml
md manage:   INFO:2023-08-31 14h20.47 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2017.xml
md manage:   INFO:2023-08-31 14h21.06 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2007.xml
md manage:   INFO:2023-08-31 14h21.14 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2011.xml
md manage:   INFO:2023-08-31 14h21.23 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2019.xml
md manage:   INFO:2023-08-31 14h22.00 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2012.xml
md manage:   INFO:2023-08-31 14h22.08 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2021.xml
md manage:   INFO:2023-08-31 14h22.43 UTC:6868: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2022.xml
md manage:   INFO:2023-08-31 14h23.21 UTC:6868: Updating CVSS scores and CVE counts for CPEs
md manage:   INFO:2023-08-31 14h25.22 UTC:6868: Updating placeholder CPEs
md manage:WARNING:2023-08-31 14h25.35 UTC:6868: sql_exec_internal: PQexec failed: ERROR:  schema "scap" already exists
 (7)
md manage:WARNING:2023-08-31 14h25.35 UTC:6868: sql_exec_internal: SQL: ALTER SCHEMA scap2 RENAME TO scap;
md manage:WARNING:2023-08-31 14h25.35 UTC:6868: sqlv: sql_exec_internal failed
md manage:WARNING:2023-08-31 14h25.35 UTC:19800: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage:   INFO:2023-08-31 14h25.35 UTC:19799: OSP service has different VT status (version 202308310606) from database (version 202308230557, 130902 VTs). Starting update ...
md manage:   INFO:2023-08-31 14h25.36 UTC:19800: update_scap: Updating data from feed
md manage:   INFO:2023-08-31 14h25.36 UTC:19800: Updating CPEs
md manage:   INFO:2023-08-31 14h27.14 utc:19799: Updating VTs in database ... 123 new VTs, 184 changed VTs
md manage:   INFO:2023-08-31 14h27.15 utc:19799: Updating VTs in database ... done (131066 VTs).
md manage:   INFO:2023-08-31 14h28.38 UTC:19800: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2005.xml
md manage:   INFO:2023-08-31 14h28.45 UTC:19800: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2006.xml
md manage:   INFO:2023-08-31 14h28.54 UTC:19800: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2008.xml
md manage:   INFO:2023-08-31 14h29.04 UTC:19800: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2010.xml

Please help me.
thanks

gpgp01 · August 31, 2023, 7:50pm

HELLO to all,
i have solved the problema:

su - postgres
psql gvmd
gvmd=# \dn

List of schemas
  Name  |       Owner
--------+-------------------
 cert   | _gvm
 public | pg_database_owner
 scap   | postgres
 scap2  | _gvm
(4 rows)

Owner scap schemas is postgres instead of _gvm

ALTER SCHEMA scap OWNER TO _gvm;

gvmd=# \dn
      List of schemas
  Name  |       Owner
--------+-------------------
 cert   | _gvm
 public | pg_database_owner
 scap   | _gvm
 scap2  | _gvm
(4 rows)

thanks

peppertea · September 1, 2023, 3:06am

I literally had the same issue and tried the exact same thing you all did

I am not understanding how you changed the postgres changed was fixed. Can you please let me know step-by-step on how you did this?

bricks · September 1, 2023, 5:52am

No SCAP database found, please help me - #18 by gpgp01 contains all the necessary steps.

su - postgres
psql -c "ALTER SCHEMA scap OWNER TO _gvm;" gvmd

gpgp01 · September 1, 2023, 7:31am

hello peppertea

please connect to the gvmd DB
#su - postgres
#psql gvmd

\dn

and post the result of this last command.

thanks