Can't create a scan config (failed to find config)

Hi, you need to check the log file of gvmd (named gvmd.log normally somewhere in /var/log). It is very likely that is contains an error message stating some database issues.

1 Like

Hi, this below is my content in log file

md main:MESSAGE:2021-03-11 06h22.44 utc:4663: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md main: INFO:2021-03-11 06h22.44 utc:4663: Migrating database.
md main:WARNING:2021-03-11 06h22.44 utc:4663: manage_migrate: no task tables yet, so no need to migrate them
md main:MESSAGE:2021-03-11 06h22.44 utc:4663: No SCAP database found for migration
md main:MESSAGE:2021-03-11 06h22.44 utc:4663: No CERT database found for migration
md main:WARNING:2021-03-11 06h22.44 utc:4663: gvmd: databases are already at the supported version
md main:MESSAGE:2021-03-11 06h22.44 utc:4669: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-11 06h22.44 utc:4669: Getting users.
md manage:WARNING:2021-03-11 06h22.45 utc:4669: sql_exec_internal: PQexec failed: ERROR: relation ā€œpublic.metaā€ does not exist
LINE 1: SELECT value FROM public.meta WHERE name = 'database_versionā€¦
^
(7)
md manage:WARNING:2021-03-11 06h22.45 utc:4669: sql_exec_internal: SQL: SELECT value FROM public.meta WHERE name = ā€˜database_versionā€™;
md manage:WARNING:2021-03-11 06h22.45 utc:4669: sql_x: sql_exec_internal failed
md manage:MESSAGE:2021-03-11 06h22.45 utc:4669: No SCAP database found
md manage:MESSAGE:2021-03-11 06h22.45 utc:4669: No CERT database found
md main:MESSAGE:2021-03-11 06h22.46 utc:4673: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-11 06h22.46 utc:4673: Creating user.
md manage:MESSAGE:2021-03-11 06h22.46 utc:4673: No SCAP database found
md manage:MESSAGE:2021-03-11 06h22.46 utc:4673: No CERT database found
md main:MESSAGE:2021-03-11 06h22.47 utc:4692: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-11 06h22.47 utc:4692: Getting users.
md manage:MESSAGE:2021-03-11 06h22.47 utc:4692: No SCAP database found
md manage:MESSAGE:2021-03-11 06h22.47 utc:4692: No CERT database found
md main:MESSAGE:2021-03-11 06h22.48 utc:4696: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-11 06h22.48 utc:4696: Modifying setting.
md manage:MESSAGE:2021-03-11 06h22.48 utc:4696: No SCAP database found
md manage:MESSAGE:2021-03-11 06h22.48 utc:4696: No CERT database found
md main:MESSAGE:2021-03-11 07h25.30 utc:5292: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-11 07h25.30 utc:5292: Getting scanners.
md manage:MESSAGE:2021-03-11 07h25.32 utc:5292: No SCAP database found
md manage:MESSAGE:2021-03-11 07h25.32 utc:5292: No CERT database found
event port_list:MESSAGE:2021-03-11 07h25.33 utc:5292: Port list All IANA assigned TCP and UDP (4a4717fe-57d2-11e1-9a26-406186ea4fc5) has been created by admin
event port_list:MESSAGE:2021-03-11 07h25.33 utc:5292: Port list All TCP and Nmap top 100 UDP (730ef368-57e2-11e1-a90f-406186ea4fc5) has been created by admin
event port_list:MESSAGE:2021-03-11 07h25.34 utc:5292: Port list All IANA assigned TCP (33d0cd82-57c6-11e1-8ed1-406186ea4fc5) has been created by admin
event report_format:MESSAGE:2021-03-11 07h25.34 utc:5292: Report format CSV Results (c1645568-627a-11e3-a660-406186ea4fc5) has been created by admin
event report_format:MESSAGE:2021-03-11 07h25.34 utc:5292: Report format Anonymous XML (5057e5cc-b825-11e4-9d0e-28d24461215b) has been created by admin
event report_format:MESSAGE:2021-03-11 07h25.34 utc:5292: Report format PDF (c402cc3e-b531-11e1-9163-406186ea4fc5) has been created by admin
event report_format:MESSAGE:2021-03-11 07h25.34 utc:5292: Report format XML (a994b278-1f62-11e1-96ac-406186ea4fc5) has been created by admin
event report_format:MESSAGE:2021-03-11 07h25.34 utc:5292: Report format TXT (a3810a62-1f62-11e1-9219-406186ea4fc5) has been created by admin
event report_format:MESSAGE:2021-03-11 07h25.35 utc:5292: Report format ITG (77bd6c4a-1f62-11e1-abf0-406186ea4fc5) has been created by admin
md main:MESSAGE:2021-03-11 07h26.58 utc:5333: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage:MESSAGE:2021-03-11 07h26.59 utc:5334: No SCAP database found
md manage:MESSAGE:2021-03-11 07h26.59 utc:5334: No CERT database found
util gpgme: INFO:2021-03-11 07h26.59 utc:5334: starting key generation ā€¦
util gpgme: INFO:2021-03-11 07h27.00 utc:5334: OpenPGP key ā€˜GVM Credential Encryptionā€™ has been generated
md manage:WARNING:2021-03-11 07h28.41 utc:5469: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2021-03-11 07h28.41 utc:5473: OSP service has different VT status (version 202103101106) from database (version (null), 0 VTs). Starting update ā€¦
md manage: INFO:2021-03-11 07h28.41 utc:5470: Initializing CERT database
md manage: INFO:2021-03-11 07h28.41 utc:5469: update_scap: Updating data from feed
md manage: INFO:2021-03-11 07h28.41 utc:5469: Updating CPEs
md manage: INFO:2021-03-11 07h28.41 utc:5470: sync_cert: Updating data from feed
md manage: INFO:2021-03-11 07h28.41 utc:5470: update_dfn_xml: dfn-cert-2015.xml
md manage: INFO:2021-03-11 07h28.41 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2015.xml
md manage: INFO:2021-03-11 07h29.24 utc:5470: update_dfn_xml: dfn-cert-2010.xml
md manage: INFO:2021-03-11 07h29.24 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2010.xml
md manage: INFO:2021-03-11 07h29.46 utc:5470: update_dfn_xml: dfn-cert-2018.xml
md manage: INFO:2021-03-11 07h29.46 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2018.xml
event target:MESSAGE:2021-03-11 07h29.51 UTC:5616: Target Target for immediate scan of IP 127.0.0.1 - 2021-03-11 07:29:51 (f12921e2-d82a-45fd-80f2-78257bf48020) has been created by admin
event task:MESSAGE:2021-03-11 07h29.51 UTC:5616: Status of task (00fb5c40-6f90-4c9d-bc2c-25a80ef5ca82) has changed to New
event wizard:MESSAGE:2021-03-11 07h29.52 UTC:5616: Wizard quick_first_scan could not be run by admin
md manage: INFO:2021-03-11 07h30.18 utc:5470: update_dfn_xml: dfn-cert-2016.xml
md manage: INFO:2021-03-11 07h30.18 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2016.xml
md manage: INFO:2021-03-11 07h30.42 utc:5470: update_dfn_xml: dfn-cert-2012.xml
md manage: INFO:2021-03-11 07h30.42 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2012.xml
md manage: INFO:2021-03-11 07h31.04 utc:5470: update_dfn_xml: dfn-cert-2019.xml
md manage: INFO:2021-03-11 07h31.04 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2019.xml
md manage: INFO:2021-03-11 07h31.48 utc:5470: update_dfn_xml: dfn-cert-2009.xml
md manage: INFO:2021-03-11 07h31.48 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2009.xml
md manage: INFO:2021-03-11 07h31.57 utc:5470: update_dfn_xml: dfn-cert-2017.xml
md manage: INFO:2021-03-11 07h31.57 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2017.xml
md manage: INFO:2021-03-11 07h32.36 utc:5470: update_dfn_xml: dfn-cert-2021.xml
md manage: INFO:2021-03-11 07h32.36 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2021.xml
md manage: INFO:2021-03-11 07h32.43 utc:5470: update_dfn_xml: dfn-cert-2014.xml
md manage: INFO:2021-03-11 07h32.43 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2014.xml
md manage: INFO:2021-03-11 07h33.02 utc:5470: update_dfn_xml: dfn-cert-2013.xml
md manage: INFO:2021-03-11 07h33.02 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2013.xml
md manage: INFO:2021-03-11 07h33.37 utc:5470: update_dfn_xml: dfn-cert-2020.xml
md manage: INFO:2021-03-11 07h33.37 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2020.xml
md manage: INFO:2021-03-11 07h34.43 utc:5470: update_dfn_xml: dfn-cert-2008.xml
md manage: INFO:2021-03-11 07h34.43 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2008.xml
md manage: INFO:2021-03-11 07h34.44 utc:5470: update_dfn_xml: dfn-cert-2011.xml
md manage: INFO:2021-03-11 07h34.44 utc:5470: Updating /var/lib/gvm/cert-data/dfn-cert-2011.xml
md manage: INFO:2021-03-11 07h35.22 utc:5470: Updating /var/lib/gvm/cert-data/CB-K13.xml
md manage: INFO:2021-03-11 07h35.32 utc:5470: Updating /var/lib/gvm/cert-data/CB-K20.xml
md manage: INFO:2021-03-11 07h35.54 utc:5470: Updating /var/lib/gvm/cert-data/CB-K14.xml
md manage: INFO:2021-03-11 07h36.16 utc:5470: Updating /var/lib/gvm/cert-data/CB-K16.xml
md manage: INFO:2021-03-11 07h36.47 utc:5470: Updating /var/lib/gvm/cert-data/CB-K15.xml
md manage: INFO:2021-03-11 07h37.09 utc:5470: Updating /var/lib/gvm/cert-data/CB-K17.xml
md manage: INFO:2021-03-11 07h37.41 utc:5470: Updating /var/lib/gvm/cert-data/CB-K19.xml
md manage: INFO:2021-03-11 07h37.55 utc:5470: Updating /var/lib/gvm/cert-data/CB-K21.xml
md manage: INFO:2021-03-11 07h37.56 utc:5470: Updating /var/lib/gvm/cert-data/CB-K18.xml
md manage: INFO:2021-03-11 07h38.07 utc:5470: sync_cert: Updating CERT info succeeded.
event target:MESSAGE:2021-03-11 07h38.51 UTC:6116: Target Target for immediate scan of IP 127.0.0.1 - 2021-03-11 07:38:51 (10ac4ab7-b854-47ca-bcbb-3450848c3d70) has been created by admin
event task:MESSAGE:2021-03-11 07h38.51 UTC:6116: Status of task (a0b88cdd-d9af-4e9c-b8d2-e608f1547e6a) has changed to New
event wizard:MESSAGE:2021-03-11 07h38.51 UTC:6116: Wizard quick_first_scan could not be run by admin
md manage: INFO:2021-03-11 07h42.42 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2002.xml
md manage: INFO:2021-03-11 07h43.15 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2021.xml
md manage: INFO:2021-03-11 07h43.28 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2011.xml
md manage: INFO:2021-03-11 07h44.22 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2012.xml
md manage: INFO:2021-03-11 07h45.11 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2009.xml
md manage: INFO:2021-03-11 07h46.16 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2006.xml
md manage: INFO:2021-03-11 07h46.55 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2016.xml
md manage: INFO:2021-03-11 07h48.00 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2005.xml
md manage: INFO:2021-03-11 07h48.48 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2018.xml
md main:MESSAGE:2021-03-11 07h51.22 utc:8886: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-11 07h51.22 utc:8886: Getting scanners.
md manage:MESSAGE:2021-03-11 07h51.24 utc:8886: No SCAP database found
md manage: INFO:2021-03-11 07h54.42 utc:5469: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2015.xml
md main:MESSAGE:2021-03-11 10h29.13 utc:1399: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage:MESSAGE:2021-03-11 10h29.16 utc:1400: No SCAP database found
event target:MESSAGE:2021-03-11 10h31.34 UTC:1873: Target Target for immediate scan of IP 127.0.0.1 - 2021-03-11 10:31:34 (2d949710-31a8-472d-b178-51b23af78b6b) has been created by admin
event task:MESSAGE:2021-03-11 10h31.34 UTC:1873: Status of task (1d62da4c-d0a0-4869-a848-5536c21cda65) has changed to New
event wizard:MESSAGE:2021-03-11 10h31.34 UTC:1873: Wizard quick_first_scan could not be run by admin
md manage:WARNING:2021-03-11 10h34.18 utc:1942: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2021-03-11 10h34.18 utc:1946: OSP service has different VT status (version 202103101106) from database (version (null), 0 VTs). Starting update ā€¦
md manage: INFO:2021-03-11 10h34.19 utc:1942: update_scap: Updating data from feed
md manage: INFO:2021-03-11 10h34.19 utc:1942: Updating CPEs
md manage: INFO:2021-03-11 10h42.37 utc:1942: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2002.xml
md manage: INFO:2021-03-11 10h43.13 utc:1942: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2021.xml
md manage: INFO:2021-03-11 10h43.23 utc:1942: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2011.xml
md manage: INFO:2021-03-11 10h44.09 utc:1942: Updating /var/lib/gvm/scap-data/nvdcve-2.0-2012.xml
md main:MESSAGE:2021-03-12 03h32.16 utc:1535: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md main: INFO:2021-03-12 03h32.16 utc:1535: Migrating database.
md main:MESSAGE:2021-03-12 03h32.16 utc:1535: No SCAP database found for migration
md main:WARNING:2021-03-12 03h32.16 utc:1535: gvmd: databases are already at the supported version
md main:MESSAGE:2021-03-12 03h32.16 utc:1541: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-12 03h32.16 utc:1541: Getting users.
md manage:MESSAGE:2021-03-12 03h32.16 utc:1541: No SCAP database found
md main:MESSAGE:2021-03-12 03h43.21 utc:1772: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-12 03h43.21 utc:1772: Getting scanners.
md manage:MESSAGE:2021-03-12 03h43.21 utc:1772: No SCAP database found
md main:MESSAGE:2021-03-12 03h44.16 utc:1789: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage:MESSAGE:2021-03-12 03h44.16 utc:1790: No SCAP database found
md manage:WARNING:2021-03-12 03h45.29 utc:1870: update_scap: No SCAP db present, rebuilding SCAP db from scratch
md manage: INFO:2021-03-12 03h45.29 utc:1874: OSP service has different VT status (version 202103111126) from database (version (null), 0 VTs). Starting update ā€¦
md manage: INFO:2021-03-12 03h45.30 utc:1871: sync_cert: Updating data from feed
md manage: INFO:2021-03-12 03h45.32 utc:1870: update_scap: Updating data from feed
md manage: INFO:2021-03-12 03h45.32 utc:1870: Updating CPEs
md manage: INFO:2021-03-12 03h45.32 utc:1871: update_dfn_xml: dfn-cert-2015.xml
md manage: INFO:2021-03-12 03h45.32 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2015.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.32 utc:1871: update_dfn_xml: dfn-cert-2010.xml
md manage: INFO:2021-03-12 03h45.32 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2010.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.32 utc:1871: update_dfn_xml: dfn-cert-2018.xml
md manage: INFO:2021-03-12 03h45.32 utc:1871: Updating /var/lib/gvm/cert-data/dfn-cert-2018.xml
md manage: INFO:2021-03-12 03h45.34 utc:1871: update_dfn_xml: dfn-cert-2016.xml
md manage: INFO:2021-03-12 03h45.34 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2016.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.34 utc:1871: update_dfn_xml: dfn-cert-2012.xml
md manage: INFO:2021-03-12 03h45.34 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2012.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.34 utc:1871: update_dfn_xml: dfn-cert-2019.xml
md manage: INFO:2021-03-12 03h45.34 utc:1871: Updating /var/lib/gvm/cert-data/dfn-cert-2019.xml
md manage: INFO:2021-03-12 03h45.39 utc:1871: update_dfn_xml: dfn-cert-2009.xml
md manage: INFO:2021-03-12 03h45.39 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2009.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.39 utc:1871: update_dfn_xml: dfn-cert-2017.xml
md manage: INFO:2021-03-12 03h45.39 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2017.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.39 utc:1871: update_dfn_xml: dfn-cert-2021.xml
md manage: INFO:2021-03-12 03h45.39 utc:1871: Updating /var/lib/gvm/cert-data/dfn-cert-2021.xml
md manage: INFO:2021-03-12 03h45.43 utc:1871: update_dfn_xml: dfn-cert-2014.xml
md manage: INFO:2021-03-12 03h45.43 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2014.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.43 utc:1871: update_dfn_xml: dfn-cert-2013.xml
md manage: INFO:2021-03-12 03h45.43 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2013.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.43 utc:1871: update_dfn_xml: dfn-cert-2020.xml
md manage: INFO:2021-03-12 03h45.43 utc:1871: Updating /var/lib/gvm/cert-data/dfn-cert-2020.xml
md manage: INFO:2021-03-12 03h45.43 utc:1871: update_dfn_xml: dfn-cert-2008.xml
md manage: INFO:2021-03-12 03h45.43 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2008.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.43 utc:1871: update_dfn_xml: dfn-cert-2011.xml
md manage: INFO:2021-03-12 03h45.43 utc:1871: Skipping /var/lib/gvm/cert-data/dfn-cert-2011.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.48 utc:1871: Skipping /var/lib/gvm/cert-data/CB-K13.xml, file is older than last revision
md manage: INFO:2021-03-12 03h45.48 utc:1871: Updating /var/lib/gvm/cert-data/CB-K20.xml
md manage: INFO:2021-03-12 03h46.02 utc:1871: Skipping /var/lib/gvm/cert-data/CB-K14.xml, file is older than last revision
md manage: INFO:2021-03-12 03h46.02 utc:1871: Skipping /var/lib/gvm/cert-data/CB-K16.xml, file is older than last revision
md manage: INFO:2021-03-12 03h46.02 utc:1871: Skipping /var/lib/gvm/cert-data/CB-K15.xml, file is older than last revision
md manage: INFO:2021-03-12 03h46.02 utc:1871: Skipping /var/lib/gvm/cert-data/CB-K17.xml, file is older than last revision
md manage: INFO:2021-03-12 03h46.02 utc:1871: Updating /var/lib/gvm/cert-data/CB-K19.xml
md manage: INFO:2021-03-12 03h46.03 utc:1871: Updating /var/lib/gvm/cert-data/CB-K21.xml
md manage: INFO:2021-03-12 03h46.04 utc:1871: Updating /var/lib/gvm/cert-data/CB-K18.xml
md manage: INFO:2021-03-12 03h46.05 utc:1871: sync_cert: Updating CERT info succeeded.
event target:MESSAGE:2021-03-12 03h52.32 UTC:2472: Target Target for immediate scan of IP 127.0.0.1 - 2021-03-12 03:52:32 (455c97f4-364d-4d96-aa8e-a60d81e02ce2) has been created by admin
event task:MESSAGE:2021-03-12 03h52.32 UTC:2472: Status of task (5505d8cf-04cd-461b-bd00-3b39bd135afc) has changed to New
event wizard:MESSAGE:2021-03-12 03h52.32 UTC:2472: Wizard quick_first_scan could not be run by admin

Can you please guide me what I can do to solve it

Hi @BAK
Please try this one (I think a non privileged user gvm exists in your system):
sudo su - gvm
gvmd --get-users --verbose
(take a note of your user ID, normally admin)
gvmd --modify-setting 78eceaec-3385-11ea-b237-28d24461215b --value [user ID]

Yesterday I fired up a new Debian VM, followed the installation write-up found in this forum in a different thread (but it should be very similar, if not identical, for Ubuntu) and I was stuck with that error.
Iā€™m sure I had run that command during the install, since it is part of the instructions! But I got the error. Maybe there was a problem with the feed updates, I donā€™t knowā€¦
Today, I run that command again and now it worksā€¦!

Even after you have fully synced the feeds, it takes gvm some time to ingest that data. Iā€™ve seen it take anywhere from 15minutes to an hour depending on how much CPU/Memory you are throwing at it. I got around this by using docker and building an image that includes a recent full copy of the feeds as well as a fully functioning DB. You can spin up the scanner and have it ready to scan in 5-10 minutes or immediately if you skip the sync.

immauss/openvas (docker.com)

2 Likes

Hey Folks,

i have the same Problem. I followed the instruction but i have 0 scan configs.

here can we see the last entry is 22 days old and 0 configs. What can i do? thanks

You need to check the gvmd log file (should be somewhere in /var/log and named gvmd.log) about GVMD_DATA sync.

1 Like

Hey Bricks, thanks for help. Here is the log. Dont know what the issue :frowning:

FATAL: role ā€œ_gvmā€ does not exist

gvmd.log (39.6 KB)

Just directly at the start of the log file

md manage:WARNING:2021-04-29 05h53.30 utc:4270: sql_open: PQconnectPoll failed
md manage:WARNING:2021-04-29 05h53.30 utc:4270: sql_open: PQerrorMessage (conn): FATAL:  role "_gvm" does not exist
md manage:WARNING:2021-04-29 05h53.30 utc:4270: init_manage_process: sql_open failed

means your database is not correctly set up. Because this is very distribution specific you need to contact the distribution for a fix. I suspect you can follow the db setup steps from https://github.com/greenbone/gvmd/blob/gvmd-21.04/INSTALL.md#setting-up-the-postgresql-database and replace the username mattm with _gvm but I am not sure about that.

2 Likes

Hi. Iā€™ve not been using Kali since quite some time now, but looking at this guide
https://www.humbertojunior.com.br/infosec/2021/01/22/installing-gvm-kali-linux.html
I remembered about this
sudo gvm-check-setup
that maybe could helpā€¦ Just in caseā€¦

Please note that script is maintained by Kali and not us. Please contact the Kali forum downstream.

1 Like

Sure, that was just a hint for @Ragna to check, I didnā€™t mean to say that it should be checked and/or fixed in this context, sorryā€¦

The error code isnā€™t good. As I understand this is an error message indicating that the user logged into GSA cannot find a specific config in the redis database. Getting data into the redis database requires a feed owner set in postgressql database using GVMD. In addition you must have downloaded the config to file using sync commands (there is a file containing the string 085569ce-73ed-11df-83c3-002264764cea if sync was successful). In addition there may be a number if misconfigs with components not being able to communicate with each other and permission issues (for sockets and files). The GSA, GVMD, openvas/ospd-openvas need to have the ability to return a proper error to allow you to quickly trouble shoot all of these possible issues for this issue, or at the very least GSA should have some good hints to resolve the error.

Note from my side the scan config is not in redis. The scan config is stored in the PostgreSQL database and provided by gvmd.

Error handling is always difficult and especially in this case. We are open to every code contribution here. Everybody is welcome to create a PR for GSA and also gvmd to improve the error handling and to add a better error message.

1 Like

And it even doesnā€™t need to be a code contribution. A guideline on how to fix this issue would also be welcome as a PR to our docs for example to the FAQ at https://github.com/greenbone/docs/blob/main/src/faq.md

1 Like

The problem in this case is that the solution requires very many steps and probably very few people know a certain number of steps that will solve the issue all of the time. I think it will be difficult to write a good guideline in this case.

Hello,
I have just installed the last version Kali Linux and OpenVAS. I canā€™t create scan config, I have current status feed, but my last logs show
libgvm util:Warning(date) ERROR: Error on line 1 char 1: Document was empty or contained only whitespace
md manage:Warning:(date) update_nvt_cache_osp: failed to get VTs

Do you know what is the problem ?

(moderator note, this is a duplicate post and followed up here) Can't create scan config - #6 by DeeAnn

Hello Folks who are trying to solve this problem in 2022.

Come on!

After spending more than 48 hours working to solve this problem, itā€™s only fair that I make a post about my experience with it.

My problem: Throughout the scan, when I clicked ā€œScanā€ it generated the following error: Failed to find config ā€˜daba56c8-73ec-11df-a475-002264764ceaā€™

things I did to try to solve it.

Step 1 Updated the following instances

greenbone-feed-sync --type GVMD_DATA
greenbone-feed-sync --type SCAP
greenbone-feed-sync --type CERT

A: But it didnā€™t.

Step 2- I uninstalled greenbone and installed it again.

A: It didnā€™t.

Step 3- sudo apt install gvm -y
sudo gvm-setup
sudo gvm-feed-update
sudo gvm-start

however, it also did not resolve.

Step - When running gvm-check-setup, all steps were correct, but the error remained.

Resolution: What solved my problem:

sudo runuser -u _gvm ā€“ gvmd --modify-setting 78eceaec-3385-11ea-b237-28d24461215b --value dabd2710-aebd-4048-a8c7-460b60e5fa93
please try:
sudo runuser -u _gvm ā€“ gvmd --modify-scanner 78eceaec-3385-11ea-b237-28d24461215b --value dabd2710-aebd-4048-a8c7-460b60e5fa93

Thanks @filo for helping me with this in your post.

2 Likes

Hi @dresc and welcome to the forum :slight_smile:

Thank you for posting your experience and what worked. This error is not fun at all to track down (or even know where to look at first). Weā€™d like to document this better for future reference and Iā€™ll probably derive a lot of it from this thread. Iā€™m glad itā€™s working now!

2 Likes

The relevant documentation on this required command can be found at https://github.com/greenbone/gvmd/blob/v21.4.4/INSTALL.md#set-the-feed-import-owner and is also part of the source build instructions at Building GVM 21.04 ā€” Greenbone Documentation documentation

2 Likes